Self-host Vaultwarden with Levelrail
VerifiedA lightweight, self-hosted password manager server compatible with the Bitwarden clients.
- Authordani-garcia
- LicenceAGPL-3.0-only
- Memory256 MiB
- Archarm64
- Services1
How to self-host Vaultwarden
-
Pull the images
One image is pulled on your server.
Show images
vaultwarden/server:1.32.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 80.
-
Fill in the secrets
1 secret is generated and stored encrypted, 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.
Vaultwarden requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-only, network copyleft (agpl) license
- Verified. Verified on arm64 with image tag 1.32.1. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 80 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 Vaultwarden. 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 Vaultwarden docs page.
Deploy Vaultwarden your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Vaultwarden from the CLI
levelrail-cli templates deploy vaultwarden --name my-vaultwarden Deploy Vaultwarden with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/vaultwarden/deploy Vaultwarden configuration
Vaultwarden services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| vaultwarden | vaultwarden/server:1.32.1 | 80 | vaultwarden_data -> /data |
Vaultwarden environment variables
| Variable | Service | Value |
|---|---|---|
| ADMIN_TOKEN | vaultwarden | Generated at deploy |
Ports and volumes
- Ports
- 80
- Volumes
- 1 named mount: vaultwarden_data -> /data
Vaultwarden FAQ
How much memory does Vaultwarden need?
The catalog lists about 256 MiB of memory for Vaultwarden.
Does Vaultwarden run on arm64?
For Vaultwarden, arm64 is tested; amd64 is image published.
What licence is Vaultwarden under?
Vaultwarden is licensed under AGPL-3.0-only, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Vaultwarden need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Vaultwarden use?
Vaultwarden listens on port 80 inside the stack.
Where does Vaultwarden keep its data?
In a named volume: vaultwarden_data mounted at /data.
Can I deploy Vaultwarden 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 vaultwarden for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image vaultwarden/server:1.32.1 is what you deploy there.