Skip to content
Udibo

Udibo vs Keycloak

Choose Keycloak when you want an identity server on your infrastructure with SAML, LDAP, and Active Directory federation. Choose Udibo when you want hosted sign-in, organizations, roles, and per-resource permissions without operating the identity service. Keycloak's operating cost depends on the infrastructure and engineering time your deployment requires; Udibo follows its published usage prices.

Homepage capabilities checked November 15, 2026 against keycloak.org. The homepage confirms SAML and OpenID Connect identity brokering, LDAP and Active Directory federation, and built-in fine-grained Authorization Services. Udibo's prices are on its pricing page.

Deployment, licensing, application integration and password defaults checked November 19, 2026 against Keycloak's production guide, license, application guidance, upgrade guide, and the administration guide below. Red Hat's entitlement note covers its supported build. Udibo usage assumptions and API access were reviewed October 2.

Realm organization, passkey, and event-logging setup checked November 15, 2026 against the current Server Administration Guide for organizations, passkeys, and event logging.

For another identity server you can run yourself, see FusionAuth. Browse the comparison index for other options.

The short version

If you needStart with
SAML, LDAP or Active Directory users, or identity that stays on your serversKeycloak
An identity server with no license cost and the team to operate itKeycloak
Hosted sign-in that nobody on your team upgrades, clusters, or patchesUdibo
Organizations, custom roles, and a per-resource permission check, hostedUdibo
A bill that scales with usage rather than with servers and an engineerUdibo

Why teams pick Udibo over Keycloak

  • Nobody on your team runs the identity server. Keycloak's production guide describes two or more instances as a typical high-availability setup and explains proxy configuration when a proxy is used. It also covers TLS, a public hostname, production database configuration, and distributed caches across instances; its upgrading guide has you review migration changes and update themes on each release. Udibo runs the service: upgrades, availability, abuse controls, email delivery, and audit retention are on the bill, not on your calendar.

  • A vocabulary sized for a product. Keycloak's model is realms, clients, realm roles, client roles, composite roles, groups, and an authorization engine of resources, scopes, policies, and permissions. Udibo's is organizations, memberships, roles, and the permissions your application interprets, assignable across a tenant, inside one organization, or on one resource.

  • A hosted check your server calls. The access token carries tenant-wide and active-organization permissions. To resolve grants on one resource, call POST /api/check. Keycloak's Authorization Services can express resource-level permissions too; they come with a policy model to configure. Your application can use a policy enforcer to apply those decisions.

  • Growth costs usage, not headcount. Udibo's rate is $3 per 1,000 retained users past the allowance. Keycloak's software is $0 at any user count; what grows with it is the database, the cluster, and the time someone spends keeping both healthy.

  • The operational pieces come built. Signed webhooks with retries and redrive, at least 90 days of audit history exportable as CSV or NDJSON, your own email sender never billed, and a custom session policy on every plan. Keycloak can store login and admin events in its database when you enable the corresponding event-logging switches; configure their expiration, and provide an SMTP server for email. Those pieces are yours to keep working.

  • Your brand at the door with no theme to maintain. Your name, logo, and colors on the hosted pages with no vendor badge on any plan. Keycloak's themes are yours to write and to carry through each upgrade.

Why Keycloak may still be the right choice

  • SAML, LDAP, and Active Directory. Keycloak brokers to SAML 2.0 and OpenID Connect identity providers and federates users from LDAP and Active Directory. Udibo connects to any OpenID Connect provider with no per-connection fee and does not offer SAML, SCIM, or directory federation today.

  • Control of where it runs. Keycloak deploys on your servers or your Kubernetes cluster, and the user data stays there. Udibo Identity is a hosted service with no self-hosted edition. Its open-source part is the MIT-licensed @udibo/oauth2 package it is built on, a toolkit for running OAuth 2.0 and OpenID Connect authorization and resource servers inside an application you operate.

  • No license cost, with a supported build if you want one. Keycloak is Apache 2.0 with no per-user price. Red Hat build of Keycloak is included with Red Hat Runtimes, Application Foundations, and OpenShift Container Platform subscriptions. Its support policy provides at least two years of combined full and maintenance support for 26.x and three years starting with 27.x.

  • A deep extension model. Custom authenticators, mappers, and policies are part of Keycloak's design. WebAuthn second-factor and passkey sign-in require realm configuration; the recovery-code form is disabled in the default browser flow. Udibo's passkeys are a sign-in method a tenant turns on.

Pricing side by side

Keycloak publishes no price list: the software is free and the cost is what you run it on. The rows below put Udibo's pricing beside what Keycloak includes and what it leaves to you. Keycloak licensing and Red Hat entitlements were checked November 19, 2026. Udibo's pricing assumptions were checked October 2.

You needUdiboKeycloak
Free plan500 retained users, 25,000 hosted permission checks, 1,000 emailsThe software, Apache 2.0, at any user count; hosting is yours
First paid plan$5 a month plus usage: 5,000 users, 250,000 checks, 10,000 emails includedNone from the project; Red Hat build of Keycloak comes inside Red Hat Runtimes, Application Foundations, and OpenShift subscriptions, by quote
Multi-factor authenticationIncluded on FreeTOTP/HOTP, recovery codes, and WebAuthn are available; configure WebAuthn and recovery-code execution in the browser flow
Custom roles and permissionsIncluded on Free, across a tenant, an organization, or one resourceIncluded: realm and client roles, composite roles, groups, and Authorization Services
Organizations and membersNo capOrganizations are available but must be enabled for each realm
Remove vendor brandingIncluded on FreeThemes are yours to write and maintain
Custom session lifetimeIncluded on FreeIncluded: realm session and token timeouts
Enterprise SSO connectionsNo per-connection fee for OpenID Connect providers; no SAMLIncluded: OpenID Connect and SAML 2.0 brokering, LDAP and Active Directory federation
Audit or application log historyAt least 90 days on every planUser and admin events can be saved to your database when their logging switches are enabled; expiration is configurable
Sign-in email1,000 on Free and 10,000 on Standard, then $1 per 1,000; your own sender is counted but not billedSent through an SMTP server you configure and pay for
Users beyond the allowance$3 per 1,000 retained users$0 in software; more database and cluster capacity
Hosted permission checksFree: 25,000 checks, refused past that. Standard: 250,000, then $10.00 per 1,000,000, only if you raise your checks limitNo per-check charge; Authorization Services run on your cluster
Machine-to-machine tokensNo per-token charge; technical and abuse limits applyNo per-token charge; issued by the server you run

Three worked examples, with the same assumptions on both sides:

ScenarioUdiboKeycloak
Consumer app: 10,000 retained users, 5,000 sign-in emails, MFA on, your own branding$20 (Standard base plus 5,000 users above allowance)$0 in software, plus hosting, a database, an SMTP provider, and the hours to run and upgrade
B2B app: 200 users, 5 organizations of 30 members, custom roles, MFA$0 on Free, or $5 on Standard$0 in software; realms, organizations, groups, and roles configured and hosted by you
Consumer app at 100,000 retained usersAbout $290$0 in software; a clustered deployment sized by you, and the operations to match

Sources: keycloak.org, the production configuration guide, Red Hat's subscription note, and Udibo's pricing page. Both change; check the vendor's current page before you decide.

Cost at scale

Udibo's column uses retained users and Standard's published rates. Keycloak has no per-user license fee, so these head counts do not produce a hosted bill. Its infrastructure, email delivery, support, and operating work still cost money.

Retained usersUdiboKeycloak
1,000$5 (Standard)$0 in software; hosting and operations yours
10,000$20$0 in software; hosting and operations yours
100,000About $290$0 in software; hosting and operations yours
1,000,000About $2,990$0 in software; hosting and operations yours

There is no crossover, because self-hosted software has no per-user price. What you pay instead is the list from Keycloak's production guide: a production database and its backups, TLS, and proxy configuration if your deployment uses a proxy; a typical high-availability setup has two or more instances and distributed caches between nodes. Add upgrades, an SMTP provider, and the engineer's time; a Red Hat subscription if you want a supported build remains by quote. Whether that beats $20 or $2,990 a month depends on whether those servers and that person already exist, so price the engineer's hours before deciding.

What the integration looks like

With Udibo, register an application and its callback, send people to the hosted sign-in page, and finish the authorization-code flow on your server. Your backend holds the session and the browser gets a cookie, never a token. The first-login guide walks each checkpoint, and the organizations and permissions guides cover a person with a different role in each of two organizations.

With Keycloak, create a realm and a client, then integrate with an OpenID Connect or SAML library. Keycloak's own guidance is to prefer the libraries already in your application's ecosystem and to treat its client adapters as "a last resort" (securing applications). Both products put an OAuth 2.0 and OpenID Connect boundary between identity and your application, which is why a move in either direction is mostly an issuer change on the client side and mostly data on the server side.

Neither approach removes your responsibility to protect application data on the server. A valid session says who someone is; your backend still decides what they may read.

Where Udibo needs a closer look

Udibo does not currently offer SAML, SCIM, or LDAP or Active Directory federation, and Udibo Identity has no self-hosted edition. Organizations are flat, so Keycloak groups that nest will need a mapping rather than a copy. The @udibo/oauth2 package is a separate option for application-owned authentication, not a Keycloak realm you can run yourself. Customers administer tenants through the dashboard today; there is no self-serve management API credential for a script or backend. See the API guide. If your product needs a particular account-management screen, test that whole journey before committing; a successful login alone does not establish parity.

Moving an existing Keycloak application

Inventory realms, clients, roles, groups, mappers, authentication flows, and upstream identity providers. A realm, an organization, and a client application are different concepts; design an explicit mapping before moving data. Custom mappers and authenticators can change both claims and login behavior, so reproduce those dependencies in tests before changing token issuers.

Check the algorithm on the accounts you plan to migrate. Keycloak defaults to Argon2 outside FIPS deployments and PBKDF2-SHA512 in FIPS deployments. PBKDF2 hashes can migrate when they match Udibo's accepted encodings and work limits. For Argon2 accounts, offer a reset or operate a password migration endpoint to check returning users against your existing system. MFA enrollments and sessions do not move with a profile. If you only need a different client integration, an identity-provider migration may be unnecessary; evaluate the smallest change that meets the requirement. See migration planning and user import.

The Udibo export guide describes what you can take with you when leaving Udibo.

Try next: complete one Udibo login, then give a person two organizations and a different role in each. Before you have an account, the agent integration brief lets your coding assistant prepare the integration.

Frequently asked questions

Is Udibo cheaper than Keycloak? At the license line, no: Keycloak's software is free. The honest comparison is Udibo's bill against the servers, database, upgrade cycle, and engineer's hours that running Keycloak takes. For a team without an operations function, $5 to $20 a month is usually less than those hours; for a team that already runs a cluster, the answer can go the other way.

Does Udibo support SAML or LDAP like Keycloak? Not today. Udibo connects to any OpenID Connect provider with no per-connection fee. SAML federation, LDAP and Active Directory user federation, and SCIM provisioning are not available.

Can I move from Keycloak to Udibo? Profiles and social identities can be imported and linked by the provider's stable subject, and realms, groups, and roles need an explicit mapping onto organizations and roles. Password hashes depend on the algorithm. PBKDF2 hashes must satisfy Udibo's encoding and work limits. For Argon2, use a reset or check the old password through a migration endpoint. MFA enrollments and sessions do not move. See migration planning.

Is there a self-hosted Udibo? No. Udibo Identity is a hosted service with no self-hosted edition. Its open-source part is the MIT-licensed @udibo/oauth2 package it is built on, for building OAuth 2.0 and OpenID Connect authorization and resource servers into an application you operate. It is a toolkit rather than a server with an administration console, and it is not a self-hosted copy of Udibo Identity.

Last verified 2026-11-19.

View Markdown