
Vaultwarden — Lightweight self-hosted server compatible with Bitwarden clients, in Rust
What it is
Vaultwarden implements the Bitwarden server API in a single small binary that runs happily on a Raspberry Pi, supporting official Bitwarden apps, org sharing and 2FA. Self-hosters use it to own their password data. It is a community project without official support, and org features trail the paid Bitwarden tiers.
Editor's review
Long-form introduction by the BetterPicker editors · checked against the official site · Oct 19, 2026
Vaultwarden answers a narrow question very well: how do you run a Bitwarden-compatible password server without dedicating real hardware to it? It is a community rewrite of the Bitwarden server API in Rust, small enough to run comfortably on a Raspberry Pi, and it speaks the protocol well enough that the official Bitwarden apps for desktop and mobile connect without modification. Setup is a Docker pull away, a SQLite database works out of the box, and environment variables cover the decisions that matter - whether signups are open, where the admin panel token lives, what the public URL is. Everything is free and open source under GPL, with no subscription and no account anywhere but your own server. The trade is responsibility. Backups are yours to schedule, and the sensible pattern is real database dumps rather than copying folders out of a running container, because a corrupt copy defeats the purpose. Updates, TLS termination and exposure control are yours too. And because the project is unofficial, it follows Bitwarden's protocol rather than leading it, so a client change can occasionally outrun the server fix until the community catches up. The project began life as bitwarden_rs and took the Vaultwarden name to make its unofficial status unmistakable - a useful signal when you are deciding what to trust with a password vault. An admin panel behind a token lets you inspect accounts and diagnose sync issues without touching the database.
What it does well
Genuinely lightweight: the Rust implementation idles at trivial memory and CPU levels, which is why Raspberry Pi and small VPS deployments are the standard pattern rather than the exception, and why it shares a box with several other services without complaint.
Full client compatibility: official Bitwarden apps for Windows, macOS, Linux, iOS and Android treat it as the real server, including TOTP codes, attachments, folders and organization sharing.
Sensible configuration surface: a documented .env template exposes the settings that matter - signup controls, admin token, domain, SMTP - so a careful half hour gets you a locked-down instance.
Who it's for
Self-hosters who want password ownership without Bitwarden's heavier official server; homelab users already running Docker who can add one more container; and small families or teams who want shared vaults on hardware they control.
Where it falls short
You are the operations team: backups, restores, certificate renewal and upgrade discipline all land on you, and a forgotten backup schedule is the classic failure mode.
Unofficial by design: it tracks the Bitwarden protocol rather than shipping it, so occasional client updates need a server-side catch-up before everything works again.
Exposure is a real risk: a password vault on the public internet needs TLS, strict signup controls and timely patching, or the convenience becomes an attack surface.
Specs at a glance
Facts from the official site · not editorial opinion
| What it is | Unofficial, open-source (GPL-3.0) Bitwarden-compatible server written in Rust for self-hosting |
|---|---|
| Deployment | Single Docker container (vaultwarden/server); light enough for Raspberry Pi and small VPS hardware |
| Database | SQLite by default; optional MySQL or PostgreSQL backends for larger deployments |
| Compatibility | Official Bitwarden apps on desktop and mobile, incl. TOTP, attachments and organization sharing |
| Configuration | Documented environment variables: signup control, admin token, domain, SMTP and more |
| Price | Free to self-host; no subscriptions or accounts beyond your own server |
| Operations | Backups, TLS and updates are operator responsibilities; database dumps are the recommended backup form |
Frequently asked questions
▸Is Vaultwarden the same as Bitwarden?
No. Vaultwarden is a community-written, Bitwarden-compatible server. It speaks the same protocol so official Bitwarden apps connect to it, but it is an independent open-source project, not a Bitwarden product.
▸What hardware does it need?
Very little. A Raspberry Pi or the smallest VPS tier is enough for personal or family use, since the Rust implementation is designed for low resource use.
▸How should I back it up?
Schedule real database dumps (SQLite file copies while stopped, or dump files for MySQL and PostgreSQL) rather than copying folders out of a running container, and test restores periodically.
▸Does it cost anything?
The server is free and open source. You pay only for the hardware or VPS you run it on. Bitwarden's own paid features are not involved.
Video reviews
5 review videos aggregated · praise and criticism included alike · click through to the original video
Channels that covered it
Channels are aggregated as sources only — we don’t rate creators
Related tools
Where to go next
External links open in a new tab; external content is independent of this site.
Link down? Every object page is re-checked monthly.





