Security & Privacy

Bitwarden Self-Hosted Requirements: Full Specs & Hidden Costs

J
James Eriksson
··9 min read
Bitwarden needs 2 GB RAM, 12 GB storage minimum. Vaultwarden uses 1 GB. Compare specs, MSSQL limits, backup needs, and learn when to use managed hosting instead.
TL;DR
  • Bitwarden Standard needs 2 GB RAM minimum and 4 GB recommended; Vaultwarden runs on 1 GB or less
  • The 10 GB MSSQL Express limit is the hidden cost: exceed it and you must upgrade databases or lose features
  • Vaultwarden uses 42-100 MB idle RAM vs Bitwarden's 500-850 MB, saving infrastructure costs
  • HTTPS, SMTP relay, and daily backups are mandatory operational costs you must budget for
  • Managed hosting removes all infrastructure management for $10-15/month

Bitwarden requires 2 GB RAM minimum and 12 GB storage as a baseline for Standard deployment. Vaultwarden, a lightweight fork, runs on 1 GB or less. Both need HTTPS, Docker, and a database. The real bottleneck is not hardware: it's MSSQL complexity, backup discipline, and operational overhead. This guide walks you through what you actually need, what you'll struggle with, and when to stop self-hosting.

What You Actually Need: Official Bitwarden Requirements

Bitwarden publishes two deployment options. Standard is the full-featured version. Lite is a single-container option for smaller deployments. Most admins choose Standard.

Bitwarden Standard minimum specs:

  • CPU: x64 1.4 GHz (1 core minimum, 2+ recommended)
  • RAM: 2 GB minimum, 4 GB recommended
  • Storage: 12 GB minimum, 25 GB recommended
  • Database: MSSQL Express (free tier, 10 GB maximum database size)
  • Docker: Required. Multi-container setup (API, web, identity, SQL Server, nginx)

The 10 GB MSSQL Express limit is the hidden gotcha. Small teams hit it faster than the storage minimum predicts. Every vault attachment, every password update, every organization backup writes to that shared 10 GB pool. Once you breach 10 GB, you cannot add users, passwords, or attachments without upgrading to MSSQL Standard (paid) or switching databases entirely.

Why the gap exists between minimum and recommended: The 2 GB minimum is tight. You run hot. One spike in MSSQL queries, one backup cycle, and your server freezes. The 4 GB recommended assumes modest user load (10-50 people) with daily backups and monitoring. The 25 GB storage accounts for logs, attachments, and growth buffer. Most small teams use 4 GB RAM and 50-100 GB storage on a shared VPS. Bitwarden works. It just does not feel fast.

Vaultwarden: A Lighter Alternative for Self-Hosting

Vaultwarden is a community-maintained Rust reimplementation of Bitwarden's backend. It does 95% of what Bitwarden does and uses a tenth of the resources. The project has 68.9K GitHub stars from teams running it in production.

Vaultwarden community guidance:

  • RAM: 1 GB minimum (no formal spec, but confirmed on single-core VPS by thousands of users)
  • Storage: < 100 MB for the app + attachment storage (variable, your choice)
  • Database: SQLite by default (no separate database needed), or PostgreSQL/MySQL if you prefer
  • Docker: Single container

The real resource comparison: Vaultwarden idle uses 42-100 MB RAM. Bitwarden idle uses 500-850 MB RAM. Under load with 10 users, Vaultwarden hits 150-200 MB; Bitwarden climbs to 800 MB-1.2 GB. Vaultwarden fits in a $2.50/month VPS. Bitwarden needs a $5-10/month instance. That $60-120 annual gap compounds if you value your setup time.

Why Vaultwarden is lightweight: Single Rust process, not multi-container orchestration. SQLite by default means zero database administration. It makes 20% of the network calls Bitwarden makes. No MSSQL licensing. No 10 GB database cap. If you want to deploy it, we have a guide to Docker Compose setup for Vaultwarden that walks through the full installation.

Bitwarden vs Vaultwarden: The Requirement Comparison

AspectBitwarden StandardVaultwarden
CPU1.4 GHz (2+ advised)0.5-1 GHz (any modern CPU)
RAM2 GB min, 4 GB rec.1 GB, often < 512 MB
Storage12-25 GB< 100 MB + attachments
DatabaseMSSQL Express (10 GB max)SQLite (unlimited) or PostgreSQL
Container count5+ (API, web, identity, DB, reverse proxy)1
ComplexityModerate (Docker Compose, MSSQL config)Low (single container, optional volume mount)
UpdatesFrequent, coordinated with MSSQLInfrequent, single container pull
BackupFull database dump + attachmentsSingle volume snapshot
Organization usersFully supportedSupported, same features
2FA/TOTPYesYes
Web autofillYesYes
CLI toolYesYes
Mobile appsOfficial Bitwarden appsWorks with Bitwarden apps

Vaultwarden trades official support and infrequent features (minor) for resource efficiency. Organizations rarely outgrow it on resources; they outgrow it on admin willingness.

What Admins Actually Struggle With

The official specs tell half the story. Here is what kills self-hosted projects:

HTTPS is mandatory, not optional. Bitwarden refuses to run without HTTPS in production. Your router needs port 443 inbound (home lab: port-forward and risk; VPS: easy). Self-signed certificates work only for testing; production needs Let's Encrypt or a paid certificate. Certificate renewal automation (Certbot, acme.sh) is non-negotiable. Expired cert means vault locked out.

SMTP and email delivery are surprisingly hard. Bitwarden sends password reset, 2FA, and organization invite emails. Your home internet likely blocks outbound SMTP (port 25). VPS SMTP is blacklisted by Gmail, Outlook, Yahoo (reputation problem). Solution: relay through Postmark, SendGrid, or your ISP's SMTP if offered. That adds a third dependency and another account to manage.

Backup discipline is the real cost. Official specs assume you backup daily. Most small teams back up weekly or monthly. A corrupted Bitwarden database means you restore from backup or lose all passwords. That is the kind of outage a founder does not come back from. Backup tools (Duplicati, Restic, BorgBackup) add complexity, maintenance, and monitoring overhead that most teams underestimate.

Multi-container orchestration (Bitwarden Standard) creates operational drag. Docker Compose works, but a stray network error, volume permissions issue, or MSSQL lock blocks the whole stack. When Vaultwarden breaks, one container restarts. When Bitwarden breaks, five things need troubleshooting, and the diagnosis takes longer. If you want to understand the specific limitations before committing to self-hosted Bitwarden, see what you should know about self-hosted Bitwarden limitations.

Infrastructure Costs: VPS, NAS, or Home Server?

Small VPS ($5-15/month): Vaultwarden on 1 GB RAM and 20 GB SSD costs $5/month (Vultr, Linode, Hetzner, DigitalOcean). Works flawlessly. Bitwarden Standard needs 2-4 GB RAM and 50 GB SSD for $10-20/month. Tight but viable. Uptime: 99.9% (data center backed). Backup depends on you (incremental snapshots help). Support: none (you own it).

Home NAS or Raspberry Pi: Vaultwarden runs fine on Raspberry Pi 4 (4 GB RAM) or older NAS. Bitwarden is possible but painful (MSSQL sluggish, Docker swaps to disk, performance degrades). Uptime: 95-98% (hardware fails, power cuts, internet drops). Backup: local redundancy (RAID) helps, but you need external backup too. Network: HTTPS requires dynamic DNS or a fixed public IP. Most home ISPs change IPs weekly.

Home server (mini-ITX or old desktop): Electricity costs 30-100W continuous, or $30-100/year. Network has same HTTPS challenges as NAS. Uptime: you restart it, not a data center SLA. Backup requires same discipline as NAS.

The math: Vaultwarden on a $5/month VPS costs $60/year plus 2 hours setup plus 1 hour maintenance per year. Reasonable. Bitwarden on $10/month VPS costs $120/year plus 4 hours setup plus 2-3 hours maintenance per year. Still reasonable for small teams. Bitwarden on home hardware costs $0/year (hardware already purchased) plus 6-8 hours initial setup plus 4-5 hours troubleshooting outages per year plus electricity. Often more expensive than VPS when you value your time.

Why Managed Hosting Removes the Requirement Headache

If you want Bitwarden or Vaultwarden but hate administration, managed hosting handles HTTPS, SMTP, backups, and updates for you. Managed providers provision the container, configure HTTPS automatically, and renew certificates. They handle outbound email via their SMTP relay (Gmail and Outlook trust it). Automated daily backups are stored separately from the live instance. One-click updates happen with no downtime and no multi-container chaos. Monitoring and alerting page on-call if it fails. Your job: log in and use the vault.

Why this matters for team adoption: Teams with 10-50 people lose passwords to self-hosted outages. Managed hosting prevents that. The data centers running managed instances hold ISO 27001 / SOC 2 certifications at the infrastructure level, which matters for regulated industries. One-person teams cannot be on-call for a password manager. Managed hosting removes that burden entirely.

Cost vs DIY: DIY costs $5-20/month plus your troubleshooting time. Managed hosting is typically $10-15/month plus zero admin time. For most small teams, managed hosting pays for itself in avoided outages and your time back. Start with managed hosting on Opsily's Vaultwarden service if operations are not your strength.

Frequently Asked Questions

Can I run Bitwarden on 1 GB of RAM? Technically yes, but poorly. The MSSQL database server alone uses 500-800 MB at idle. A single user login causes memory pressure and disk swapping. You will restart it weekly to clear memory leaks. Vaultwarden on 1 GB is designed and tested; Bitwarden is not.

Does Vaultwarden need HTTPS? Yes. Both Bitwarden and Vaultwarden refuse to serve passwords over unencrypted connections. HTTPS is non-negotiable, whether self-hosted or managed. This is a feature, not a bug.

What happens if I hit the 10 GB MSSQL limit? You cannot add passwords, users, or attachments until you upgrade to MSSQL Standard (paid license, $50-$500+/year depending on scale) or migrate to PostgreSQL/MySQL (complex, downtime required). Plan for growth or switch to Vaultwarden (no limit).

How often do I need to back up? Daily is recommended if you add or edit passwords daily. Weekly is acceptable for stable teams. Monthly is too infrequent. A backup is only useful if you test it quarterly; a one-time backup is a wish, not a recovery plan.

Can I migrate from self-hosted Bitwarden to managed hosting later? Yes. Export your vault, import to managed hosting. Takes 10 minutes. You can also switch from self-hosted Bitwarden to Vaultwarden (same import process) or vice versa.

Is Vaultwarden as secure as Bitwarden? Vaultwarden uses the same encryption as Bitwarden (AES-256-GCM). The difference is not encryption; it is software maintenance. Vaultwarden is maintained by a community contributor, not a company. Bitwarden is audited annually by third parties; Vaultwarden is not. For small teams, Vaultwarden is secure enough. For regulated industries or high-risk data, Bitwarden's audit record matters.

Is Bitwarden free if self-hosted? Yes. The container is free. The infrastructure (VPS or home server) costs money. MSSQL Express is free but capped at 10 GB. Premium features on self-hosted Bitwarden require an organization subscription ($3-5/user/month). Vaultwarden is free and has no licensing upsells.

The Bottom Line

Bitwarden Standard requires 2-4 GB RAM and 12-25 GB storage. Vaultwarden does the same job on 1 GB and 100 MB. The real cost is not hardware; it is HTTPS setup, SMTP relay configuration, backup discipline, and your ongoing troubleshooting. Self-host Vaultwarden on a $5/month VPS if you like infrastructure. Use managed hosting if you want a password manager, not a hobby.

Skip the complexity. Start managed.
Opsily handles HTTPS, backups, SMTP, and updates. You log in and use the vault.
Get Started Free

Ready to self-host your own apps?

One server. Multiple apps. No per-app fees.

Get started →