This is the exact reasoning I used to justify using Auth0 at my current job, and it’s the same logic I use to justify the maintenance time I put into my own Django library and using Auth0 for all my personal projects from now on.

They know what they are doing better than I do and their current pricing suits my needs fine.

> their current pricing suits my needs fine

$2 per user of your API? How can any company afford that?

If you're put off by the $2 per user per month pricing for "Internal Users", then I'd like to point out their docs about Internal vs External users... https://auth0.com/docs/policies/billing#in-our-pricing-what-...

The key line being: "There are no technical differences between these types of users, they simply refer to whether someone is external to your company, or an internal employee."

Also... This pricing distinction is only noted on their Developer Pro plan.

So for building things that are intended to be used by external users or external paying customers... where you can make the business case for spending at least $0.023 per User per Month (Developer Plan) or $0.28 per User per Month (Developer Pro Plan) then its fine.

If you start to build internal applications and your internal business processes start to rely on your staff logging in using Auth0, then $2 per internal employee per month that uses those tools doesn't seem expensive at all.

I'm in the market for the same type of service.

The pricing of Auth0 would never work out (our accounts are free and no one is paying us per account directly) for us.

(Indeed, that's why we are launching https://www.cloud-iam.com a Keycloak as a Service)

FYI, your TLS certificate is invalid.

Not a good look questioning people who know what they are doing by promoting a service apparently built by someone who does NOT know what they are doing.