Self-Host Vaultwarden: Bitwarden Password Manager 2026

TL;DR

Vaultwarden (AGPL 3.0, ~40K GitHub stars, Rust) is an unofficial Bitwarden-compatible server — the most popular self-hosted password manager setup. Bitwarden charges $10/year for premium features. Vaultwarden gives you all premium features free: TOTP, file attachments, emergency access, organization sharing, and Bitwarden Send — on your own hardware. The official Bitwarden browser extensions, mobile apps, and desktop clients all connect to your Vaultwarden server seamlessly.

Key Takeaways

• Vaultwarden: AGPL 3.0, ~40K stars, Rust — Bitwarden-compatible, all premium features free
• Bitwarden clients: Official iOS, Android, browser extensions, desktop apps — all work with Vaultwarden
• Zero-knowledge: Passwords are E2E encrypted; your server never sees plaintext
• Organizations: Share passwords with family or team via collections
• TOTP: Store TOTP secrets and auto-fill 2FA codes (Bitwarden Authenticator)
• Admin panel: Manage users, organizations, and settings via /admin

---

Vaultwarden vs Bitwarden Cloud vs 1Password

Feature	Vaultwarden	Bitwarden Cloud	1Password
License	AGPL 3.0	Bitwarden Open Source	Proprietary
Cost	Free (self-host)	Free / $10/yr premium	$2.99/mo
TOTP/2FA storage	Free	$10/yr premium	Yes
File attachments	Free	$10/yr premium	Yes
Organizations	Free	$40/yr	$4.99/mo/family
Emergency access	Free	$10/yr	Limited
Bitwarden Send	Free	Free	No
Passkey support	Yes	Yes	Yes
E2E encryption	Yes	Yes	Yes

---

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: "https://vault.yourdomain.com"
      # Disable signups after you've created your account:
      SIGNUPS_ALLOWED: "true"
      # Admin token (for /admin panel) - generate with: openssl rand -base64 48
      ADMIN_TOKEN: "${ADMIN_TOKEN}"
      # Rate limiting:
      LOGIN_RATELIMIT_MAX_BURST: 10
      LOGIN_RATELIMIT_SECONDS: 60
      ADMIN_RATELIMIT_MAX_BURST: 5
      ADMIN_RATELIMIT_SECONDS: 300
      # Push notifications (optional, for mobile sync):
      PUSH_ENABLED: "false"
      # Require email verification:
      SIGNUPS_VERIFY: "true"
      # Email settings:
      SMTP_HOST: "smtp.yourdomain.com"
      SMTP_PORT: 587
      SMTP_SECURITY: "starttls"
      SMTP_FROM: "vault@yourdomain.com"
      SMTP_USERNAME: "${SMTP_USER}"
      SMTP_PASSWORD: "${SMTP_PASS}"

volumes:
  vaultwarden_data:

# .env
ADMIN_TOKEN=$(openssl rand -base64 48)

docker compose up -d

Visit http://your-server:8080 → Create Account → register your first user.

---

Part 2: HTTPS with Caddy

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

vault.yourdomain.com {
    reverse_proxy localhost:8080
}

Now visit https://vault.yourdomain.com to access your vault.

---

Part 3: Disable Open Registration

After creating your account (and any family/team accounts), disable signups:

environment:
  SIGNUPS_ALLOWED: "false"

docker compose up -d

To invite specific users later, use the admin panel at https://vault.yourdomain.com/admin.

---

Part 4: Browser Extensions

Connect official Bitwarden extensions to your self-hosted server:

Chrome / Firefox / Edge

1. Install Bitwarden browser extension
2. Click the extension → Log in → click Self-hosted
3. Server URL: https://vault.yourdomain.com
4. Log in with your email and master password
5. Extension auto-fills passwords and generates new ones

---

Part 5: Mobile Apps

iOS

1. Install Bitwarden from App Store
2. Tap Self-hosted environment
3. Server URL: https://vault.yourdomain.com
4. Log in → enable Autofill in iOS Settings → Passwords → AutoFill Passwords → Bitwarden

Android

1. Install from Google Play or F-Droid
2. Same server setup process
3. Enable Autofill: Accessibility Settings → Bitwarden

---

Part 6: Organizations (Family/Team Sharing)

Share passwords with family members or a team:

Create an organization

1. Web vault → Organizations → New Organization
2. Name: Family or Company
3. Billing email: your email (free on Vaultwarden)

Create collections

Organization: "Family"
├── Collection: "Shared Accounts" (all members can view)
│   ├── Netflix login
│   ├── Spotify family
│   └── Home WiFi
├── Collection: "Financial" (adults only)
│   ├── Bank accounts
│   └── Investment accounts
└── Collection: "Kids" (children can access)
    ├── School accounts
    └── Gaming accounts

Invite members

1. Organization → Members → Invite Member
2. Enter email → select role (Owner/Admin/Manager/Member/Custom)
3. Assign collections

---

Part 7: TOTP (2FA Authenticator)

Store TOTP seeds alongside passwords:

1. When adding/editing a password entry, scroll to Authenticator Key (TOTP)
2. Scan the QR code or paste the secret key
3. Bitwarden shows the live TOTP code when viewing the entry
4. Browser extension auto-fills TOTP codes on 2FA prompts

---

Part 8: Admin Panel

Access https://vault.yourdomain.com/admin with your ADMIN_TOKEN:

Key settings:

• Users → list users, invite new ones, force 2FA enrollment
• Organizations → view all orgs and members
• Diagnostics → check config and connectivity
• Settings → enable/disable features, set limits

# Common admin tasks via env vars:
# Invite-only mode:
SIGNUPS_ALLOWED: "false"
INVITATIONS_ALLOWED: "true"

# Require TOTP/2FA for all users:
REQUIRE_DEVICE_EMAIL: "true"

# Limit attachment size:
ROCKET_LIMITS: "{ json = 10485760 }"

# Org limit:
ORG_CREATION_USERS: "alice@example.com"    # Only Alice can create orgs

---

Part 9: Push Notifications (Mobile Sync)

For real-time vault sync on mobile (optional):

1. Register at bitwarden.com/host — free, get installation ID + key
2. Update docker-compose.yml:

environment:
  PUSH_ENABLED: "true"
  PUSH_INSTALLATION_ID: "${PUSH_INSTALLATION_ID}"
  PUSH_INSTALLATION_KEY: "${PUSH_INSTALLATION_KEY}"

Without push: vault syncs when you open the app. With push: syncs immediately when you save a new password.

---

Maintenance

# Update Vaultwarden:
docker compose pull
docker compose up -d

# Backup (critical!):
tar -czf vaultwarden-backup-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect vaultwarden_vaultwarden_data --format '{{.Mountpoint}}')

# Restore from backup:
tar -xzf vaultwarden-backup-20260101.tar.gz -C /
docker compose restart vaultwarden

# Logs:
docker compose logs -f vaultwarden

# Check admin panel health:
curl -s https://vault.yourdomain.com/api/config | jq

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:

1. Confirm the container is running: docker compose ps
2. Test locally on the server: curl -I http://localhost:PORT
3. If local access works but external doesn't, check your firewall: ufw status
4. 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 our advanced Vaultwarden hardening guide for PostgreSQL backend, fail2ban, 2FA enforcement, and production security.

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

See open source alternatives to Vaultwarden on OSSAlt.