Self-host ZITADEL with Levelrail
An identity and access management server with single sign on and OIDC.
- Authorzitadel
- LicenceAGPL-3.0
- Memory512 MiB
- Services2
How to self-host ZITADEL
-
Pull the images
2 images are pulled on your server.
Show images
postgres:17-alpineghcr.io/zitadel/zitadel:v4.16.0
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
4 secrets are generated and stored encrypted, 14 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
ZITADEL requirements
- Memory
- About 512 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then ZITADEL. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the ZITADEL docs page.
Deploy ZITADEL your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy ZITADEL from the CLI
levelrail-cli templates deploy zitadel --name my-zitadel Deploy ZITADEL with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/zitadel/deploy ZITADEL configuration
ZITADEL services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:17-alpine | none | zitadel_db_data -> /var/lib/postgresql/data |
| zitadel | ghcr.io/zitadel/zitadel:v4.16.0 | 8080 | none |
ZITADEL environment variables
| Variable | Service | Value |
|---|---|---|
| PGUSER | db | Preset by the template |
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| ZITADEL_DATABASE_POSTGRES_ADMIN_PASSWORD | zitadel | Generated at deploy |
| ZITADEL_DATABASE_POSTGRES_ADMIN_SSL_MODE | zitadel | Preset by the template |
| ZITADEL_DATABASE_POSTGRES_ADMIN_USERNAME | zitadel | Preset by the template |
| ZITADEL_DATABASE_POSTGRES_DATABASE | zitadel | Preset by the template |
| ZITADEL_DATABASE_POSTGRES_HOST | zitadel | Preset by the template |
Show all 18 variables
- ZITADEL_DATABASE_POSTGRES_PORTzitadelPreset by the template
- ZITADEL_DATABASE_POSTGRES_USER_PASSWORDzitadelGenerated at deploy
- ZITADEL_DATABASE_POSTGRES_USER_SSL_MODEzitadelPreset by the template
- ZITADEL_DATABASE_POSTGRES_USER_USERNAMEzitadelPreset by the template
- ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_REQUIREDzitadelPreset by the template
- ZITADEL_EXTERNALDOMAINzitadelPreset by the template
- ZITADEL_EXTERNALPORTzitadelPreset by the template
- ZITADEL_EXTERNALSECUREzitadelPreset by the template
- ZITADEL_MASTERKEYzitadelGenerated at deploy
- ZITADEL_TLS_ENABLEDzitadelPreset by the template
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: zitadel_db_data -> /var/lib/postgresql/data
ZITADEL FAQ
How much memory does ZITADEL need?
The catalog lists about 512 MiB of memory for ZITADEL across its 2 services.
Does ZITADEL run on arm64?
For ZITADEL, arm64 support is not confirmed; amd64 is unknown.
What licence is ZITADEL under?
ZITADEL is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does ZITADEL need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does ZITADEL bundle?
The template includes Postgres, running as its own service.
Which ports does ZITADEL use?
ZITADEL listens on port 8080 inside the stack.
Where does ZITADEL keep its data?
In a named volume: zitadel_db_data mounted at /var/lib/postgresql/data.
Can I deploy ZITADEL on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id zitadel for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:17-alpine, ghcr.io/zitadel/zitadel:v4.16.0 is what you deploy there.