Keycloak operating cost calculator

Estimate Keycloak operation from authentication peaks, federation, environments, database capacity, recovery targets and support responsibilities.

Last updated

In short

  • Identity capacity follows authentication behavior and peaks, not just registered users.
  • Federation and application integration create work outside the Keycloak process.
  • Extra instances do not remove database, network or identity-provider failure modes.
On this page (5)

Costs and savings · Part of Keycloak

Interactive worksheet · no sign-up

Estimate Keycloak identity costs

Use the same currency and scope for both options. Inputs stay in this page; they are not included in analytics or sent with an enquiry.

1. Your current bill
2. The replacement

Business management: CHF 1,590/month for up to 3 apps; onboarding from CHF 9,900. Infrastructure and paid licences are extra.

Email, SMS or delivery units

Use the delivery vendor’s unit. Keep phone, AI and messaging charges outside the base licence visible.

An identity-provider migration does not replace endpoint management, directory services or all governance capabilities. Validate recovery and emergency access.

3. Transition and overlap
Optional: value internal operating time

Time released is capacity, not automatically payroll or cash saved. Keep time already billed by Pilae or another supplier out of these fields.

How the calculation works
  1. Current monthly invoices = billed units × unit price + additional current spend.
  2. Replacement monthly invoices = Pilae management + additional infrastructure + target licences + workload usage + retained services.
  3. Transition = plan onboarding + new hardware + extra migration + training + parallel months × max(0, current invoices − retained services). Parallel months are capped at the comparison horizon.
  4. Total invoices = monthly invoices × horizon, plus transition for the replacement. Payback uses the full transition commitment divided by positive monthly invoice saving, including all entered overlap months even beyond the selected horizon.
  5. Economic saving adds the change in valued internal operating time. It does not assume headcount reduction.

Business includes up to 3 apps, then a published per-app fee (CHF 390 in CHF). Starter’s published CHF price is CHF 449/month. All Pilae figures come from the same price data as the pricing page. Workload inputs are your estimates, not supplier quotes. Taxes, price growth, discount rates, opportunity costs and differences in functionality are outside this arithmetic.

Keycloak removes some identity-provider licence costs only when its capabilities and operating model fit the requirement. It still needs a database, monitoring, updates, recovery and integration work. The calculator helps budget those responsibilities; the first sizing input is authentication behavior.

Describe the login workload

Count peak logins, token refreshes, active sessions, realms and clients. Include events that synchronize demand: staff arriving at work, a mobile-app release or an outage after which clients reconnect together. Federation can place part of the load and failure risk on an external directory.

Input Question to answer Budget consequence
Authentication peak How many logins arrive during the busiest interval? CPU and spare capacity
Session lifetime How long are users active and how often are tokens refreshed? Memory and database behavior
Credential checks Which password and authentication flows are used? CPU cost per login
Federation Which external identity sources must respond? Integration and dependency operation
Environments Production, staging and recovery? Separate capacity and maintenance
Availability What happens if sign-in is unavailable? Redundancy and support coverage

The upstream CPU and memory sizing guide is a reference for its documented architecture and test assumptions. Do not turn a published benchmark into a promise that a particular machine supports a fixed employee count under every authentication method.

Inventory the applications as well as the server

Each application needs a supported protocol, redirect configuration, claims, role mapping and a lifecycle decision. Signing in with a central identity does not automatically provision every account or disable every existing application session. Budget tests for leavers, changed groups, password resets and emergency administrator access.

If the previous provider also supplies device management, risk detection or access reviews, identify which of those functions remain. A successful OpenID Connect login is not a replacement for that entire service bundle.

Separate basic operation from resilience

A single-instance design and a highly available design have different costs. Keycloak’s high-availability documentation describes several deployment choices and trade-offs. Additional application instances still depend on database, networking and upstream identity services. Define the failure you need to tolerate before buying a topology.

For illustration, an estate might require one production environment, one staging environment and an isolated recovery target. Even when staging is smaller, it needs configuration maintenance, secrets handling and upgrade validation. Counting only production compute leaves those activities unpriced. This is a planning example, not a capacity recommendation.

Compare invoices and responsibilities honestly

Enter the actual identity licence bill that can end, the licences that stay and the new service plus infrastructure costs. Add migration of clients, federation and account state. Separate one-off rollout from recurring client onboarding. If your organization already operates Keycloak, distinguish the incremental cost of another application from the full estate cost.

Pilae pricing is the service-rate source used by the calculator. A scoped identity proposal should state who owns each client configuration, who responds to authentication failures and which upstream support or paid application features are necessary.

Accept the service with recovery evidence

Validate the chosen release and database combination against upstream support. Test normal login, expired credentials, group changes, upstream unavailability and access denial. Back up the database and required configuration/secrets, then demonstrate recovery in an isolated environment before relying on the service.

An upgrade plan should preserve a compatible recovery path; restoring an old application binary against a changed database is not a generic rollback strategy. Bring the current client list and login profile to an identity review. If Entra remains upstream, the federation guide explains the boundary that the budget must retain.

Sources and further reading

Use the linked documentation to confirm the version, edition and contract that apply to your project.

Plan our identity service

Bring your current bill, required capabilities and workload assumptions. We will separate recurring operation from migration and retained services.