compare
Keycloak vs ZITADEL
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Keycloak | ZITADEL |
|---|---|---|
| Language | Java | Go |
| Licence | Apache-2.0 | AGPL-3.0 |
| Stars | 37k | 15k |
| Latest | 26.8.0 | v4.19.4 |
| Last push | 2026-10-06 | 2026-10-06 |
| Release cadence | about 14 days between releases | about 2 days between releases |
| Active contributors | 97+ commit authors on the default branch in the last 90 days | 20 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace Auth0. Alternatives to Auth0 →
Full replacementKeycloakHosted login pages, social login and OpenID Connect for your applications.
Full replacementZITADELMulti-tenant login, OpenID Connect, SAML and passkeys, built for B2B apps.
Both replace Okta. Alternatives to Okta →
Full replacementKeycloakSSO over OpenID Connect and SAML, user federation with LDAP and Active Directory, and MFA.
PartialZITADELSSO for your own applications rather than a workforce app catalogue.
Keycloak
ZITADEL
- v4.19.42026-10-01actions: set instance ID in async execution worker context (#12730) (03a2469), closes #11985
- v4.19.32026-09-29query: index users14 by instance and org (#12830) (d378dea), closes #12826
- v4.19.22026-09-28This release fixes three security vulnerabilities. We recommend all 4.x deployments upgrade.
- v4.19.12026-09-23setup step 79 batch unique constraint owner backfill (#12803) (42cdd5d)
- v4.19.02026-09-23eventstore: omit owners on empty unique constraint inserts (#12785) (6308539), closes #12740 #12780 #12740
Keycloak
unsigned The latest release, 26.8.0, carries no signature GitHub could verify.
Loading the security report
ZITADEL
✓ signed The latest release, v4.19.4, carries a signature GitHub verified.
Loading the security report