Keycloak
keycloak.org
- Free plan
- Windows
- Linux
- Web
- API
- Self-hosted
What Keycloak is
Keycloak is free, open-source identity and access management software for adding authentication to applications and secure services. Its single sign-on lets users authenticate once and access several applications, with coordinated sign-out. Keycloak supports OpenID Connect, OAuth 2.0 and SAML, and can broker authentication through external identity providers and social networks including Google, GitHub, Facebook and Twitter. It synchronizes users from LDAP and Active Directory and can bridge authentication through Kerberos. Authentication methods include passwords, passkeys, X.509 certificates and two-factor authentication using TOTP, HOTP and recovery codes. Administrators can define fine-grained authorization policies. Deployment options include a server distribution, container images for Docker, Podman, Kubernetes and OpenShift, and a Kubernetes/OpenShift operator. The project uses the Apache License, Version 2.0. Some features are disabled by default, and preview features require enabling and may not be generally supported.
Who it suits
Keycloak suits teams that need self-managed authentication, SSO, directory synchronization, federation and policy controls across web, Linux, Windows, API or self-hosted environments. It is especially relevant when open-source licensing and deployment control matter.
Good to know, and what to watch
- Free Apache-licensed open-source project
- Supports OpenID Connect, OAuth 2.0 and SAML
- Multiple MFA methods including passkeys
- LDAP, Active Directory and Kerberos integration
- Container and Kubernetes deployment options
- Some features are disabled by default
- Preview features may lack general support
- No free trial because the software is already free
- Long-term support is recommended through Red Hat build
Plans
Every plan and priceKeycloak
Open source
The verdict
Keycloak provides broad standards support, federation, MFA and deployment flexibility without a software charge. Review feature status and support requirements before operating it in production.
What the maker publishes
- Access-control types
- Policies can implement ABAC, RBAC and context-based access control. source
- Authentication
- Keycloak supports passkeys, passwords, X.509 certificates, and two-factor authentication with recovery codes and TOTP/HOTP. source
- Authorization
- Administrators can define fine-grained authorization policies for applications and services. source
- Authorization model
- Supports fine-grained authorization policies and multiple access-control mechanisms. source
- AuthZEN interoperability
- Can act as an AuthZEN-compatible policy decision point (experimental). source
- Centralized policy management
- Provides centralized management of resources, permissions and policies. source
- Deployment
- The downloads page provides a server distribution, a container image for Docker, Podman, Kubernetes, and OpenShift, and an operator for Kubernetes and OpenShift. source
- Deployment options
- Distributed as a downloadable server and container images for Docker, Podman, Kubernetes and OpenShift. source
- Feature status
- Some features are disabled by default, and the project notes that preview features require enabling and may not be generally available as supported features. source
- Identity brokering
- Keycloak can authenticate users through external OpenID Connect or SAML identity providers and social networks including Google, GitHub, Facebook, and Twitter. source
- Licensing
- The Keycloak project is licensed under the Apache License, Version 2.0. source
- Open-source availability
- The project identifies itself as open source. source
- Policy decision point
- Authorization requests are evaluated by a distributable policy decision point. source
- Policy enforcement
- Policy enforcement points at resource servers enforce returned authorization decisions. source
- Project home
- Keycloak is an open-source identity and access management project accepted into the CNCF as an incubating project in April 2023. source
- Protocols
- Keycloak supports OpenID Connect, OAuth 2.0, and SAML. source
- Purpose
- Keycloak adds authentication to applications and secure services, so they do not need to store or authenticate users themselves. source
- Resource and scope granularity
- Permissions can protect resources and scopes, with scopes representing actions or attributes. source
- REST and API integration
- Offers a RESTful API and a Java Authorization Client API for programmatic checks. source
- Security reporting
- The project asks vulnerability reporters to email its security team and says it aims to acknowledge reports within seven business days. source
- Single sign-on
- Users can sign in once through Keycloak to access multiple applications and sign out of them together. source
- Support
- The project recommends Red Hat build of Keycloak for users who cannot regularly upgrade and need long-term support for specific versions. source
- User federation
- Keycloak can synchronize users from LDAP and Active Directory servers and bridge authentication through Kerberos. source
Checked against the maker's pages on 18 Nov 2026.