Layer 5 · self-hosting reality check
What it actually takes to self-host Bitwarden
The docs say 2 GB. In practice you want 4 GB for the official self-hosted stack. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from 1Password alternatives, where Bitwarden is one of the picks.
Wondering whether you need to at all? Is 1Password free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 2 GB |
|---|---|
| RAM — what it really needs | 4 GB for the official self-hosted stack |
| CPU | 2 vCPU |
| Disk | 20 GB |
| Monthly cost | $20–35/mo — which is more than the hosted plan costs |
| Setup time | 2 hours |
| How you install it | The official installer script, or Unified Deployment for a lighter single container |
| Ongoing maintenance | Moderate, and non-negotiable. Security updates are not optional here. |
| Where it stops scaling | Organisation-sized deployments. For a household, Vaultwarden is the right shape. |
The thing that catches people out
The official self-hosted server runs a stack of containers — SQL Server, Identity, API, admin — and wants around 4 GB, which is why most people who set out to self-host Bitwarden end up running Vaultwarden instead. Vaultwarden is a compatible reimplementation in Rust that fits in 256 MB. Choose the official server only if you need the enterprise features it carries.
When not to self-host Bitwarden
You will not commit to patching it promptly. A password manager you host badly is worse than one somebody else hosts well.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does Bitwarden actually need?
- 4 GB for the official self-hosted stack in practice. The documented minimum is 2 GB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU alongside it.
- What does self-hosting Bitwarden cost per month?
- $20–35/mo — which is more than the hosted plan costs This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for moderate, and non-negotiable. Security updates are not optional here.
- How long does it take to set up Bitwarden?
- 2 hours, via The official installer script, or Unified Deployment for a lighter single container.
- When should I NOT self-host Bitwarden?
- You will not commit to patching it promptly. A password manager you host badly is worse than one somebody else hosts well.
- What is the most common mistake when self-hosting Bitwarden?
- The official self-hosted server runs a stack of containers — SQL Server, Identity, API, admin — and wants around 4 GB, which is why most people who set out to self-host Bitwarden end up running Vaultwarden instead. Vaultwarden is a compatible reimplementation in Rust that fits in 256 MB. Choose the official server only if you need the enterprise features it carries.