PUBLISHED ARTIFACT // vaultwarden
A lightweight, self-hosted Bitwarden-compatible password manager server written in Rust.
services:
vaultwarden:
image: vaultwarden/server:latest
container_name: vaultwarden
restart: unless-stopped
environment:
DOMAIN: "https://vaultwarden.example.com"
volumes:
- ./vw-data:/data
ports:
- "127.0.0.1:8000:80"Lightweight single-container service; storage grows with attachments and Sends. No fixed minimum is published, so size for users, attachments, and the selected database backend.
Requires a supported container runtime and HTTPS reverse proxy or other TLS termination. The default mounted /data volume uses SQLite; MySQL/MariaDB and PostgreSQL are optional.
Bitwarden-compatible accounts with TOTP, email, FIDO2/WebAuthn, YubiKey, Duo, emergency access, and optional OpenID Connect SSO. The web vault requires HTTPS and a secure context.
Back up /data regularly. With SQLite, use the built-in /vaultwarden backup command or SQLite online backup, and separately retain attachments, optional Send files, config.json, and rsa_key* files. External MySQL/PostgreSQL databases require their own dumps. Test restores with Vaultwarden stopped.
Vaultwarden is an independent, unofficial Bitwarden-compatible server. Client releases can outpace API compatibility; report issues to Vaultwarden rather than Bitwarden support.
It is substantially lighter than the official Bitwarden self-hosted stack and works with official clients, but compatibility is independently maintained and operators own TLS, upgrades, backups, and hardening.