ZITADEL Self-Hosted
Application identity platform that can run as a self-operated service with its own PostgreSQL database.
6 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 →
ZITADEL v4.20.5 Login V2 MFA-enrolment fix
v4.20.5 requires the configured second factor before a session may add a new authenticator.
Scope: ZITADEL Login V2 authenticator enrolment.
The path requires an account with an existing second factor and a first-factor-only session that could previously enrol another authenticator.
Action: Upgrade to v4.20.5 or later and test MFA enrolment and recovery flows.
Primary source · Fix commit · Reviewed 2026-11-19
What lands where
Supplied by
Vendor or project
Deploy the official Docker Compose stack with ZITADEL API, login application, reverse proxy and PostgreSQL, then apply the documented hardening configuration.
Runs in
Documented customer environment
Customer-operated Go API, login application and PostgreSQL behind a configured proxy
- Railway: Customer platform workspace
- Railway
Servers / containers
Operated by
Your team
Customer manages identity storage, cryptographic keys, proxy/TLS, backups, email/SMS providers and updates.
Deployment boundaries by provider
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
ZITADEL community deployment template on Railway ↗ · 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 | Deploy the official Docker Compose stack with ZITADEL API, login application, reverse proxy and PostgreSQL, then apply the documented hardening configuration. |
|---|---|
| Infrastructure | Servers / containers Customer-operated Go API, login application and PostgreSQL behind a configured proxy. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. |
| Licensing model | Open Source / Open Core GNU Affero General Public License version 3 for the reviewed upstream code; commercial products and agreements are separate. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms. |
| License | GNU Affero General Public License version 3 for the reviewed upstream code; commercial products and agreements 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.
6 of 12 fields researched (50%) · 6 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
ZITADEL can broker external OIDC and SAML identity providers for applications, with instance-wide or organization-specific login policies. Configure permitted providers, callbacks, claims and account linking/creation policy. Being an identity platform does not automatically integrate every application or establish SCIM lifecycle provisioning.
ZITADEL identity-brokering role and external IdP configuration; not an assertion that every client is preconfigured · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
v4.20.5 fixes Login V2 authenticator enrolment accepting a first-factor-only session despite an existing second factor. Upgrade and test MFA enrolment.
ZITADEL Login V2 authenticator enrolment · Source ↗ · Fix commit ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The Compose guide deploys API, login application, reverse proxy and PostgreSQL and then describes hardening. It is a homelab/semi-production starting point, not a full HA architecture.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The production guide separates an approximately 512 MB application process from database capacity and password-hashing peaks. Its minimal HA reference uses three nodes at 4 CPU cores and 16 GB RAM each, or about 8 GB without nonessential telemetry services. Database sizing and actual login/request load still need validation; 512 MB is not an HA stack minimum.
Current self-hosted production/HA reference, distinct from application-process memory · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream application uses GNU AGPLv3. 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.
ZITADEL v4.20.5 upstream source; software terms only, excluding infrastructure and operations · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
ZITADEL v4.20.5 was published November 18, 2026. It requires the configured second factor before a session may add an authenticator, closing a Login V2 MFA-bypass path.
Upstream ZITADEL v4 release · Source ↗ · Prior reviewed release context ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (6 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.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
The Compose guide is a starting point for a homelab or semi-production installation. The current contribution guide states that engineering focus on next-generation work limits community PR review capacity for this codebase; evaluate the supported release roadmap. External identity and message providers remain separate. ZITADEL v4.20.4 enables PKCE by default for Google, GitHub, GitLab, and Azure AD identity providers and hardens SMS OTP and password history. Revalidate external IdP callbacks and authentication policy after upgrading. ZITADEL v4.20.5 fixes a Login V2 MFA bypass in which a first-factor-only session could add a new authenticator even when a second factor was already configured. Upgrade and verify authenticator-enrolment policy.
Community & maintenance
Official project information reports more than 200 contributors, and the upstream release history records continuing 2026 maintenance. Current contribution guidance explicitly discloses reduced review capacity while the team builds its next generation.
Category fit
- Identity & access management
- Application identity and access management with user/organization administration and configured authentication flows.
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
- Keycloak Self-HostedIdentity and access management for application sign-on, federation and authorization.
- AWS
- Azure
- 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
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
- Official installation and runtime ↗zitadel.com
- Upstream project and capabilities ↗github.com
- Current upstream license ↗raw.githubusercontent.com
- ZITADEL v4.20.4 release ↗github.com
- ZITADEL v4.20.5 release ↗github.com
- ZITADEL authenticator-enrolment fix ↗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.
- ZITADEL community deployment template on Railway ↗ · Railway
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community template uses official ZITADEL server and login images with PostgreSQL in a customer Railway project. Review server/login version alignment, initial administrator credentials and the production checklist; Login V2 requires additional service-user configuration. This is separate from ZITADEL Cloud.
- ZITADEL community deployment template on Railway ↗ · Railway
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Contributor community ↗zitadel.com
- Current release maintenance ↗github.com
- Current contribution-capacity caveat ↗raw.githubusercontent.com