Guides / Vaultwarden
Self-host Vaultwarden without Docker
Last updated 17 November 2026 · By Mohammad AlSaraf
Vaultwarden is a small, open-source server for the Bitwarden password manager apps and browser extensions. Your vault is encrypted with your master password before it leaves your device, so the server never sees your passwords in the clear. We tested these steps on a fresh natbox server on 17 November 2026 with Vaultwarden 1.37.5: install, service and Caddy forwarding. The certificate step needs your own domain and follows Caddy's standard setup.
1. Get Vaultwarden
Vaultwarden is published as a Docker image, and natbox servers don't run Docker. Its documentation points to a small script that unpacks a program from an image without Docker. The Alpine image contains a single static program that runs on any Linux:
apt update
apt install -y curl ca-certificates jq
mkdir -p /opt/vaultwarden && cd /opt/vaultwarden
curl -fsSL -o docker-image-extract https://raw.githubusercontent.com/jjlin/docker-image-extract/main/docker-image-extract
chmod +x docker-image-extract
./docker-image-extract vaultwarden/server:latest-alpine
mv output/vaultwarden output/web-vault .
rm -rf output docker-image-extract
./vaultwarden --version
Use the latest-alpine image: the plain latest image needs newer system libraries than Debian 12 has.
2. A user and a settings file
useradd -r -d /opt/vaultwarden -s /usr/sbin/nologin vaultwarden
mkdir -p /opt/vaultwarden/data
cat > /opt/vaultwarden/.env <<'EOF'
DOMAIN=https://vault.example.com
ROCKET_ADDRESS=127.0.0.1
ROCKET_PORT=8000
DATA_FOLDER=/opt/vaultwarden/data
WEB_VAULT_FOLDER=/opt/vaultwarden/web-vault
SIGNUPS_ALLOWED=true
EOF
chmod 600 /opt/vaultwarden/.env
chown -R vaultwarden:vaultwarden /opt/vaultwarden
Replace vault.example.com with your own domain. Vaultwarden only listens on 127.0.0.1; Caddy will face the internet.
3. Keep it running with systemd
cat > /etc/systemd/system/vaultwarden.service <<'EOF'
[Unit]
Description=Vaultwarden
After=network-online.target
Wants=network-online.target
[Service]
User=vaultwarden
WorkingDirectory=/opt/vaultwarden
EnvironmentFile=/opt/vaultwarden/.env
ExecStart=/opt/vaultwarden/vaultwarden
Restart=always
RestartSec=5
[Install]
WantedBy=multi-user.target
EOF
systemctl daemon-reload
systemctl enable --now vaultwarden
curl -s http://127.0.0.1:8000/alive
The last command prints a date and time when it is running.
4. HTTPS with Caddy
Link your domain in the client area's Domains tab first (A record to our address, plus the TXT record shown). Then:
apt install -y caddy
cat > /etc/caddy/Caddyfile <<'EOF'
vault.example.com {
reverse_proxy 127.0.0.1:8000
}
EOF
systemctl restart caddy
Caddy gets a certificate on its own. Open https://vault.example.com and create your account. If you use the Caddy one-click app, add the same reverse_proxy block as a file in /etc/caddy/sites instead.
5. Close sign-ups
Once you and your family have accounts, stop strangers from creating one:
sed -i 's/^SIGNUPS_ALLOWED=true/SIGNUPS_ALLOWED=false/' /opt/vaultwarden/.env
systemctl restart vaultwarden
6. Back it up
Everything lives in /opt/vaultwarden/data. Copy it somewhere else regularly (backups guide), or add Off-site backups to your plan. Keep an exported copy of your vault too: if you lose the server and the master password, nobody can recover it.
Updating
Repeat step 1 in a temporary folder, stop the service, replace vaultwarden and web-vault, fix the owner with chown -R vaultwarden: /opt/vaultwarden, and start it again. Take a snapshot first.
Related: self-hosting on a small VPS, automatic HTTPS with Caddy, secure your server.
More guides: Run a WireGuard VPN, Back up your server with restic, Automatic HTTPS with Caddy.