Bitwarden and KeePassXC: What We Run
$47.88/yr + $0 — the whole stack the number that matters here
By Stan K.
Our two-manager stack: Bitwarden Families at $47.88/year for everything shared, and KeePassXC ($0, GPLv3) synced with Syncthing for the local vault. The honest costs of each — sync-conflict files you merge by hand, what Bitwarden Free actually loses, and when Vaultwarden makes sense.
We run two password managers on purpose, and the combination costs less than most people’s single subscription. Bitwarden covers everything shared — the household logins, the recovery codes, the accounts two people must both reach. KeePassXC holds the local vault that never touches a vendor’s server. Total bill: $47.88/year, which is one Bitwarden Families plan, plus zero dollars for the local half. Here is where each one earns its keep, and where each one honestly hurts.
The split, and why two
Bitwarden Families ($3.99/mo billed annually at $47.88, up to 6 users) is the shared layer: same apps on every device and browser, sharing collections with the household, 5 GB personal plus 5 GB family storage for attachments. Cloud-synced, zero-knowledge, and boring in the way infrastructure should be boring.
KeePassXC is the opposite bet. GPLv3, free forever — the project’s own words are “no cloud, no ads, no subscriptions.” The vault is one local .kdbx file; nothing leaves our machines except through the sync channel we chose ourselves, which is Syncthing moving the file peer-to-peer. The features people pay subscriptions for are in the free download: built-in TOTP and YubiKey challenge-response unlock. The trade is that the sync layer is now our problem — and it behaves like a file, because it is one.
The honest costs of the local vault
A file-based vault has a failure mode cloud managers don’t: simultaneous edits on two devices produce sync-conflict copies — the classic .kdbx-plus-file-sync experience, documented across every community that runs this stack. Syncthing faithfully preserves both versions, and a human merges them by hand. It is rare, it is manageable, and it is real: if two people edit the same vault at the same moment, someone is doing archaeology that evening. KeePassXC 2.8.0 added remote database synchronization support for external tools, but the conflict discipline stays yours.
The second cost is mobile. keepassxc.org endorses no mobile apps, so you pick a third-party companion — KeePassDX, Strongbox, KeePassium — and some of those are one-time paid. Budget a coffee’s worth of dollars and an hour of testing before you commit the family vault to one.
Free keeps unlimited passwords, passkeys and devices, sharing with one other user, Bitwarden Send, and encrypted export — the encryption is identical to the paid tier. Premium ($19.80/yr) adds built-in TOTP, 5 GB of attachments, vault health reports and emergency access. One ambiguity we won’t paper over: the help page’s wording lists hardware keys under free 2FA as well, and we couldn’t verify that in the vault UI — treat hardware-key support as a Premium question until you’ve tested it. Pay only if you can name the feature you’re paying for.
Vaultwarden, when you want Bitwarden’s apps on your own box
Bitwarden itself is open-source and self-hostable, and the lightweight community rewrite — Vaultwarden — runs the same apps against your own server on any small VPS. Same clients, same encrypted vault format, no per-seat bill. The price changes shape rather than disappearing: you are now the SRE. Updates, backups, TLS certificates and access control are yours, and a misconfigured server becomes your incident. We don’t self-host the shared layer — $47.88/yr to outsource on-call to Bitwarden is, per person, the cheapest line item in our stack — but if your threat model says “no third-party server at all,” it is the legitimate exit, and the per-person math tells you exactly what you’re giving up in dollars.
The full comparison — every vendor’s free tier, family division math and breach history — is in the Password Managers hub.