How to Self-Host Vaultwarden 2026

TL;DR

Vaultwarden (GPL 3.0, ~38K GitHub stars, Rust) is an unofficial Bitwarden-compatible server written in Rust. It works with all official Bitwarden clients (browser extensions, desktop apps, mobile apps, CLI) but runs in ~10MB RAM vs Bitwarden's ~500MB. LastPass charges $3/month; 1Password charges $2.99/month. Vaultwarden gives you the same security model — zero-knowledge, end-to-end encrypted — on your own server, free.

Key Takeaways

Vaultwarden: GPL 3.0, ~38K stars, Rust — Bitwarden-compatible server using official clients
10MB RAM: Runs on any hardware — Raspberry Pi, VPS, NAS
All Bitwarden features: Organizations, collections, sends, emergency access, TOTP generator
Admin panel: Built-in admin UI for user and organization management
Zero-knowledge: Vault data encrypted client-side — server never sees plaintext passwords
Official clients: Use the official Bitwarden browser extension, desktop app, and mobile app

Part 1: Docker Setup

# docker-compose.yml
services:
  vaultwarden:
    image: vaultwarden/server:latest
    container_name: vaultwarden
    restart: unless-stopped
    ports:
      - "8080:80"
    volumes:
      - vaultwarden_data:/data
    environment:
      # Domain (required for WebAuthn):
      DOMAIN: "https://vault.yourdomain.com"

      # Admin token (for /admin panel):
      ADMIN_TOKEN: "${ADMIN_TOKEN}"   # openssl rand -base64 48

      # Disable public registration after you create your account:
      SIGNUPS_ALLOWED: "false"

      # Invite-only registration:
      INVITATIONS_ALLOWED: "true"

      # Email (for 2FA codes, invitations, emergency access):
      SMTP_HOST: mail.yourdomain.com
      SMTP_PORT: 587
      SMTP_SECURITY: starttls
      SMTP_FROM: vault@yourdomain.com
      SMTP_USERNAME: vault@yourdomain.com
      SMTP_PASSWORD: "${MAIL_PASSWORD}"

      # Enable WebAuthn (hardware keys):
      # Already enabled by default

      # Show password hints (disable for security):
      SHOW_PASSWORD_HINT: "false"

      # Enable organizations:
      ORG_CREATION_USERS: "all"   # or specific email

      # Sends (file sharing):
      SENDS_ALLOWED: "true"

volumes:
  vaultwarden_data:

# Generate admin token:
echo "ADMIN_TOKEN=$(openssl rand -base64 48)" >> .env

docker compose up -d

Part 2: HTTPS with Caddy

HTTPS is required — Bitwarden clients refuse to connect over HTTP:

vault.yourdomain.com {
    reverse_proxy localhost:8080
}

Part 3: Create Your Account

Visit https://vault.yourdomain.com
Create Account:
- Email: your email
- Name: your name
- Master Password: strong, memorable passphrase (NEVER forget this)
- Hint: optional — keep vague
Verify email
Disable signups: set SIGNUPS_ALLOWED: "false" and restart

Part 4: Admin Panel

Access the admin panel at https://vault.yourdomain.com/admin using your ADMIN_TOKEN.

Admin panel capabilities

View all users and organizations
Delete users or deactivate accounts
Resend email invitations
Send test emails
View event logs
Force 2FA for all users
Set org storage limits

Invite additional users

Admin Panel → Users → Invite User → email@example.com

The user receives an invitation email and can create their account.

Part 5: Browser Extension Setup

Chrome / Chromium / Edge / Firefox / Safari

Install Bitwarden Browser Extension
Click the extension icon → Log In
Server URL → Enter: https://vault.yourdomain.com
Log in with your email and master password
All your vault items sync immediately

The extension auto-fills logins, generates passwords, and shows TOTP codes.

Configuration tips

Settings → Security:
  - Vault timeout: 15 minutes (or On Browser Restart)
  - Vault timeout action: Lock (not Log Out)
  - Unlock with biometrics: Yes (if supported)
  - Two-step login: Enable TOTP or WebAuthn

Part 6: Mobile Apps

iOS and Android

Install official Bitwarden app
Log In → tap gear icon → Self-hosted
Server URL: https://vault.yourdomain.com
Log in with credentials
Enable biometric unlock in settings

iOS AutoFill

iPhone Settings → Passwords → AutoFill Passwords
Enable Bitwarden
Bitwarden now fills passwords system-wide in all apps

Organizations allow sharing vault items with family or team:

Create an organization

New Organization in the Bitwarden web vault
Name: Family, Work
Plan: Free (up to 2 users) or Families equivalent

Note: Vaultwarden allows unlimited org members regardless of Bitwarden plan tier.

Edit item → Move to Organization
Select the organization
Choose collection: Shared, Work Tools, etc.
Permission: Can View or Can Edit

Invite family members

Organization Settings → People → Invite
Enter email → Confirm role (Member or Manager)
User accepts invite and accesses shared collection

Part 8: Advanced Features

Emergency Access

Allow a trusted person to access your vault if you're incapacitated:

Settings → Emergency Access → Add
Enter trusted contact's email (must be a Vaultwarden user)
Access type: View or Takeover
Wait time: 1 day, 2 days, 7 days (they can request access, you have time to deny)

Share text or files securely — recipient gets a temporary link:

# Via Bitwarden CLI:
bw send -n "Secret note" -d 7 --text "The server password is..."
# Returns: https://vault.yourdomain.com/#/send/...

# File send:
bw send -n "Document" -d 1 -f /path/to/document.pdf

Bitwarden CLI

# Install:
npm install -g @bitwarden/cli
# or brew install bitwarden-cli

# Configure server:
bw config server https://vault.yourdomain.com

# Login:
bw login

# Get a password:
bw get password "GitHub"

# List items:
bw list items | jq '.[].name'

# Generate a password:
bw generate --length 20 --uppercase --lowercase --number --special

# Sync vault:
bw sync

# Export vault:
bw export --format encrypted_json --output vault-backup.json

Backup Strategy

# Backup the SQLite database (the entire vault):
docker compose stop vaultwarden

docker cp vaultwarden:/data/db.sqlite3 \
  vault-backup-$(date +%Y%m%d).db

docker compose start vaultwarden

# Full data backup (includes attachments):
tar -czf vaultwarden-full-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect vaultwarden_vaultwarden_data --format '{{.Mountpoint}}')

# Automated nightly backup script:
#!/bin/bash
BACKUP_DIR=/home/user/backups/vaultwarden
mkdir -p "$BACKUP_DIR"

# Export via Bitwarden CLI (encrypted):
bw export --format encrypted_json \
  --output "$BACKUP_DIR/vault-$(date +%Y%m%d).json"

# Keep last 30 days:
find "$BACKUP_DIR" -name "*.json" -mtime +30 -delete
find "$BACKUP_DIR" -name "*.db" -mtime +30 -delete

Update and Maintenance

# Update (check release notes first — breaking changes possible):
docker compose pull
docker compose up -d

# View active sessions:
# Admin Panel → Users → [user] → View Sessions

# Force logout all sessions (if compromised):
# Admin Panel → Users → [user] → Deactivate

# Logs:
docker compose logs -f vaultwarden

Why Self-Host Vaultwarden?

The case for self-hosting Vaultwarden comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Vaultwarden means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Vaultwarden, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Vaultwarden headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Vaultwarden data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Vaultwarden without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Vaultwarden's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Vaultwarden backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Vaultwarden's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Vaultwarden's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Vaultwarden's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Vaultwarden's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f vaultwarden

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Vaultwarden's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

Confirm the container is running: docker compose ps
Test locally on the server: curl -I http://localhost:PORT
If local access works but external doesn't, check your firewall: ufw status
If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats vaultwarden. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Vaultwarden Updated

Vaultwarden follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Vaultwarden is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See all open source security tools at OSSAlt.com/categories/security.

See open source alternatives to Vaultwarden on OSSAlt.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)