Self-host Vault on a VPS
HashiCorp Vault for secrets storage, encryption as a service, and dynamic credentials, with integrated Raft storage. Vault is reachable only from services in this project at vault:8200 over plain HTTP and is not published on the host. It starts uninitialized and sealed: run vault operator init and vault operator unseal from the app console, keep the unseal keys and root token offline, and put a domain with HTTPS in front of it before anything outside this project talks to it.
levelrail-cli templates deploy vault --name my-vaultSpecification
- Status
- Listed
- Category
- Security
- Services
- vault
- Ports
- 8200
- Volumes
- 1
- Memory
- about 256 MiB
- arm64
- image published
- amd64
- image published
- Settings to fill in
- none
- License
- Source available, BUSL-1.1
About Vault
HashiCorp Vault for secrets storage, encryption as a service, and dynamic credentials, in file-storage mode. Runs as a single container from the vault image, listening on port 8200 and keeps its data in named volumes.
What it deploys
Vault runs as one service in a single Compose app, listening on port 8200, with 1 named volume mount.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| vault | hashicorp/vault | 2.1.2 | 8200 | vault_data -> /vault/file |
Before you install
- CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
Settings and environment
You do not have to fill in anything. Values are never shown here.
| Service | Variable | Value |
|---|---|---|
| vault | VAULT_ADDR | Preset by the template |
| vault | VAULT_LOCAL_CONFIG | Preset by the template |
Install Vault on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get vault -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy vault --name my-vault
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Vault.
Docs and upstream
More in Security
- VaultwardenA lightweight, self-hosted password manager server compatible with the Bitwarden clients.
- VoidAuthA 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.
- TinyauthA small login screen and forward-auth server that protects other apps behind your reverse proxy with username and password or OAuth. Runs on SQLite in one container. Users are set with a bcrypt hash in the install form.
- Whoogle SearchA privacy-focused front end for Google search results, with no tracking, ads, or JavaScript required.
- SuperTokensA self-hosted authentication backend with session management, social login, and passwordless, backed by Postgres.
- Step CAA private certificate authority that issues and renews TLS and SSH certificates over ACME or a CLI. Apache-2.0 licensed. The CA password is generated for you and shown in the deployment variables.