Last verified:
Everyone in the Bitwarden ecosystem eventually asks the same question: run the official self-hosted server, or the unofficial Rust reimplementation everyone on r/selfhosted actually uses? Vaultwarden speaks the same API as Bitwarden, works with the official apps, and needs roughly one-thirtieth of the resources.
The answer is less obvious than the meme suggests, because the two projects serve different risk profiles. Here is the honest breakdown.
TL;DR: Which One Should You Pick?
Pick Vaultwarden if this is for you, your family, or a small team, and you want premium features like TOTP and organizations without a license, on a VPS that costs 5 EUR per month.
Pick official Bitwarden if you are deploying for a company that needs vendor support, compliance paperwork, SSO integrations, and the guarantee that the server is maintained by the same organization that builds the clients.
Vaultwarden vs Bitwarden at a Glance
| Vaultwarden | Bitwarden (self-hosted) | |
|---|---|---|
| What it is | Unofficial Rust rewrite of the server | Official server stack |
| RAM footprint | 50-100 MB idle | 4 GB+ realistic minimum |
| Database | SQLite (Postgres/MySQL optional) | MSSQL (unified beta: others) |
| Containers | 1 | ~12 (3+ for unified) |
| Premium features | Included free | Require paid license |
| Vendor support | Community | Commercial, SLAs available |
| Compliance story | None official | SOC 2, enterprise docs |
| Client apps | Official Bitwarden apps | Official Bitwarden apps |
Where Vaultwarden Wins
Efficiency and features-per-euro. A single container with SQLite gives you the full premium feature set: TOTP authenticator storage, emergency access, organizations, attachments, Send. It idles at double-digit megabytes, which means the cheapest VPS tier of any provider runs it with room for a reverse proxy and a backup agent beside it.
Operationally it is also simpler: one container to update, one data folder to back up. The project has been stable for years and tracks upstream API changes quickly.
Where Bitwarden Wins
Accountability. The official stack is built, tested, and supported by the company that ships the clients, so an API change can never brick your server. For a business, that plus SOC 2 reports, SSO via SAML/OIDC, directory sync, and a support contract is the entire decision. Nobody gets fired for choosing the vendorโs own server.
The cost is infrastructure: a dozen containers, MSSQL, and a 4 GB+ server for something a homelabber does with 100 MB.
VPS Requirements Compared
| Spec | Vaultwarden | Bitwarden official |
|---|---|---|
| Minimum RAM | 128 MB | 4 GB |
| Recommended RAM | 512 MB | 8 GB |
| Storage | 5-10 GB | 30 GB+ |
| CPU | Any single vCPU | 2+ vCPU |
| Key requirement | Uptime + backups | Same, plus MSSQL resources |
For Vaultwarden, the decision is not specs, it is reliability: this server holds your passwords. Hetzner from 5.49 EUR per month is our default pick for its uptime record and snapshot support; Contabo from 5.99 EUR gives you spare headroom to co-host other services on the same box. For an official Bitwarden deployment, start at a 4 vCPU / 8 GB plan - DigitalOcean from 6 USD scales cleanly and its snapshots make the MSSQL stack easy to roll back. Full details in the best VPS for Vaultwarden and best VPS for Bitwarden guides, or see the complete VPS comparison.
Verdict
For personal use and homelabs, Vaultwarden is the rational default, and the r/selfhosted consensus reflects that: same clients, premium features free, and hosting costs that round to a coffee. The official server earns its footprint only where the support contract and compliance letters have monetary value - which is to say, at work.
Whichever you run: put it behind HTTPS, turn on 2FA, and automate an off-site backup of the data directory before you migrate a single password. A password server without tested backups is a time bomb, not a service.
Frequently asked questions
Do the official Bitwarden apps work with a Vaultwarden server?
Yes. Vaultwarden reimplements the Bitwarden server API, so the official browser extensions, mobile apps, and desktop clients connect to it by simply pointing the self-hosted URL at your Vaultwarden instance. Sync, autofill, TOTP, and organizations all work. The clients neither know nor care that the backend is not the official server.
Is Vaultwarden safe enough to store all my passwords?
Vaultwarden has a strong security track record, an active maintainer, and regular audits of its dependency chain by the community. Encryption happens client-side in the official Bitwarden apps, so the server only ever stores encrypted blobs. The bigger risk in practice is your own setup: keep the instance behind HTTPS, restrict the admin panel, enable 2FA, and back up the data folder off-site.
How much VPS do I need for Vaultwarden compared to Bitwarden?
Vaultwarden idles around 50 to 100 MB RAM with SQLite, so the smallest tier of any provider works - even a 5 EUR plan is generous headroom. The official Bitwarden self-host stack pulls a dozen containers with MSSQL and realistically wants 4 GB RAM minimum. That difference alone is why most homelabbers run Vaultwarden.