Comparisons anchored on self-hosted Bitwarden, the AGPL-3.0 password manager server with Bitwarden-licensed paid modules: against Vaultwarden and Passbolt, and its own deployment and hosting options.
Running the official Bitwarden server yourself against Vaultwarden, the Rust reimplementation of the Bitwarden client API: licensing, which features need a paid license, resource needs, databases, SSO and who supports each when something breaks.
Two self-hostable team password managers with different designs: Bitwarden's vault model against Passbolt's OpenPGP per-user encryption and browser-extension-first approach. Compares editions, SSO and directory sync, imports, export controls and deployment.
The self-hosted password manager shortlist compared on license and paid features, encryption model, SSO and LDAP, supported databases, installation footprint and support, with a verdict by scenario for small teams, regulated companies and IT departments.
The question companies ask once a pilot works: Vaultwarden's README disclaims affiliation and liability and points users to backups, while Bitwarden offers licensed features and vendor support. Covers support, auditability, licensing and when each is defensible.
Bitwarden's two self-hosted deployment options: the standard multi-container installation with MSSQL against the single-container lite deployment with a choice of databases, which Bitwarden positions for personal use and home labs. Covers sizing and fit.
Staying on Bitwarden's cloud versus running the same server yourself: licensing tied to the installation ID, data region matching, the documented cloud to self-hosted migration and what it leaves behind, and the operating work self-hosting adds.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.