👍 What we like
- Vault encrypted client-side: the server never sees passwords in plain text
- Vaultwarden works with the official Bitwarden apps (browser, mobile, desktop, CLI)
- Minimal hosting cost: a small VPS or a mini PC is enough
- KeePassXC lets you do without a server entirely
👎 What to watch
- Backups, updates and uptime are your responsibility
- No native SAML SSO or SCIM in Vaultwarden (OpenID Connect SSO only)
- Passbolt is heavier to deploy (PHP, MySQL/MariaDB, GPG keys)
- Manual sync and possible conflicts with KeePassXC
📑 Contents ▾
- 01 Comparison table
- 02 Vaultwarden: the default choice
- 03 Passbolt: the vault designed for teams
- 04 KeePassXC + sync: no server at all
- 05 Psono: for technical secrets
- 06 Which one for your profile
- 07 Where to host the server
- 08 What really protects the vault: master password and backup
- 09 Hosting nothing: LastPass, 1Password, Bitwarden or NordPass
- 10 FAQ
- Our picks
For an individual, a family or a homelab, the best password manager to self-host is Vaultwarden: it is lightweight and works with every official Bitwarden app. A team that shares sensitive secrets and needs an audit log should rather pick Passbolt; someone who wants no server at all, KeePassXC with a synced file. If you do not want to deal with backups or updates, a commercial service such as Bitwarden, 1Password or LastPass is safer than a neglected server: more on that further down.
This guide compares these tools based on their documentation, on the criteria that actually decide: encryption model, team sharing, client quality, deployment effort and user profile.
Comparison table
| Criteria | Vaultwarden | Passbolt | KeePassXC + sync | Psono |
|---|---|---|---|---|
| Model | Bitwarden-compatible server | Team-oriented server | Local encrypted file | Server |
| Technology | Docker (Rust) | Docker (PHP) | Local app + file sync | Docker |
| Encryption | AES-256, client-side | Per-user OpenPGP | AES-256 or ChaCha20 (KDBX4) | Client-side |
| Clients | All Bitwarden apps | Browser, desktop, mobile | Desktop + third-party KDBX apps | Browser, mobile |
| Browser autofill | Official Bitwarden extensions | Passbolt extension | KeePassXC-Browser extension (app open) | Psono extension |
| Team sharing | Yes (organizations) | Yes (core of the product) | Basic (shared file) | Yes (granular) |
| Resources | Very light | Moderate | No server | Moderate |
| Deployment | Very easy | Moderate | Nothing to deploy | Moderate |
| Two-factor authentication | TOTP, WebAuthn, YubiKey | TOTP, YubiKey (depending on edition) | YubiKey challenge-response | TOTP, YubiKey |
| License | AGPL-3.0 | AGPL | GPL | Apache 2.0 |
| Best for | Individual, family, homelab | SMEs, structured teams | Purist, offline | Technical team |
Vaultwarden: the default choice
Vaultwarden is a lightweight reimplementation of the Bitwarden server, written in Rust. It speaks the same protocol, so every official Bitwarden client works with it: browser extensions, iOS and Android apps, desktop clients, CLI. You get Bitwarden’s ecosystem and ease of use, on your own server and without a subscription.
On resources, it is hard to get lighter: a SQLite database by default and a Docker deployment in minutes. Encryption happens client-side before anything is sent, so the server never sees your passwords in plain text; key derivation uses PBKDF2 by default, or Argon2id as an option. Two-factor authentication supports TOTP, WebAuthn and YubiKey, and organizations allow sharing within a family or a small team.
Its limits show at scale: it is not designed for hundreds of users with enterprise access management. It has no native SAML SSO or SCIM (only OpenID Connect SSO), an area where Bitwarden’s commercial offer or Passbolt take the lead. For personal or family use, those limits never come into play.
Step-by-step installation is covered in our Vaultwarden with Docker and HTTPS tutorial, and the head-to-head with the official service in Vaultwarden, Bitwarden or Passbolt.
Passbolt: the vault designed for teams
Where Vaultwarden is user-centric, Passbolt is centred on secure team sharing. It relies on OpenPGP: each user has their own key pair, and sharing a secret means encrypting it for the public keys of the authorized recipients. This elegant, auditable model suits technical teams that share infrastructure secrets (API keys, server access, shared credentials).
Permission management is fine-grained: groups, roles, per-resource permissions, audit log. The Community edition is free and open source; the Pro editions add SSO, more detailed logging and support.
In return, deployment is heavier (PHP, a MySQL or MariaDB database, GPG key generation, strict HTTPS required), and day-to-day use is less smooth than Bitwarden: the extension has to decrypt with the private key, which adds steps. For purely personal use it is oversized; for an SME or a DevOps team it is a very good choice.
KeePassXC + sync: no server at all
KeePassXC flips the model: no server. Your passwords live in an encrypted file (KDBX4 format, AES-256 or ChaCha20, Argon2 key derivation) that you sync yourself: Syncthing, Nextcloud, a Git repository, or even a public cloud, since the file is encrypted.
The advantage is radical: no server-side attack surface, no open port, no service to maintain. The file is useless without the master password, optionally combined with a key file or a YubiKey in challenge-response mode.
The drawbacks come from having no server. Syncing across devices is up to you and can create conflicts if you edit the database on two devices at the same time. Team sharing is limited to a common file, without fine-grained permissions. Browser autofill goes through the KeePassXC-Browser extension, which needs the desktop app open, and on mobile you need a third-party KDBX-compatible app. To sync the file without a public cloud, peer-to-peer Syncthing or your own Nextcloud does the job: see our tutorial hosting Nextcloud on a VPS.
Psono: for technical secrets
Psono is an open-source server password manager aimed at teams and infrastructure secrets: client-side encryption, granular sharing, an API for automation (fetching secrets in a CI/CD pipeline or a script) and hardware key support. Its interface is plain and technical.
It sits between Vaultwarden (general public) and Passbolt (teams, OpenPGP), with a “secrets management” approach close to HashiCorp Vault but lighter. For a DevOps team mixing human passwords and machine secrets, it is a credible option; for an individual, Vaultwarden remains simpler.
Which one for your profile
Individual or family. Vaultwarden: the best clients, the simplest deployment and the lightest footprint.
Secrets of an SME or a structured team. Passbolt: per-user OpenPGP keys, fine-grained permissions and auditing.
Security purist, offline. KeePassXC with your own sync: no network attack surface, an open and durable format.
Technical team that automates. Psono, or Vaultwarden and its CLI: the API makes the difference in CI/CD pipelines.
You do not want to administer anything. A commercial service, described in the next section.
Where to host the server
Vaultwarden runs easily on the smallest VPS: an entry-level plan at Hetzner or OVHcloud is enough. At home, an always-on low-power mini PC does the same job, for example the Beelink Mini S12 Pro (Intel N100, 16 GB) or the Beelink EQ14 (Intel N150, dual 2.5 GbE ports). To choose the machine: our guide to the best mini PCs for a homelab. Passbolt and Psono need a little more memory but remain modest; KeePassXC needs no machine at all.
In every case, put the service behind an HTTPS reverse proxy and never expose it without two-factor authentication.
What really protects the vault: master password and backup
Whatever the tool, two things matter more than the choice of software:
- The master password. It is the only secret protecting all the others: a long, unique passphrase of at least 4 to 5 random words. No encryption saves a vault protected by “password123”.
- The backup. A lost vault means all your access is gone. Back up the database regularly (Vaultwarden’s SQLite, the KDBX file, a Passbolt export), encrypted and off the server: our guide automatic backup with Restic and Backblaze covers exactly this.
Add two-factor authentication, ideally a hardware key such as a YubiKey, supported by all four solutions.
Hosting nothing: LastPass, 1Password, Bitwarden or NordPass
Self-hosting your vault means owning backups, updates and uptime. A reputable commercial service has a dedicated security team that you do not have: if you do not plan to maintain a server, it is the more prudent choice. The vault, however, stays with a third party.
- Bitwarden is the natural bridge with this page: Vaultwarden uses its official apps. Its code is public and auditable, with a free plan and paid plans. Since the clients are identical, you can start on Bitwarden’s cloud and move to Vaultwarden later through an export and an import. See Bitwarden on Amazon
- 1Password is known for its ease of use; the Families plan lets family members share vaults, up to 5 accounts. See 1Password Families on Amazon
- LastPass offers an encrypted vault synced across devices, with password generation and autofill. See LastPass Premium on Amazon
- NordPass is an end-to-end encrypted service with nothing to administer. See NordPass
Be wary of free plans that are too limited, and pick a tool the whole family or team will actually use: a manager that is too complex ends up abandoned.
FAQ
Is self-hosting your passwords safer than a commercial service?
Not automatically. Self-hosting is safer if you apply good practices: HTTPS, two-factor authentication, a strong master password, regular updates, encrypted backups. Done well, it removes the risk of a breach at a third party exposing your data; done badly, it creates that risk at home.
Is Vaultwarden as secure as official Bitwarden?
Encryption is the same, since it happens client-side with the same protocol. The difference lies in maintenance: Vaultwarden is run by a community, Bitwarden by a company. Security depends mostly on how your server is configured.
Which solution for sharing passwords within a team?
Passbolt for a structured team that needs auditing and fine-grained permissions, Vaultwarden organizations for simple sharing within a family or small team, Psono if the team fetches secrets through an API. KeePassXC is the least suited to multi-user sharing.
Can I migrate from LastPass, 1Password or Bitwarden Cloud?
Yes. These managers export to CSV or JSON, a format you can import into Vaultwarden (through the Bitwarden clients), KeePassXC or Passbolt. Permanently delete the export file after migrating: it is a plain-text copy of all your secrets.
Do I need a hardware key like a YubiKey?
It is not mandatory, but it is strongly recommended for the vault that protects all your access. A hardware key (WebAuthn/FIDO2 or challenge-response) resists phishing and TOTP code theft, and all four solutions compared here support it.
How does KeePassXC sync between my PC and my phone?
You sync the encrypted KDBX file with the tool of your choice: Syncthing, a self-hosted Nextcloud, or a public cloud that will only ever see an encrypted file. To avoid conflicts, edit the database in one place at a time and let the sync propagate.
Key facts
Our picks
Affiliate links · same price for youBeelink Mini S12 Pro
- Intel N100
- 16 GB of RAM
Amazon · price and availability on the listing
Beelink EQ14
- Intel N150
- Dual 2.5 GbE ports
Amazon · price and availability on the listing
1Password Families
- Up to 5 accounts
Amazon · price and availability on the listing
See all our recommended gear in the shop.