Self-host Kestra with Levelrail
An event driven workflow orchestrator where flows are defined in YAML.
- Authorkestra-io
- LicenceApache-2.0
- Memory1.5 GiB
- Services2
How to self-host Kestra
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16-alpinekestra/kestra:v2.0.10
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 8080.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 2 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.
Kestra requirements
- Memory
- About 1.5 GiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive 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 Kestra. 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 Kestra docs page.
Deploy Kestra your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Kestra from the CLI
levelrail-cli templates deploy kestra --name my-kestra Deploy Kestra with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/kestra/deploy Kestra configuration
Kestra services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | db_data -> /var/lib/postgresql/data |
| kestra | kestra/kestra:v2.0.10 | 8080 | kestra_data -> /app/storage |
Kestra 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 |
| KESTRA_CONFIGURATION | kestra | Generated at deploy |
Ports and volumes
- Ports
- 8080
- Volumes
- 2 named mounts: db_data -> /var/lib/postgresql/data, kestra_data -> /app/storage
Kestra FAQ
How much memory does Kestra need?
The catalog lists about 1.5 GiB of memory for Kestra across its 2 services.
Does Kestra run on arm64?
For Kestra, arm64 support is not confirmed; amd64 is unknown.
What licence is Kestra under?
Kestra is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Kestra need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Kestra bundle?
The template includes Postgres, running as its own service.
Which ports does Kestra use?
Kestra listens on port 8080 inside the stack.
Where does Kestra keep its data?
In named volumes: db_data mounted at /var/lib/postgresql/data and kestra_data mounted at /app/storage.
Can I deploy Kestra 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 kestra for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, kestra/kestra:v2.0.10 is what you deploy there.