compare
Ory Hydra vs ZITADEL
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Ory Hydra | ZITADEL |
|---|---|---|
| Language | Go | Go |
| Licence | Apache-2.0 | AGPL-3.0 |
| Stars | 18k | 15k |
| Latest | v26.2.0 | v4.19.4 |
| Last push | 2026-07-29 | 2026-10-06 |
| Release cadence | about 294 days between releases | about 2 days between releases |
| Active contributors | 8 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 →
PartialOry HydraAn OAuth 2.0 and OpenID Connect server; login, consent and users stay in your own app.
Full replacementZITADELMulti-tenant login, OpenID Connect, SAML and passkeys, built for B2B apps.
Ory Hydra
- v26.2.02026-03-20v26.2.0
- v25.4.02025-11-07v25.4.0 brings first-class support for agentic authorization with the Device Authorization Grant (RFC 8628) and OAuth 2…
- v2.3.02025-01-17We’re thrilled to announce the release of Ory Hydra 2.3.0! This version comes packed with graceful token refresh, perfo…
- v2.2.02024-02-12!Ory Hydra 2.2.0
- v2.2.0-rc.32023-08-16Introduces logout compatibility with Ory Kratos.pre-release
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
Ory Hydra
unsigned The latest release, v26.2.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