Self-host VoidAuth with Levelrail
A self-hosted single sign-on and identity provider with OIDC, passkeys, user invitations and self-service profiles, backed by Postgres. Create the first admin from the invitation link printed in the container log.
- Authorvoidauth
- LicenceAGPL-3.0-or-later
- Memory384 MiB
- Services2
How to self-host VoidAuth
-
Pull the images
2 images are pulled on your server.
Show images
postgres:17.11-alpinevoidauth/voidauth:1.19.1
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 3000.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 3 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
- Read the first admin invitation link from the voidauth container log, open it and set the admin password.
VoidAuth requirements
- Memory
- About 384 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-or-later, 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 VoidAuth. 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 VoidAuth docs page.
Deploy VoidAuth your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy VoidAuth from the CLI
levelrail-cli templates install voidauth --name my-voidauth Deploy VoidAuth with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/voidauth/install \
-d '{
"name": "my-voidauth"
}' VoidAuth configuration
VoidAuth services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:17.11-alpine | none | pgdata -> /var/lib/postgresql/data |
| voidauth | voidauth/voidauth:1.19.1 | 3000 | config -> /app/config |
VoidAuth environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_PASSWORD | db | Generated at deploy |
| APP_URL | voidauth | Preset by the template |
| DB_ADAPTER | voidauth | Preset by the template |
| DB_HOST | voidauth | Preset by the template |
| DB_PASSWORD | voidauth | Generated at deploy |
| STORAGE_KEY | voidauth | Generated at deploy |
Ports and volumes
- Ports
- 3000
- Volumes
- 2 named mounts: pgdata -> /var/lib/postgresql/data, config -> /app/config
VoidAuth FAQ
How much memory does VoidAuth need?
The catalog lists about 384 MiB of memory for VoidAuth across its 2 services.
Does VoidAuth run on arm64?
For VoidAuth, arm64 support is not confirmed; amd64 is unknown.
What licence is VoidAuth under?
VoidAuth is licensed under AGPL-3.0-or-later, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does VoidAuth need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does VoidAuth bundle?
The template includes Postgres, running as its own service.
Which ports does VoidAuth use?
VoidAuth listens on port 3000 inside the stack.
Where does VoidAuth keep its data?
In named volumes: pgdata mounted at /var/lib/postgresql/data and config mounted at /app/config.
Can I deploy VoidAuth 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 VoidAuth, 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, voidauth/voidauth:1.19.1 is what you deploy there.