
Deploy Zitadel
[2026-10-27] Zitadel v4.20, classic login kept (see README).
Just deployed
/var/lib/postgresql/data
Zitadel-railway
Just deployed
Are you searching for a user management tool that is quickly set up like Auth0 and open source like Keycloak?
Do you have a project that requires multi-tenant user management with self-service for your customers?
Look no further — ZITADEL is the identity infrastructure, simplified for you.
This template spins up Zitadel instance and connects it to a Postgres database. First time you login, you can access the instance by visting your railway public url and with the following credentials:
root@email.com RootPassword1!
Update 2026-10-27
- Pinned Zitadel v4.20.0 (was floating latest).
- BREAKING (upstream, Zitadel v4): new instances default to Login V2, which is served by a separate container (ghcr.io/zitadel/zitadel-login) that this template does not run - logins were 404ing. The template now sets ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_REQUIRED=false to keep the built-in v1 login. Set it to true only if you deploy the login container yourself.
- Postgres password is now autogenerated per deploy (was a fixed default), DB traffic moved to private networking, Postgres pinned to 17.
Template Content
Zitadel-railway
leonardochappuis/Zitadel-railway
