Keycloak Self-Hosted
Identity and access management for application sign-on, federation and authorization.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Keycloak 26.8.2 security release review
The release fixes authentication, token, authorization, account-takeover, XSS and dependency issues.
Scope: Upstream Keycloak 26.8.2 security release; affected ranges and configurations vary by linked CVE.
Identity-provider, database, organization and authentication-flow settings determine applicability; a single blanket affected range is not established.
Action: Review the linked CVEs and migration guide, then install a fixed supported release.
Primary source · Reviewed 2026-11-17
What lands where
Supplied by
Vendor or project
Official server/container distribution or Kubernetes Operator; configure production database and TLS.
Runs in
Documented customer environment
Customer-operated identity server, database and optional clustered caches
- AWS: Customer cloud account
- Azure: Customer cloud account
- AWS
- Azure
Servers / containers
Operated by
Your team
Customer manages identity-server availability, configuration, updates, database and backups.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Keycloak supported configurations ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Keycloak supported configurations ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official server/container distribution or Kubernetes Operator; configure production database and TLS. |
|---|---|
| Infrastructure | Servers / containers The documented self-hosted runtime uses an application server or container with persistent state services. Hosted vendor editions are outside this listing. |
| Licensing model | Open Source / Open Core This entry covers the open-source Keycloak server. Separately purchased support or a commercial distribution does not change this entry’s code-license classification. |
| License | Open-source project; commercial support/distribution arrangements are separate |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
Keycloak acts as an OAuth 2.0, OpenID Connect and SAML identity server. Applications must be configured as compatible clients; this is not automatic SSO for every application.
Keycloak identity-provider role and client integration · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official container guide builds and starts an optimized Keycloak server image, with external database and hostname/TLS configuration for production. Select a released image and compatible database; start-dev and an ephemeral local database are separate evaluation paths. Operator deployment is another supported installation option.
Official self-hosted server/container deployment; configure production persistence and recovery separately · Source ↗ · Deployment artifact ↗ (26.8.2 upstream server distribution and matching container tag) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The HA sizing guide starts at about 1,250 MB per pod including realm caches and 10,000 cached sessions. Its tested password-login profile budgets 1 vCPU per 15 logins/second plus 150% CPU headroom; database capacity is separate. These are load-test assumptions, not a universal host minimum or a 100-user, 1 TB HA guarantee.
Official tested HA sizing model; login rate, password hashing, caches, topology and database determine capacity · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream application uses Apache License 2.0. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote.
Keycloak 26.8.2 upstream distribution; software terms only, excluding infrastructure and operations · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The official guides cover physical/virtual servers, containers and Kubernetes. Development defaults are separate from the production configuration. Connections to external identity providers are customer-configured; hosting the server does not eliminate those dependencies. Keycloak 26.8.2 is a security release addressing authentication, token issuance and revocation, authorization, account takeover, admin API, stored XSS, denial-of-service, and bundled Brotli issues. Review the migration guide and upgrade to 26.8.2 or later.
Category fit
- Identity & access management
- Identity and access management with SSO, identity brokering, federation and OpenID Connect/OAuth 2.0/SAML support.
Compare within Identity & access management
- authentikIdentity provider for centralized authentication and access policies across connected applications.
- AWS
- FusionAuth Self-HostedProprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Render
- HashiCorp Boundary EnterpriseCommercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.
- AWS
- Azure
- Google Cloud
- Infisical Self-HostedSelf-hosted secrets-management platform with application and machine-identity access workflows.
- AWS
- Google Cloud
- Vultr
- NetBird Self-Hosted Community EditionOpen-source zero-trust networking control plane self-hosted on a customer cloud VM.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- DigitalOcean
- Hetzner
- OpenBaoFoundation-governed secrets, key and certificate management with a customer-operated server.
- Linode
- OpenVPN Access ServerSelf-hosted business VPN and network-access server deployed in the customer's cloud account.
- AWS
- Azure
- Google Cloud
- Teleport Enterprise Self-HostedCommercial access platform deployed as a high-availability Teleport cluster in the customer's cloud.
- AWS
- Azure
- Google Cloud
Showing 8 of 10 other listings in Identity & access management. These products address related workflows; read their category-fit notes before comparing scope. See all of Identity & access management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Container deployment ↗www.keycloak.org
- Installation and production guide index ↗www.keycloak.org
- Identity capabilities ↗www.keycloak.org
- Keycloak 26.8.2 security release ↗www.keycloak.org
- Keycloak 26.8.2 release details ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Keycloak supported configurations ↗ · AWS, Azure
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project names Amazon EKS and Azure Kubernetes Service as non-OpenShift Kubernetes deployments supported on a best-effort basis. Distribution-specific issues may fall outside that support; check the documented Kubernetes API versions.
- Keycloak supported configurations ↗ · AWS, Azure
- Infrastructure evidenceChecked
- Licensing evidenceChecked