Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
A secrets manager that stores, generates and controls access to API keys, passwords, certificates and encryption keys behind one API, CLI and web UI. It adds dynamic secrets, leases and revocation, encryption as a service, pluggable auth methods and policies, and a detailed audit log. Vault starts sealed and is unlocked with unseal keys created at initialisation.
Runs on a VPS from $6/mo (Kamatera 2GB, 2 GB RAM) · prices checked Nov 2026
Fits home hardware (23 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 untested), Raspberry Pi 5 (8 GB) (arm64 untested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick Vault when you need the reference implementation of a secrets engine rather than only a place to store key-value pairs: the README describes it as a tool for securely accessing secrets, with a unified interface, tight access control and a detailed audit log, and it can also generate short-lived dynamic credentials, encrypt data as a service and issue certificates. It is Go under the Business Source License 1.1 (not open source in the OSI sense; the Additional Use Grant allows production use unless you offer it to third parties on a hosted or embedded basis in competition with IBM's paid versions). Our snippet is the Docker Hub image's server mode, not dev mode: file storage on a named volume, a listener with TLS disabled and the UI on, read from a config file in `./vault-config` with `disable_mlock = true`, pinned to `2.2.1`, the newest stable patch tag on Docker Hub when we wrote this. The snippet's readiness check uses `/v1/sys/health` with `uninitcode=200&sealedcode=200`, because a fresh Vault is uninitialised and would otherwise answer 501. We did not find an upstream RAM minimum for a single test node, so our 512 MB floor is an estimate. OpenBao in this catalog is the MPL-2.0 community fork with a Vault-compatible API; Infisical and Phase are application-secrets managers with project and environment views rather than a general secrets-engine platform.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# HashiCorp Vault — server mode (not dev), file storage on a named volume, config file — pinned to 2.2.1
mkdir -p vault-config
cat > vault-config/vault.hcl <<'EOF'
ui = true
disable_mlock = true
storage "file" {
path = "/vault/file"
}
listener "tcp" {
address = "0.0.0.0:8200"
tls_disable = true
}
EOF
cat > docker-compose.yml <<'EOF'
services:
vault:
image: hashicorp/vault:2.2.1
restart: unless-stopped
command: server
ports:
- 8200:8200
environment:
VAULT_ADDR: http://127.0.0.1:8200
volumes:
- ./vault-config:/vault/config
- vault_data:/vault/file
volumes:
vault_data:
EOF
docker compose up -d
timeout 120 bash -c 'until curl -fsS "http://localhost:8200/v1/sys/health?uninitcode=200&sealedcode=200" >/dev/null; do sleep 3; done'
# → http://SERVER_IP:8200/ui — Vault starts sealed and uninitialised: run `docker compose exec vault vault operator init`, save the unseal keys and root token offline, then `docker compose exec vault vault operator unseal` three times (once per key)The Docker Hub page and Vault's licence flag these before you put it in front of real secrets:
A developer dashboard on PostgreSQL and Redis with an MIT core, or an API-first, sealed-by-default secrets engine under the Business Source License.
The MPL-2.0 community fork under the Linux Foundation, or HashiCorp's original now under the Business Source License.
HashiCorp Vault used 23 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 512 MB.
The HashiCorp Vault install snippet is marked verified on Ubuntu 26.04 (Nov 2026).