Auth0 alternatives in 2026: five open-source identity providers compared, and when to stay
Auth0 alternatives and competitors compared: Keycloak, authentik, ZITADEL, Ory and Logto on license, architecture and price, plus authentik vs Keycloak and when to stay.
Auth0 is free up to 25,000 monthly active users. The first paid plan starts at $35 a month, Professional at $240, and the moment your B2B customers ask for their own SSO, you are looking at the B2B plans. That is usually when teams start searching for an alternative. The open-source options below cover the same protocols: OIDC, OAuth 2.0, SAML, MFA. They differ in three things that matter more than the feature list: the license, the architecture, and who operates them at 3 a.m.
This article compares Keycloak, authentik, ZITADEL, Ory and Logto as of November 2026, with prices read on each vendor's page. If you only want the head-to-head with Keycloak, read Keycloak vs Auth0.
Why teams leave Auth0
The product is rarely the reason. The bill is.
- Pricing follows users, not load. Every new active user moves you up a tier. A login service that costs the same to run at 10,000 and 50,000 users is billed very differently.
- Enterprise features sit behind plan jumps. Enterprise connections, self-service SSO and SCIM are part of the B2B plans. The first enterprise customer who wants SAML changes your identity budget.
- Data location. The user store sits on a US-controlled platform. For GDPR and NIS2 scope reviews, that is a discussion you have every year.
- Exit cost grows with time. Custom Actions, rules and hosted login pages are proprietary. The longer you stay, the more you rewrite when you leave.
What Auth0 costs in 2026
- Free: up to 25,000 monthly active users.
- Essentials: from $35 a month.
- Professional: from $240 a month.
- B2B plans: needed for enterprise connections, self-service SSO and SCIM.
- Enterprise: by quote.
The price moves with monthly active users, so run your own number through the calculator on Auth0's pricing page. Prices as of November 2026.
The short list
Criterion | Keycloak | authentik | ZITADEL | Ory | Logto |
License | Apache 2.0 | MIT core, enterprise features under EE license | AGPL-3.0 since v3; SDKs Apache 2.0 | Apache 2.0 | MPL-2.0 |
Architecture | Full IAM server, Java (Quarkus) | IdP plus app proxy, Python and Go | Multi-tenant IdP, Go, event-sourced | Headless API components: Kratos, Hydra, Keto | Developer-first CIAM with hosted sign-in UI |
Strongest at | Enterprise SSO, SAML, LDAP and AD federation | Internal apps, homelab to SME, protecting apps without native SSO | B2B SaaS with many customer organisations | Teams that build their own login UI and want only APIs | Product teams that want Auth0-like DX, self-hosted |
Paid option | None from the project; managed by providers | Enterprise $5 per internal user, $0.02 per external user a month | Cloud Pro $100/mo for 25,000 DAU; self-hosted Enterprise on commercial license | Ory Network from $770/year | Self-hosted Pro $249/mo list |
Governance | CNCF Incubating since 2023 | Company-backed | Company-backed | Company-backed | Company-backed |
Prices as of November 2026, net, in the vendor's currency. Sources are linked in each section below.
Keycloak: the default for enterprise SSO
Keycloak is the most complete of the five and the one most auditors already know. SAML 2.0, OIDC, LDAP and Active Directory federation, Entra ID as an identity provider, fine-grained admin per realm: all of it is in the open-source release, nothing is gated. It is a CNCF Incubating project since April 2023, which matters if your procurement asks who governs the code.
The catch is operations. Keycloak ships fast: the current release is 26.8.2, and the 26.7 branch reached end of life on 1 October 2026, three months after its first release (version history). Running it well means a clustered deployment, a database you back up and test, and an upgrade every quarter.
Choose it if you sell to enterprises, need SAML and directory federation, or want the option every IAM consultant can support.
authentik: the most pleasant to run for internal apps
authentik combines an identity provider with an outpost proxy, so it can put SSO in front of applications that have none. The open-source edition covers OIDC, SAML, LDAP, SCIM, RADIUS and proxy providers. The core is MIT-licensed; enterprise features live in a separate directory under their own license (repository).
Enterprise costs $5 per internal user and $0.02 per external user a month, billed annually. For a customer-facing app that is cheap; for 2,000 employees it is $10,000 a month. Check which side of that line you are on.
Choose it if most of your users are employees and your apps include tools without native SSO.
ZITADEL: multi-tenancy built in
ZITADEL was designed for B2B SaaS: organisations, per-customer branding and delegated admin are core concepts, not plugins. It is written in Go and runs as a single binary.
The license changed. Since version 3, the core, console and login are AGPL-3.0, while APIs and SDKs stay Apache 2.0. For running it internally this rarely matters; if you modify ZITADEL and offer it to others as a service, AGPL obligations apply, and the vendor sells a commercial license for that case. The cloud offer starts free at 100 daily active users and costs $100 a month for 25,000, with EU and Swiss regions (pricing).
Choose it if you run a B2B product where each customer is an organisation with its own users and SSO.
Ory: identity as APIs, UI is yours
Ory is a set of Apache-licensed components: Kratos for identities and login flows, Hydra for OAuth 2.0 and OIDC, Keto for permissions. There is no admin console in the open-source stack and no ready login page you would ship to customers. You build the UI against the APIs.
That makes Ory the most flexible and the most work. The managed Ory Network bills per average daily active user and starts at $770 a year (pricing).
Choose it if you have frontend capacity, want full control over every screen, and prefer small services over one server.
Logto: closest to the Auth0 developer experience
Logto is MPL-2.0 and aims at the same developer audience as Auth0: SDKs for common frameworks, a hosted sign-in experience, social login, organisations. The open-source edition has no user caps. The self-hosted Pro plan, $249 a month list, adds tenant-wide MFA enforcement, custom UI and unlimited SAML apps for deployments up to 50,000 MAU (plans).
Choose it if you are a product team migrating a customer login from Auth0 and want the shortest rewrite.
If you are looking for Keycloak alternatives
Keycloak is the reference point for the other four, so the same list answers a second question: what to use instead of Keycloak. Two comparisons come up most often.
- authentik vs Keycloak. Both speak SAML, OIDC and LDAP. Keycloak has the deeper federation features and the widest support among IAM consultants; authentik is easier to run for internal apps and puts SSO in front of tools without native login through its proxy outpost. Customer-facing enterprise SSO points to Keycloak, an employee portal to authentik.
- ZITADEL vs Keycloak. Keycloak separates tenants as realms; ZITADEL has organisations, per-customer branding and delegated admin built in. Keycloak is Apache 2.0, ZITADEL AGPL-3.0 since v3. For B2B SaaS with many customer organisations ZITADEL fits more naturally; wherever directory federation matters, Keycloak.
The license decides more than the feature list
All five speak OIDC. What separates them on a three-year horizon is what you are allowed to do with the code.
- Apache 2.0 and MIT (Keycloak, Ory, authentik core): use, modify and run it as a service without publishing your changes.
- MPL-2.0 (Logto): changes to Logto's own files must be shared if you distribute them; your application code stays yours.
- AGPL-3.0 (ZITADEL since v3): modified versions offered over a network must be published, or you buy the commercial license.
- Open core (authentik, Logto, ZITADEL, Ory): some features exist only in paid editions. Check that the one you need today is in the free tier, not on the roadmap of the paid one.
This is not legal advice. If your platform team plans to fork, ask your counsel before you pick.
The cost that is not on any pricing page
Self-hosting removes the per-user fee. It does not remove the work.
- High availability. Login is the one service every other service depends on. Plan at least two nodes and a database with tested failover.
- Upgrades. Keycloak's 26.7 line lived three months. Every identity provider here ships security fixes you cannot skip.
- Backups you restore. A backup of the user database that nobody has restored is a hope, not a backup.
- Monitoring and on-call. When the IdP is down, nobody can log in to the tools you would use to fix it.
- Policy work. MFA rules, passwordless rollout, realm or organisation design, session lifetimes. This is where most migration projects spend their time.
If nobody on the team owns these five, budget for someone who does: an engineer, or a managed service.
How to choose in five questions
- Are most users employees or customers? Employees point to Keycloak or authentik; customers to Logto, ZITADEL or Ory.
- Do your customers need their own SSO and organisations? Then ZITADEL or Keycloak.
- Do you need SAML and LDAP or AD federation? Keycloak is the safest bet.
- Will you modify the code and offer it to others? Prefer Apache or MIT, or budget a commercial license.
- Who runs it? If the answer is nobody, choose a managed offer first and the software second.
Moving off Auth0 without a big bang
Run the new provider in parallel, move one application at a time, and keep Auth0 as the fallback until the last app is switched. Two details decide how smooth this is. First, password hashes: Auth0 does not include them in its self-service user export, so plan the support request early or let users reset passwords on first login. Second, custom Actions: list them before you start, because each one becomes code or configuration on the new side.
When to stay on Auth0
Stay if you are below 25,000 monthly active users and on the free plan, if you have no one to operate identity and no budget for a managed service, or if you rely on an Auth0-only feature you cannot rebuild. Auth0 is a good product. The reasons to leave are cost at scale, gated enterprise features and data location; if none of them applies to you, moving is effort without return.
What we do
Hostzero runs Managed Keycloak in Frankfurt: 24/7 operations, security patches, backups, MFA and passwordless policy, 99.9% availability SLA, from €49 a month with no per-user fee. We also maintain an open-source Keycloak Operator for Kubernetes on GitHub. If Keycloak is the wrong fit for you, we will say so in the first call. All prices net, as of November 2026.
Pascal Ehlert, founder of Hostzero, talks about running Keycloak as a product at DevOpsCon Munich on 1 December 2026: talk details.
Frequently asked questions
What is the best open-source alternative to Auth0?
For enterprise SSO with SAML and directory federation, Keycloak. For customer login with an Auth0-like developer experience, Logto. For B2B SaaS with many customer organisations, ZITADEL. For employee apps, authentik. For teams that build their own UI, Ory.
What are the best Keycloak alternatives?
authentik for internal apps and employee SSO, ZITADEL for multi-tenant B2B SaaS, Logto for product teams that want hosted sign-in and SDKs, Ory for teams that build their own UI. All four are open source and can be self-hosted.
authentik or Keycloak?
Keycloak for enterprise SSO with SAML and directory federation and the widest consultant support; authentik for internal apps and for putting SSO in front of tools that have none.
Is Keycloak free for commercial use?
Yes. Keycloak is Apache 2.0, with no paid edition and no per-user fee. You pay for the servers and for the people or the service that run it.
Can I self-host ZITADEL commercially after the AGPL change?
Yes for internal use. If you modify ZITADEL and offer it to third parties over a network, AGPL requires you to publish those changes, or you buy ZITADEL's commercial license.
How long does a migration from Auth0 take?
It depends on the number of applications and custom Actions more than on the user count. Moving one application at a time with Auth0 as fallback avoids downtime.
Do self-hosted identity providers help with GDPR and NIS2?
They let you choose where user data lives and who can access it, which simplifies the supply-chain part of a NIS2 risk assessment. Your own obligations stay yours.
Have questions about this topic?
Our experts are happy to advise you on your individual strategy.
Schedule a consultation