Keycloak is free. It's open source under the Apache 2.0 licence, with no licence fee, no per-user price and no paid edition hiding the useful features.
Running it is not free. The good news is that the costs are predictable, if you know where they come from. The bad news is that the biggest one isn't on any invoice.
Budget Keycloak like a database, not like a library.
You'd never run a production database without backups, upgrades and someone on call. Identity deserves the same, because when it's down, nobody can sign in to anything.
The three bills
Bill 1: why is infrastructure sized by traffic, not users?
The most common mistake in Keycloak budgets is sizing by number of users. Keycloak doesn't care how many accounts exist. It cares how many people try to sign in at the same moment.
We learned this 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. The number that decided the infrastructure was never 200,000. It was how many people tried to log in during the busiest minute.
Keycloak's sizing guide.1
Cost by peak password logins per second
Amazon EKS across three availability zones, Graviton nodes, Aurora PostgreSQL with a standby, a load balancer. US East on-demand, no discounts. Excludes storage, backups, data transfer, monitoring and AWS Support.2
sign-ins in an hour is what roughly 36 password logins a second adds up to. That's the point where the $780 a month floor starts to rise, and it covers far more organisations than people expect.
Keycloak also needs a relational database. PostgreSQL is the usual choice. The built-in development database isn't meant for production.
Bill 2: why are upgrades the price of "free"?
This is the cost no invoice shows, and the one that catches teams out. Keycloak ships four minor releases a year and a major release every two to three years.3 Its security policy says fixes go into the current release line, with lower-severity fixes and hardening in the next one.4 In practice, staying on community Keycloak and staying secure means upgrading roughly every quarter.
Community releases vs Red Hat patch windows
Each upgrade is usually routine. The cost comes from skipping them. Fall several releases behind, and an urgent security fix turns into a multi-version jump: deprecated features removed, extensions to rebuild, themes to fix, all under time pressure.
The real licence fee for community Keycloak is a quarterly upgrade habit.
Teams that keep it pay a few days a quarter. Teams that don't pay it all at once, usually at the worst possible moment. If quarterly upgrades don't fit how you work, Keycloak's own security page points to the Red Hat build:
| Community Keycloak | Red Hat build of Keycloak | |
|---|---|---|
| Cost | Free | Included in Red Hat Runtimes or OpenShift subscriptions, counted by cores. Not sold on its own5 |
| Minor releases | Four a year | About every six months6 |
| Patches per minor | Fixes go into the current release line | About 12 months |
| Major versions | A new one every two to three years | Each supported at least 2 years (26.x), 3 from 27.x |
| Who runs it | You | Still you. Red Hat supports it but doesn't operate it |
Bill 3: who owns it?
Somebody has to own Keycloak: upgrades, patches, monitoring, certificate renewals, realm changes, and the incident when sign-in slows down on a Monday morning. We won't put a number on this, because it depends far more on your team than on Keycloak.
What are your options for running it?
When Keycloak really is free
- Local development, test environments and prototypes
- Small internal tools where an hour of downtime isn't an incident
- Teams with a platform group already running it among many services
When it isn't
- Customer-facing sign-in, where downtime means lost revenue
- Regulated environments that need patching evidence and audit trails
- Teams without anyone who wants to own an identity system
Questions we hear
Is Keycloak open source?
Yes. Keycloak is open source under the Apache 2.0 licence and is a Cloud Native Computing Foundation incubating project.9
Is there a paid version of Keycloak?
There's no paid edition of the software. The Red Hat build of Keycloak adds Red Hat support and longer version lifecycles, and comes with Red Hat Runtimes or OpenShift subscriptions.5
How much does it cost to host Keycloak?
On AWS at list prices, a highly available setup starts at about $780 a month in infrastructure, and stays there until peak traffic passes roughly 36 password logins a second. Engineering time comes on top.2
Does Keycloak need a database?
Yes. Keycloak stores users, configuration and sessions in a relational database, usually PostgreSQL. The built-in development database isn't for production.
Size it by traffic, schedule the upgrades, decide up front who owns it.
Tell us your peak sign-in traffic and how you'd like to run Keycloak. We'll size the infrastructure and show what each option involves.
Talk to our Keycloak teamSources
Every number on this page comes from a public source. Prices checked 14 Nov 2026.
- 1KeycloakConcepts for sizing CPU and memory resourcesvCPU per login, refresh and machine token; 150% headroom; database sizing.keycloak.org ↗
- 2
- 3Keycloak · Oct 2024Keycloak release updatesFour minor releases a year; a major release every two to three years.keycloak.org ↗
- 4KeycloakSecurity policyFixes go into the current major.minor release, lower-severity ones into the next. Points to the Red Hat build for long-term support.keycloak.org ↗
- 5Red HatSubscriptions for Red Hat build of KeycloakEntitled through Runtimes or OpenShift, counted by cores; not sold alone.redhat.com ↗
- 6Red HatRed Hat build of Keycloak life cycleMinor releases about every six months with about 12 months of patches; 26.x supported at least two years, 27.x and later three.redhat.com ↗
- 7US Bureau of Labor StatisticsSoftware developers: median pay$64.44 an hour median pay, 2025.bls.gov ↗
- 8US Bureau of Labor StatisticsEmployer costs for employee compensationWages are 70% of total compensation (June 2026), so $64.44 becomes $92 fully loaded.bls.gov ↗
- 9