Who this is for
You are set on self-hosting your passwords to keep your data off public cloud servers, but you are staring down two very different paths. One is the official, enterprise-grade Docker stack supported by Bitwarden. The other is Vaultwarden, a lightweight, unofficial rewrite that does the same job on a fraction of the hardware.
If you are still weighing whether to self-host at all, check out our Vaultwarden vs Bitwarden cloud breakdown first. If you are ready to boot up a server, this comparison will save you from making a bad hardware choice.
At a glance
| Bitwarden Server (Official) | Vaultwarden (Unofficial) | |
|---|---|---|
| Best for | Enterprise teams, compliance audits | Homelabs, families, low-spec servers |
| RAM Footprint | 2 GB to 4 GB minimum (10+ Docker containers) | 15 MB to 50 MB (single container) |
| Premium Features | Requires paid license from Bitwarden | Unlocked by default (free) |
| Database | MSSQL, PostgreSQL, MySQL/MariaDB | SQLite, PostgreSQL, MySQL |
| API Sync Lag | None (official upstream) | Days or weeks for new client features |
| Dealbreaker | High resource cost; painful to update | Unofficial; no enterprise support |
Option A: Bitwarden Server
This is the real deal: the exact same .NET-based backend that runs Bitwarden’s official cloud service. When you self-host the official server, you are pulling down their public Docker repositories and running the full corporate suite in your own environment.
The immediate reality check is its size. The official stack is a microservices engine running up to a dozen different Docker containers: including APIs, identity managers, billing services, and admin portals. Running this stack comfortably requires a minimum of 2 GB of RAM, though 3 GB to 4 GB is closer to the true baseline once your vault grows. If you run MS SQL Server as your database, that database engine alone will eat 1.5 GB of memory just standing still.
Even if you self-host, you do not bypass the cash register. The server is open-core, which means enterprise features: like SSO integration, directory sync, and collections for large teams: still require you to upload a valid license file purchased from Bitwarden.
Wins on:
- Perfect client compatibility. Because you are running official code, new features like passkeys, passwordless login, and secure exports work instantly. There is no waiting for community reverse-engineering.
- SSO and Enterprise sync. If you need to bind your vault to Active Directory, Azure AD, or Okta, this is your only viable path.
- Audit compliance. For corporate IT departments that require official vendor support and security certificates, running the official stack is non-negotiable.
Loses on:
- Heavy resource costs. Running this on a $5 virtual private server is out of the question. You will pay more in monthly cloud hosting bills just to keep the Docker engine happy.
- Complicated maintenance. Upgrades involve pulling down dozens of images and managing a sprawling docker-compose file. When a container fails, troubleshooting is a multi-container puzzle.
Option B: Vaultwarden
Vaultwarden (formerly known as bitwarden_rs) is a clean-room implementation of the Bitwarden API written in Rust. It is not official code. Instead, the community reverse-engineered the API so that the official Bitwarden apps, browser extensions, and CLIs can talk to it directly.
Because it is written in Rust, Vaultwarden is shockingly efficient. Instead of running a dozen containers, Vaultwarden runs inside a single Docker container. Its baseline memory consumption is around 15 MB to 30 MB of RAM. It is so lightweight that you can easily run it on a $5 virtual private server alongside your other self-hosted services, or even on a spare Raspberry Pi in your closet.
The biggest draw for home users is feature enablement. Because Vaultwarden is a custom API server, it does not check licenses against Bitwarden’s billing gateways. It simply tells the official clients that your account has Premium status. This enables file attachments, TOTP generation, security reports, and small-group organization collections for free. For a step-by-step setup guide, see how to run Vaultwarden on a VPS.
However, “compatible” does not mean “identical.” This is a community-run project. If Bitwarden updates its mobile app with a new login flow or encryption scheme, Vaultwarden has to catch up.
Wins on:
- Tiny hardware footprint. It runs anywhere, uses almost zero idle CPU, and fits onto cheap VPS tiers without breaking a sweat.
- Features enabled by default. Personal premium tools and multi-user collections are active out of the box without buying license files.
- Simple backups. If you use the default SQLite backend, backing up your entire database is as simple as copying a single
.dbfile or using a standard backup script.
Loses on:
- API sync lag. When Bitwarden introduces major client features, you must wait for the Vaultwarden maintainers to patch the Rust API. This can take days or weeks, occasionally causing client sync issues in the interim.
- No official support. If your database gets corrupted or an update goes sideways, you cannot open a corporate support ticket. You are reliant on GitHub discussions and your own backups.
Verdict by scenario
- Choose Vaultwarden if you are running a personal homelab, a family setup, or a small office vault: and you want premium features like TOTP and file attachments without paying license fees or upgrading to a massive VPS.
- Choose Bitwarden Server if you are running an enterprise, need deep Active Directory or SSO integrations: and have the dedicated IT team and hardware resources to keep a heavy multi-container stack updated.
- Choose Bitwarden Cloud if the thought of managing your own database backups, patching docker-compose files, and handling server downtime makes you sweat: offload the maintenance and let them host it.
Bottom line
Vaultwarden is the homelab champion. It gives you the full premium Bitwarden feature set on hardware that costs less than a cup of coffee. The official Bitwarden self-hosted stack is for businesses that need to check corporate audit boxes, sync directory access, and hold vendor support contracts.
For the solo developer or family admin, running the official stack is like buying a semi-truck to bring home groceries: it is expensive, hard to park, and completely unnecessary. Stick to the Rust container and keep your VPS bills light.
