← Back to Blogs
Keycloak · Running costs

Is Keycloak free? Yes, and here's what it costs

No licence, no per-user price. Three bills instead, and how to budget each one.

· 7 min read · Lokesh Ravichandru, CTO

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.

15/s
password logins per vCPU. Hashing does most of the work.
120/s
token refreshes or machine-to-machine tokens per vCPU.
+150%
CPU headroom for spikes.
0.35–0.7
database vCPU per 100 logins, logouts and refreshes a second.

Keycloak's sizing guide.1

Keycloak on AWS, per month

Cost by peak password logins per second

Keycloak on AWS monthly infrastructure cost by peak password logins per secondAbout $777 a month from zero to 36 logins per second, rising in steps to about $2,058 at 300 logins per second.$0$1K$2K$3K$4K050100150200250300$780/mo up to ~36 logins/s$2,058Peak 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

130,000

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.

Two years, illustrated from published cadence

Community releases vs Red Hat patch windows

Two years of Keycloak releasesCommunity Keycloak ships a minor release every quarter, eight in two years. The Red Hat build ships a minor release about every six months, each patched for about twelve months.TodayYear 1Year 2Communityminor releasesRed Hat buildpatch windows
Community minor releaseRed Hat minor, patched ~12 months

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 KeycloakRed Hat build of Keycloak
CostFreeIncluded in Red Hat Runtimes or OpenShift subscriptions, counted by cores. Not sold on its own5
Minor releasesFour a yearAbout every six months6
Patches per minorFixes go into the current release lineAbout 12 months
Major versionsA new one every two to three yearsEach supported at least 2 years (26.x), 3 from 27.x
Who runs itYouStill 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.

Knowledge concentrationIf one engineer knows how your Keycloak is configured, your identity system has a single point of failure that isn't on any architecture diagram.
Opportunity costEvery hour on identity plumbing is an hour not spent on the product. Fine if identity is strategic for you. Waste if it isn't.
$11,000

a year for every 10 hours a month your team spends on Keycloak, at the US median for software developers, fully loaded ($92 an hour).7,8 So ask: how many hours a month would we spend, and is that less than what we pay now?

What are your options for running it?

Option 1Your own teamPay for infrastructure and engineering time. Best if you already run Kubernetes and stateful services.
Option 2Red Hat buildAdd a Red Hat subscription. Best for enterprises that need vendor support and longer version support.
Option 3A managed partnerInfrastructure plus a service fee. Control of your data without running identity day to day. How we run it
Option 4Dev and test onlyAlmost free. Prototypes, internal tools, learning.

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.

How often does Keycloak need upgrading?

Keycloak ships four minor releases a year, and security fixes go into the current release line. Most teams on community Keycloak upgrade roughly every quarter.3,4

Budget it before you choose it

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 team
Lokesh RavichandruCTO, Grootan Technologies. Lokesh has led enterprise Keycloak migrations and upgrades, and Keycloak and AI implementations for clients in Germany, Switzerland, Singapore and Australia.
Evidence

Sources

Every number on this page comes from a public source. Prices checked 14 Nov 2026.

  1. 1
    KeycloakConcepts for sizing CPU and memory resourcesvCPU per login, refresh and machine token; 150% headroom; database sizing.keycloak.org ↗
  2. 2
    Amazon Web ServicesAWS pricing, US East (N. Virginia)EKS $0.10/h, ALB $0.0225/h plus LCUs, Aurora I/O-Optimized. Graviton c7g and Aurora r7g instance prices via price trackers.EKS ↗ · ELB ↗ · Aurora ↗ · c7g ↗ · r7g ↗
  3. 3
    Keycloak · Oct 2024Keycloak release updatesFour minor releases a year; a major release every two to three years.keycloak.org ↗
  4. 4
    KeycloakSecurity 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 ↗
  5. 5
    Red HatSubscriptions for Red Hat build of KeycloakEntitled through Runtimes or OpenShift, counted by cores; not sold alone.redhat.com ↗
  6. 6
    Red 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 ↗
  7. 7
    US Bureau of Labor StatisticsSoftware developers: median pay$64.44 an hour median pay, 2025.bls.gov ↗
  8. 8
    US 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. 9
    Cloud Native Computing FoundationKeycloak project pageIncubating project since April 2023.cncf.io ↗