compare
Hanko vs ZITADEL
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Hanko | ZITADEL |
|---|---|---|
| Language | Go | Go |
| Licence | Other | AGPL-3.0 |
| Stars | 9k | 15k |
| Latest | backend/v3.1.0 | v4.19.4 |
| Last push | 2026-10-06 | 2026-10-06 |
| Release cadence | about 59 days between releases | about 2 days between releases |
| Active contributors | 7 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 →
PartialHankoPasskeys, passwords and social login for your applications, without enterprise SAML.
Full replacementZITADELMulti-tenant login, OpenID Connect, SAML and passkeys, built for B2B apps.
Hanko
- backend/v3.1.02026-10-01Hanko v3.1
- backend/v3.0.42026-07-27Hanko v3: Multitenancy
- backend/v2.7.02026-06-05Hanko v2.7: Firebase User and Password Hashes Import
- backend/v2.6.02026-06-05Hanko v2.6: Inactivity Logout
- backend/v2.5.02026-03-03Hanko 2.5
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
Hanko
✓ signed The latest release, backend/v3.1.0, carries a signature GitHub verified.
Loading the security report
ZITADEL
✓ signed The latest release, v4.19.4, carries a signature GitHub verified.
Loading the security report