Self-host Temporal with Levelrail
Durable workflow execution: write long-running business logic as code and let Temporal survive failures.
- Authortemporalio
- LicenceMIT
- Memory1 GiB
- Archarm64
- Services3
How to self-host Temporal
-
Pull the images
3 images are pulled on your server.
Show images
postgres:16-alpinetemporalio/auto-setup:1.29.7temporalio/ui:2.54.1
-
Create the app
3 services start in a single Compose app, with 1 named volume mount for your data, on ports 7233, 8080.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 7 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.
Temporal requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 7233, 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes ports 7233, 8080 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Temporal. 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 Temporal docs page.
Deploy Temporal your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Temporal from the CLI
levelrail-cli templates deploy temporal --name my-temporal Deploy Temporal with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/temporal/deploy Temporal configuration
Temporal services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | temporal_db_data -> /var/lib/postgresql/data |
| temporal | temporalio/auto-setup:1.29.7 | 7233 | none |
| temporal-ui | temporalio/ui:2.54.1 | 8080 | none |
Temporal environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Preset by the template |
| DB | temporal | Preset by the template |
| DB_PORT | temporal | Preset by the template |
| POSTGRES_PWD | temporal | Generated at deploy |
| POSTGRES_SEEDS | temporal | Preset by the template |
| POSTGRES_USER | temporal | Preset by the template |
Show all 9 variables
- TEMPORAL_ADDRESStemporal-uiPreset by the template
Ports and volumes
- Ports
- 7233, 8080
- Volumes
- 1 named mount: temporal_db_data -> /var/lib/postgresql/data
Temporal FAQ
How much memory does Temporal need?
The catalog lists about 1 GiB of memory for Temporal across its 3 services.
Does Temporal run on arm64?
For Temporal, an arm64 image is published; amd64 is image published.
What licence is Temporal under?
Temporal is licensed under MIT, which is permissive, with few conditions on reuse.
Does Temporal need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Temporal bundle?
The template includes Postgres, running as its own service.
Which ports does Temporal use?
Temporal listens on ports 7233 and 8080 inside the stack.
Where does Temporal keep its data?
In a named volume: temporal_db_data mounted at /var/lib/postgresql/data.
Can I deploy Temporal on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Temporal, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, temporalio/auto-setup:1.29.7, temporalio/ui:2.54.1 is what you deploy there.