If you want a password manager where you hold the data — not a company's cloud — self-hosting is the answer. The appeal is real: your encrypted vault lives on infrastructure you control, with no third-party provider in the trust chain. The trade-off is just as real: you become responsible for updates, backups and security. This guide ranks the serious self-hosted options honestly, and helps you decide whether self-hosting is actually right for you.
The short answer
- For most people: Vaultwarden. A lightweight, open-source server that speaks the Bitwarden protocol, runs in one Docker container (even on a Raspberry Pi), and works with the official Bitwarden apps. Best balance of power and simplicity. See our Vaultwarden self-host tutorial for the full setup.
- Want the official stack: Bitwarden self-host. The vendor's own server — more resource-hungry, but first-party.
- Prefer file-based, no server: KeePassXC + your own sync. A local encrypted database you sync yourself.
- Team / business self-hosting: Passbolt or Psono. Built around shared access and granular permissions.
What "self-hosted" really buys you (and costs you)
What you gain:
- Control & privacy. The encrypted vault sits on your hardware or VPS. No third-party provider can be compelled, breached, or change terms in a way that exposes your data.
- No subscription for the software itself (open-source).
- Auditability. These projects are open-source, so the code can be inspected.
What you take on:
- Maintenance. Security updates, TLS certificates, server hardening — on you.
- Backups. If you don't back up, nobody does. A lost disk = a lost vault.
- Uptime. If your server is down and you're travelling, so is your vault (mitigated by offline app caches).
In short: self-hosting trades convenience for control. That's a great trade if you'll actually maintain it.

The options, honestly
Vaultwarden — the default pick
Vaultwarden (formerly "bitwarden_rs") is an unofficial, Rust-based server that implements the Bitwarden API. It's remarkably light — a single Docker container that happily runs on a Raspberry Pi or the cheapest VPS — yet it works with all the official Bitwarden clients (desktop, mobile, browser extensions). You get organisations, attachments, and 2FA without paying for Bitwarden's hosted Premium. For the overwhelming majority of self-hosters, it's the right answer. Our step-by-step Vaultwarden tutorial covers Docker Compose, a reverse proxy, TLS and automated backups.
Bitwarden self-host — the official route
Bitwarden offers an official self-hosted server. It's first-party and fully featured, but it's a heavier, multi-container deployment (more RAM, more moving parts) than Vaultwarden. Choose it if you specifically want the vendor's own stack and don't mind the extra resource footprint.
KeePassXC + your own sync — no server at all
KeePassXC is a local, open-source manager that stores everything in a single encrypted .kdbx file. There's no server to run: you sync that file yourself with Syncthing, Nextcloud, or any storage you trust. It's the most minimal, most private option — and the most manual, since you manage sync and conflict resolution. Excellent for people who want zero server and full file ownership.
Passbolt — team-oriented
Passbolt is built for teams: granular sharing, user/group permissions, and an admin model designed for organisations. It's heavier to deploy than Vaultwarden and aimed at collaborative use rather than a single person. A strong pick for a small company that wants self-hosted, shared credentials.
Psono — business self-hosting
Psono is another team/business-focused self-hosted manager with role-based access and an API. Like Passbolt, it's overkill for an individual but well-suited to organisations that want to keep credentials on their own infrastructure.
Who should actually self-host?
- Yes, self-host if you're comfortable running a small server, you'll keep it updated and backed up, and control is a real priority for you. Start with Vaultwarden.
- Probably not if you want something that "just works" everywhere with zero maintenance, or you're not confident about TLS, updates and backups. A misconfigured self-hosted vault is riskier than a good managed one.
If that second description is you, there's no shame in it — a reputable, open-source managed manager gives you most of the privacy benefits without the server admin.
Don't want to run a server? Try Proton PassOpen-source, end-to-end encrypted, Swiss, independently audited — with a free tier. The managed alternative to self-hosting.→The bottom line
In 2026, the best self-hosted password manager for most people is Vaultwarden — light, open-source, Bitwarden-compatible, and easy to run. KeePassXC suits those who want no server at all; Passbolt and Psono fit teams. Whichever you pick, remember the two rules that make or break self-hosting: keep it updated, and back it up automatically. And if running a server isn't for you, a managed open-source manager is a perfectly honest choice.
★ Audit Cure53 2024 · ✓ Plan gratuit · Cross-platform
Get NordPass30-day money-back guarantee · Free plan available→