
# Identity & access management on Railway

Compare documented Identity & access management deployments on Railway, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/identity-access-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Railway workspace, project and environment; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.railway.com/projects (checked 2026-11-20).
- Network: Project/environment private networking with separately exposed public services
- Identity and access: Workspace/project access and scoped deployment tokens
- Installation guidance: Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
- Guidance source: https://docs.railway.com/projects
- Guidance reviewed: 2026-11-12


### 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.
Source: https://docs.railway.com/networking/private-networking (reviewed 2026-11-14).

The listings below have evidence for Railway. Read each cloud evidence note for the applicable package, edition and support qualifications.

1 listing.


## ZITADEL Self-Hosted

Application identity platform that can run as a self-operated service with its own PostgreSQL database.

- Listing: https://launchinyourcloud.com/directory/zitadel/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU Affero General Public License version 3 for the reviewed upstream code; commercial products and agreements are separate.
- Licensing model: open-source
- Installation: Deploy the official Docker Compose stack with ZITADEL API, login application, reverse proxy and PostgreSQL, then apply the documented hardening configuration.
- Architecture: Customer-operated Go API, login application and PostgreSQL behind a configured proxy
- Operations: Customer manages identity storage, cryptographic keys, proxy/TLS, backups, email/SMS providers and updates.
- Product website: https://zitadel.com/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

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.


### Category fit

- identity-access-management: Application identity and access management with user/organization administration and configured authentication flows.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/zitadel-1 (checked 2026-11-12). 


### Cloud deployment evidence

- ZITADEL community deployment template on Railway (railway): https://railway.com/deploy/zitadel-1
  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.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-10.

- Contributor community: https://zitadel.com/about

- Current release maintenance: https://github.com/zitadel/zitadel/releases

- Current contribution-capacity caveat: https://raw.githubusercontent.com/zitadel/zitadel/main/CONTRIBUTING.md

### Sources

- Official installation and runtime: https://zitadel.com/docs/self-hosting/deploy/compose

- Upstream project and capabilities: https://github.com/zitadel/zitadel

- Current upstream license: https://raw.githubusercontent.com/zitadel/zitadel/main/LICENSE

- ZITADEL v4.20.4 release: https://github.com/zitadel/zitadel/releases/tag/v4.20.4

- ZITADEL v4.20.5 release: https://github.com/zitadel/zitadel/releases/tag/v4.20.5

- ZITADEL authenticator-enrolment fix: https://github.com/zitadel/zitadel/commit/59827a8ec6dd0c23acbba5d0ebdf41fdc857d66c

### Licensing sources

- https://raw.githubusercontent.com/zitadel/zitadel/main/LICENSE

### Infrastructure sources

- https://zitadel.com/docs/self-hosting/deploy/compose


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. 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. Scope: ZITADEL identity-brokering role and external IdP configuration; not an assertion that every client is preconfigured. Source: https://zitadel.com/docs/guides/integrate/identity-providers/introduction (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. v4.20.5 fixes Login V2 authenticator enrolment accepting a first-factor-only session despite an existing second factor. Upgrade and test MFA enrolment. Scope: ZITADEL Login V2 authenticator enrolment. Source: https://github.com/zitadel/zitadel/releases/tag/v4.20.5 (reviewed 2026-11-19). Supporting source: Fix commit — https://github.com/zitadel/zitadel/commit/59827a8ec6dd0c23acbba5d0ebdf41fdc857d66c.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://zitadel.com/docs/self-hosting/deploy/compose (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. 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. Scope: Current self-hosted production/HA reference, distinct from application-process memory. Source: https://zitadel.com/docs/self-hosting/manage/production (reviewed 2026-11-20).

- License pricing: Documented. 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. Scope: ZITADEL v4.20.5 upstream source; software terms only, excluding infrastructure and operations. Source: https://github.com/zitadel/zitadel/blob/v4.20.5/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream ZITADEL v4 release. Source: https://github.com/zitadel/zitadel/releases/tag/v4.20.5 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/zitadel/zitadel/releases/tag/v4.20.4.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- ZITADEL v4.20.5 Login V2 MFA-enrolment fix (security-advisory): v4.20.5 requires the configured second factor before a session may add a new authenticator. Scope: ZITADEL Login V2 authenticator enrolment. Conditions: 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. Source: https://github.com/zitadel/zitadel/releases/tag/v4.20.5; reviewed 2026-11-19. Supporting source: Fix commit — https://github.com/zitadel/zitadel/commit/59827a8ec6dd0c23acbba5d0ebdf41fdc857d66c.



