Vaultwarden
Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs.
Vaultwarden is an unofficial, open-source implementation of the Bitwarden server API written in Rust. It is fully compatible with all official Bitwarden clients — browser extensions, mobile apps, and the desktop app — so you get the same user experience while keeping your vault entirely on your own infrastructure.
Compared to the official Bitwarden server, Vaultwarden is significantly lighter. It runs comfortably on a Raspberry Pi or a small VPS with less than 100MB of RAM, making it practical to add alongside other self-hosted services without needing dedicated hardware.
Vaultwarden supports the full Bitwarden feature set: organisations, collections, two-factor authentication, emergency access, the Send feature, and the web vault UI. It is a drop-in replacement for the Bitwarden cloud for individuals and small teams who want full control over their password data.
Categories:
Tags:
Build with:
Frequently Asked Questions
What is Vaultwarden?
Vaultwarden (formerly bitwarden_rs) is an alternative implementation of the Bitwarden server, written in Rust and compatible with the official Bitwarden clients (browser extensions, desktop, mobile, and CLI). It is designed for lightweight self-hosted deployments where running the official, resource-heavy Bitwarden server isn't ideal — and serves as a private alternative to hosted services like 1Password.
Can I use official Bitwarden apps with Vaultwarden?
Yes. Vaultwarden implements essentially the full Bitwarden Client API, so the official Bitwarden browser extension, desktop, mobile, and CLI apps connect to it without modification — you just point the app's server URL at your Vaultwarden instance. The clients can't tell they're talking to Vaultwarden instead of Bitwarden's cloud.
How is Vaultwarden different from the official Bitwarden server?
Vaultwarden ships as one lightweight Rust binary in a single container with SQLite by default (MySQL/PostgreSQL optional), idling at roughly 40 MB RAM — versus the official server's six containers plus SQL Server. It targets individuals, families, and small organizations, and unlocks premium features like TOTP storage, Sends, and attachments without a paid license.
Can I self-host Vaultwarden?
Yes, self-hosting is its purpose. Deploy it via official container images on ghcr.io, docker.io, or quay.io, or build the binary yourself, and pair it with a reverse proxy for HTTPS (required by the web vault and clients). It runs comfortably on a modest VPS or even a Raspberry Pi, and comes with an admin panel for configuration.
What features does Vaultwarden include?
Vaultwarden covers the Bitwarden API surface: personal and Organization vaults, collections, password sharing, groups, roles, policies, Send, attachments, website icons, a personal API key, two-factor authentication (TOTP, email, Duo, YubiKey, FIDO2/WebAuthn), Emergency Access, username generator with SimpleLogin/AnonAddy/Firefox Relay, and live sync. Note it does not include enterprise SSO (SAML/OIDC) or directory sync.
Looking for contributors
This project is actively seeking help, join the community!
Repository details
Updated 8/6/2026, 3:00:30 PM
View RepositoryRepository activity
Compare Vaultwarden with
Similar open source alternatives
KeePassXC
Cross-platform community-driven port of KeePass Password Safe.
1Password
Passbolt
Open-source, security-first password manager designed for teams. End-to-end encryption, granular access control, and self-hostable.
1Password
AliasVault
Privacy-first password manager with built-in email aliasing. Fully encrypted and self-hostable.
1Password
Bitwarden
Bitwarden infrastructure/backend (API, database, Docker, etc).
1Password


