Self-host Infisical with Levelrail
An open-source secrets manager to centralize API keys, database credentials, and app config.
- AuthorInfisical
- LicenceMIT
- Memory512 MiB
- Archarm64
- Services3
How to self-host Infisical
-
Pull the images
3 images are pulled on your server.
Show images
postgres:16-alpineinfisical/infisical:v0.154.6redis:7-alpine
-
Create the app
3 services start in a single Compose app, with 2 named volume mounts for your data, on port 8080.
-
Fill in the secrets
4 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.
Infisical requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 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 port 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 Infisical. 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 Infisical docs page.
Deploy Infisical your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Infisical from the CLI
levelrail-cli templates deploy infisical --name my-infisical Deploy Infisical with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/infisical/deploy Infisical configuration
Infisical services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | infisical_db_data -> /var/lib/postgresql/data |
| infisical | infisical/infisical:v0.154.6 | 8080 | none |
| redis | redis:7-alpine | none | infisical_redis_data -> /data |
Infisical 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 |
| AUTH_SECRET | infisical | Generated at deploy |
| DB_CONNECTION_URI | infisical | Generated at deploy |
| ENCRYPTION_KEY | infisical | Generated at deploy |
| REDIS_URL | infisical | Preset by the template |
| SITE_URL | infisical | Preset by the template |
Ports and volumes
- Ports
- 8080
- Volumes
- 2 named mounts: infisical_db_data -> /var/lib/postgresql/data, infisical_redis_data -> /data
Infisical FAQ
How much memory does Infisical need?
The catalog lists about 512 MiB of memory for Infisical across its 3 services.
Does Infisical run on arm64?
For Infisical, an arm64 image is published; amd64 is image published.
What licence is Infisical under?
Infisical is licensed under MIT, which is permissive, with few conditions on reuse.
Does Infisical need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Infisical bundle?
The template includes Postgres and Redis, running as its own service.
Which ports does Infisical use?
Infisical listens on port 8080 inside the stack.
Where does Infisical keep its data?
In named volumes: infisical_db_data mounted at /var/lib/postgresql/data and infisical_redis_data mounted at /data.
Can I deploy Infisical 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 infisical for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, infisical/infisical:v0.154.6, redis:7-alpine is what you deploy there.