Identity & access management on Railway
Application sign-on, identity federation and access controls.
1 documented option on Railway. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| ZITADEL Self-Hosted | Railway | Customer-operated Servers / containers | Open Source / Open Core GNU Affero General Public License version 3 for the reviewed upstream code; commercial products and agreements are separate. | Deploy the official Docker Compose stack with ZITADEL API, login application, reverse proxy and PostgreSQL, then apply the documented hardening configuration. | Customer manages identity storage, cryptographic keys, proxy/TLS, backups, email/SMS providers and updates.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-12 |
Deployment evidence and category fit
ZITADEL Self-Hosted
Application identity and access management with user/organization administration and configured authentication flows.
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.
- ZITADEL community deployment template on 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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Deployment and procurement checks
- Project networking
- Private networking connects services inside a project environment using encrypted tunnels and internal DNS. This project boundary does not give the customer ownership of the underlying infrastructure account. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: Railway workspace, project and environment; platform-managed infrastructure. Access: Workspace/project access and scoped deployment tokens. Network: Project/environment private networking with separately exposed public services.
Provider documentation ↗ · Guidance reviewed 2026-11-12. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings