Most Keycloak vs Okta comparisons line up feature tables and declare a winner. That misses the question a CTO actually has to answer.
Which parts of Okta are you using, and what would those parts cost to run yourself?
Okta sells a platform. Keycloak is an identity provider. If your team uses Okta for single sign-on and MFA and little else, you're paying platform prices for a feature you could run on your own infrastructure. If you depend on Okta to create and remove accounts across fifty SaaS tools when people join and leave, that's a different conversation.
The short answer
Two Okta products, two different comparisons
Okta sells Workforce Identity for your employees and customer identity for the people who use your product. It also owns Auth0. The pricing models have almost nothing in common, so the comparison with Keycloak splits too.1
| Workforce plan | Per user / month | What's added |
|---|---|---|
| Starter | $6 | SSO, MFA, Universal Directory, 5 workflows |
| Core Essentials | $14 | Lower-cost bundle without advanced security and compliance |
| Essentials | $17 | Adaptive MFA, privileged access, lifecycle management, governance, 50 workflows |
Okta list prices, checked 14 Nov 2026.
What does Keycloak cost to run?
Keycloak is open source under Apache 2.0: no licence, no per-user fee. You pay for infrastructure and for the people who keep it healthy. Infrastructure depends on how many sign-ins hit it per second, not on how many accounts exist. Keycloak's sizing guide puts it at about 15 password logins per second per vCPU, with 150% headroom for spikes.2
A highly available Keycloak on AWS (three Graviton nodes on Amazon EKS, Aurora PostgreSQL with a standby, a load balancer) costs about $9,320 a year at list prices, until peak traffic passes roughly 36 password logins a second.3
For workforce identity that ceiling is high. If all 5,000 employees of a large company signed in within the same ten minutes, that would be about 8 logins a second.
Where does Keycloak start to pay off?
Infrastructure is only half the bill. The fair test is how much engineering time the price gap pays for. At the US median for software developers, fully loaded ($92 an hour),4,5 here's Okta's list price against Keycloak with 20 hours a month of your team's time:
Okta per employee vs Keycloak's flat cost
Okta list prices, annual billing. Keycloak: AWS US East on-demand, excluding storage, backups and monitoring. Illustrative.
| Engineering time on Keycloak | Break-even vs Starter | Break-even vs Essentials |
|---|---|---|
| 10 hours a month | ~280 employees | ~100 employees |
| 20 hours a month | ~440 employees | ~150 employees |
| 40 hours a month | ~740 employees | ~260 employees |
For SSO and MFA, per-seat pricing stops making sense somewhere in the hundreds of employees. But only if you compare like for like.
What does Okta do that Keycloak doesn't?
Most comparisons skip this, and it's where switching projects go wrong.
| Okta Workforce | Keycloak | |
|---|---|---|
| Single sign-on | OIDC, SAML | OIDC, SAML |
| MFA and passkeys | Yes | Yes, passkeys supported since 26.46 |
| User directory | Universal Directory | Built-in users, plus LDAP and Active Directory federation |
| Joiner-mover-leaver automation | Lifecycle management, workflows | Not built in. Needs SCIM tooling or custom work |
| Pre-built app integrations | Large catalogue | Standard protocols; you configure each app |
| Risk-based MFA | Included from Essentials | Conditional flows you configure; no built-in risk scoring |
| Where it runs | Okta's cloud | Your cloud, your region, or on-premises |
If your IT team's daily work happens in Okta Workflows and lifecycle rules, Keycloak will feel like a step back. If your Okta tenant is mostly a login page in front of internal apps, you're paying for capability you don't use.
The options most comparisons miss
This doesn't have to be all or nothing.
The best identity architecture is the one you can change later.
Putting Keycloak in front of your applications, even while Okta stays behind it, turns a future migration from a big-bang project into a configuration change.
Why data location matters more in Europe
Okta runs in Okta's cloud. Keycloak runs wherever you deploy it: your AWS account, a German region, an on-premises data centre. Google search data shows more interest in Keycloak in Germany than in the United States:7
Average monthly Google searches for "keycloak", Oct 2025 to Sep 2026.
The top German result for "keycloak vs okta" is a list of European alternatives to Okta. For organisations that need identity data under their own control, self-hosting isn't an engineering preference. It's a procurement requirement.
What does switching from Okta involve?
- PasswordsOkta's APIs don't return user passwords, according to Okta's developer forum.8 Decide early how users will get their passwords into Keycloak, and test it before cutover.
- ApplicationsRe-register each app's OIDC or SAML integration. Catalogue apps you never configured by hand need the most attention.
- MFAUsers re-enrol factors. Plan the communication; it's the step employees notice.
- ProvisioningAnything Okta created or removed automatically needs a new owner before cutover.
- CutoverMove in phases, by application or department, with a rollback path at each step.
Our IdP migration service covers moves from Okta, Auth0, Azure AD B2C or an in-house login.
Who should run Keycloak?
Questions we hear
Is Keycloak a good alternative to Okta?
For single sign-on and MFA, yes. Keycloak supports the same standards (OIDC, OAuth 2.0, SAML) and runs where you choose. It doesn't replace Okta's lifecycle management, workflow automation or app catalogue without extra tooling.
Is Keycloak cheaper than Okta?
On licence, yes: Keycloak has none. A highly available setup on AWS costs about $9,320 a year in infrastructure at list prices. Whether it's cheaper overall depends on how many employees you have and how many hours your team spends running it.3
Can you get user passwords out of Okta?
Okta's APIs don't return user passwords, according to an Okta staff answer on its developer forum. Plan how passwords will be handled before you start a migration.8
Can Keycloak and Okta work together?
Yes. Keycloak can broker authentication to Okta, so applications use Keycloak while employees keep signing in with Okta.
Does Okta own Auth0?
Yes. Okta completed its acquisition of Auth0 in 2021.
List what you actually use. If it's SSO and MFA, price Keycloak against it.
Send us your Okta plan and headcount. One of our Keycloak engineers will map what moving, splitting or brokering would involve.
Talk to our Keycloak teamSources
Every number on this page comes from a public source. Prices checked 14 Nov 2026.
- 1OktaOkta pricingWorkforce: Starter $6, Core Essentials $14, Essentials $17 per user/month, $1,500 annual minimum. Customer identity: $3,000/month base platform.okta.com ↗
- 2KeycloakConcepts for sizing CPU and memory resourcesvCPU per login, refresh and machine token; 150% headroom; database sizing.keycloak.org ↗
- 3
- 4US Bureau of Labor StatisticsSoftware developers: median pay$64.44 an hour median pay, 2025.bls.gov ↗
- 5US Bureau of Labor StatisticsEmployer costs for employee compensationWages are 70% of total compensation (June 2026), so $64.44 becomes $92 fully loaded.bls.gov ↗
- 6
- 7OpenSEO · Google dataKeyword researchAverage monthly searches for "keycloak", Oct 2025 to Sep 2026: Germany about 14,800, United States about 12,100.
- 8Okta Developer ForumGet current users' passwordsOkta staff reply: "Okta APIs will not return a user's password back."devforum.okta.com ↗
- 9Red HatSubscriptions for Red Hat build of KeycloakEntitled through Runtimes or OpenShift, counted by cores; not sold alone.redhat.com ↗