Self-host Svix with Levelrail
A webhooks sending service with retries, signatures, a message log and an HTTP API, backed by Postgres and Redis. Create applications and send events through the API with a token signed by your JWT secret.
- Authorsvix
- LicenceMIT
- Memory384 MiB
- Services3
How to self-host Svix
-
Pull the images
3 images are pulled on your server.
Show images
postgres:17.11-alpineredis:7.4.7-alpinesvix/svix-server:v1.105.0
-
Create the app
3 services start in a single Compose app, with 2 named volume mounts for your data, on port 8071.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 4 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.
After the first start
- Create an API token with the svix-server jwt generate command inside the container, then call the API at the published port.
Svix requirements
- Memory
- About 384 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8071
- 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.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Svix. 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 Svix docs page.
Deploy Svix your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Svix from the CLI
levelrail-cli templates install svix --name my-svix Deploy Svix with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/svix/install \
-d '{
"name": "my-svix"
}' Svix configuration
Svix services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:17.11-alpine | none | pgdata -> /var/lib/postgresql/data |
| redis | redis:7.4.7-alpine | none | redis_data -> /data |
| svix | svix/svix-server:v1.105.0 | 8071 | none |
Svix 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 |
| SVIX_DB_DSN | svix | Generated at deploy |
| SVIX_JWT_SECRET | svix | Generated at deploy |
| SVIX_REDIS_DSN | svix | Preset by the template |
| WAIT_FOR | svix | Preset by the template |
Ports and volumes
- Ports
- 8071
- Volumes
- 2 named mounts: pgdata -> /var/lib/postgresql/data, redis_data -> /data
Svix FAQ
How much memory does Svix need?
The catalog lists about 384 MiB of memory for Svix across its 3 services.
Does Svix run on arm64?
For Svix, arm64 support is not confirmed; amd64 is unknown.
What licence is Svix under?
Svix is licensed under MIT, which is permissive, with few conditions on reuse.
Does Svix need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Svix bundle?
The template includes Postgres and Redis, running as its own service.
Which ports does Svix use?
Svix listens on port 8071 inside the stack.
Where does Svix keep its data?
In named volumes: pgdata mounted at /var/lib/postgresql/data and redis_data mounted at /data.
Can I deploy Svix 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 Svix, 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:17.11-alpine, redis:7.4.7-alpine, svix/svix-server:v1.105.0 is what you deploy there.