Editorial take
Why it stands out
Compare Okta or Auth0 when managed uptime and support contracts matter more than license cost; compare Authentik or Zitadel for lighter-weight OSS alternatives.
Tool profile
Open-source identity and access management you run yourself: realms, brokers, SAML/OIDC, and user federation for teams that own the metal.
Regulated or on-prem environments that forbid external auth UIs
Keycloak is the default self-hosted choice when you need a full identity server—realms, clients, themes, social brokering, SAML/OIDC federation, and user storage adapters—without SaaS licensing. You operate upgrades, scaling, and backups, which buys control and data residency at the cost of engineering time. It pairs well with Kubernetes and enterprise Java ecosystems; it is slower to value than Clerk if you just need a login button on a landing page.
Quick fit
Editorial take
Compare Okta or Auth0 when managed uptime and support contracts matter more than license cost; compare Authentik or Zitadel for lighter-weight OSS alternatives.
What it does well
Primary use cases
Fit notes
Pricing snapshot
Software is free under open-source licenses; you pay for compute, storage, support staff, and optionally vendor support (e.g., Red Hat build)—not a per-seat SaaS fee.