We worked on a citizen super app in Türkiye that signed in more than 200,000 people through Keycloak. Daily active users rose and fell from one day to the next.
When it came to sizing, 200,000 was never the number that mattered. What mattered was how many people tried to log in during the busiest minute.
Auth0 bills you for who logs in.
Keycloak bills you for how fast they log in.
Get that wrong and you either overpay Auth0 for users who barely show up, or under-build Keycloak for a Monday-morning spike. Here's how both price out, and when staying on Auth0 is the right call.
The short answer
What does Auth0 cost as you grow?
Auth0 prices by monthly active users (MAU), in tiers, with separate B2C and B2B plans. Published monthly list prices:
| MAU | B2C Essentials | B2C Professional | B2B Essentials | B2B Professional |
|---|---|---|---|---|
| 500 | $35 | $240 | $150 | $800 |
| 1,000 | $70 | $240 | $300 | $800 |
| 5,000 | $350 | $1,000 | $1,300 | $1,500 |
| 10,000 | $700 | $1,600 | $2,100 | $2,400 |
| 20,000 | $1,400 | $3,200 | $3,800 | Quote |
Auth0 list prices, checked 14 Nov 2026.1 Annual billing is 11× the monthly price.
If every enterprise customer brings its own Entra ID or Okta tenant, your SSO bill grows with your sales pipeline. And a 200,000-user app like the one above sits entirely in quote territory.
What does Keycloak actually cost to run?
Keycloak is open source under Apache 2.0, with no licence fee and no per-user price. You pay for infrastructure and for the people who run it. Infrastructure depends on traffic, and Keycloak's own sizing guide is specific about how much:2
Keycloak's 26.4 benchmark ran 500 logins and 2,500 token refreshes a second on three pods with Aurora PostgreSQL, and reported near-linear vertical scaling up to 12,000 requests a second.3
We priced that guidance on AWS: three Graviton nodes on Amazon EKS (one per availability zone), Aurora PostgreSQL with a standby in a second zone, and an Application Load Balancer.4 Put the two meters side by side:
Users
Logins per second
Left: Auth0 B2B Essentials, monthly list price. Right: Keycloak on AWS US East, monthly on-demand infrastructure, password logins only. Same dollar scale.
A highly available Keycloak on AWS costs about the same at 5,000 users as at 500,000, until your peak passes roughly 36 password logins a second.2,4
Excludes database storage, backups, data transfer, monitoring and AWS Support. On-demand prices, no reserved-instance discounts.
People are the other half: upgrades, patches, monitoring and the occasional 2 a.m. page. Keycloak releases often, and staying current matters for security. That cost depends far more on your team than on Keycloak, so we don't guess it. We work out what the price gap can pay for instead.
Where's the crossover for you?
Take your Auth0 bill, subtract Keycloak's infrastructure, and divide by what an engineer costs. At the US median for software developers, fully loaded ($92 an hour),5,6 this is how many hours a month the gap pays for:
Auth0 list prices with annual billing, against Keycloak's $9,320 a year floor (peak under 36 logins/s). Illustrative; your invoice and traffic will differ.
At 10,000 to 20,000 users the gap is real but modest: a few days of engineering a month. It widens fastest with enterprise connections and with scale, which is exactly where Auth0 stops publishing prices.
Switching to Keycloak doesn't save money by itself. It saves money when the hours to run it cost less than the gap.
That's why most teams that switch either already run Kubernetes, or hand day-to-day operations to a partner who runs Keycloak every day.
Auth0 or Keycloak: which fits?
Stay on Auth0 if
- Your users number in the low thousands and grow slowly
- No one wants to own an identity system at 2 a.m.
- Most users sign in with Google or Apple
- Procurement needs a vendor-backed SLA
- Engineering time is your scarcest resource
Move to Keycloak if
- Enterprise customers each want their own SSO
- Your user count is heading into quote territory
- Customers or regulators ask where identity data lives
- Your login flow needs steps Auth0 makes awkward
- You already run Kubernetes and stateful services
On features, the two are closer than the pricing suggests. The real difference is control.
| Auth0 | Keycloak | |
|---|---|---|
| Protocols | OIDC, OAuth 2.0, SAML | OIDC, OAuth 2.0, SAML |
| B2B multi-tenancy | Organizations | Organizations, fully supported since 26.07 |
| Passkeys and MFA | Yes | Yes, passkeys supported since 26.48 |
| Enterprise SSO | Priced per connection on B2B plans | Identity brokering, no per-connection fee |
| Customisation | Actions (hosted functions) | Authenticators, themes and extensions (SPIs) |
| Data location | Auth0's regions | Your cloud, your region, or on-premises |
| Who keeps it running | Auth0, owned by Okta | Your team or a partner |
What does switching involve?
Moving off Auth0 is very doable, but it isn't a weekend job. The parts that need a plan:
- Password hashesAuth0 exports them only through a support case, encrypted with your PGP key and signed off by a CISO, CSO or VP. It reviews each request and gives no ETA.9 Start early, or move users on their next login instead.
- ConnectionsRe-create social logins and each enterprise SSO connection, and test them with the customer's IT team.
- MFADecide how enrolled factors carry over or how users re-enrol.
- Custom logicAuth0 Actions become Keycloak authenticators or extensions.
- TokensApps that read specific claims must get the same claims from Keycloak.
- CutoverMove in phases, by application or user group, with a rollback path at each step.
Our IdP migration service covers each of these, from Auth0, Okta, Azure AD B2C or an in-house login.
Who should run Keycloak?
Questions we hear
Why is Auth0 so expensive?
Auth0 charges by monthly active users in tiers, and its B2B plans add $100 a month for every enterprise SSO connection beyond the 3 or 5 included. The bill grows with your user base and your enterprise customer count, even when your traffic doesn't.1
Is Keycloak free?
The software is free and open source under Apache 2.0. Running it isn't. A highly available setup on AWS starts at about $780 a month in infrastructure at list prices, plus the time to operate it.2,4
Does Okta own Auth0?
Yes. Okta completed its acquisition of Auth0 in 2021. Auth0 is now Okta's customer identity product.
Is Keycloak outdated?
No. Keycloak is a Cloud Native Computing Foundation incubating project under active development. Organizations became fully supported in Keycloak 26.0 and passkeys in 26.4.11,7,8
Can Keycloak do MFA?
Yes. Keycloak supports one-time passwords, WebAuthn security keys and passkeys, and conditional flows that ask for a second factor only when it's needed.
Close call? Keep Auth0. Clear gap? Plan the move while you can do it in phases.
Send us your Auth0 plan and peak traffic. One of our Keycloak engineers will check the numbers and map what a move would involve.
Talk to our Keycloak teamSources
Every number on this page comes from a public source. Prices checked 14 Nov 2026.
- 1Auth0Auth0 pricingPlan prices by monthly active users, SSO connection add-ons, annual billing.auth0.com/pricing ↗
- 2KeycloakConcepts for sizing CPU and memory resourcesvCPU per login, refresh and machine token; 150% headroom; database sizing.keycloak.org ↗
- 3Keycloak · Oct 2025Keycloak 26.4 performance benchmarks500 logins/s on three pods; near-linear scaling to 12,000 requests/s.keycloak.org ↗
- 4
- 5US Bureau of Labor StatisticsSoftware developers: median pay$64.44 an hour median pay, 2025.bls.gov ↗
- 6US Bureau of Labor StatisticsEmployer costs for employee compensationWages are 70% of total compensation (June 2026), so $64.44 becomes $92 fully loaded.bls.gov ↗
- 7
- 8
- 9Auth0 docsExport password hashes and MFA secretsSupport case, PGP key, executive sign-off, no ETA.auth0.com ↗
- 10Red HatSubscriptions for Red Hat build of KeycloakEntitled through Runtimes or OpenShift, counted by cores; not sold alone.redhat.com ↗
- 11