Bitwarden and KeePassXC both show up on every "best password manager for teams" list, and they sit in genuinely different parts of the market. Bitwarden is the open-source value pick — fully auditable, self-hostable, with a free tier that actually scales. KeePassXC, by contrast, is free, local-first, open-source vault file format — provably zero-knowledge, but with no native sync, SSO, SCIM or audit log.
This comparison is written for the people actually making the call: founders, IT leads and ops folk at startups, agencies and small teams. No affiliate rankings, no "best of" filler — just the trade-offs that matter once more than one person touches the vault.
Quick verdict
Pick Bitwarden if teams who want linear pricing, open source, or self-hosting. Predictable per-seat cost and an auditable client. Admin UI is plainer.
Pick KeePassXC if tech-savvy or air-gapped teams comfortable owning the sync layer. Free and provably zero-knowledge — but you wear the sync, mobile and access-control layers yourself.
Both are zero-knowledge and both have a defensible recent security story. The choice is almost never about cryptography — it's about collaboration model, governance, and how much per seat per month you want to spend.
Team pricing at a glance
| Feature | Bitwarden | KeePassXC |
|---|---|---|
| Smallest team planAll prices USD, billed annually unless noted. Verify on vendor sites before buying. | Teams: $4/user/mo | Free (GPL-3.0) |
| Next tier for growing teams | Enterprise: from $6/user/mo | Free — no paid tiers |
| Free tier available | ||
| SSO (SAML / OIDC) | Enterprise only | |
| SCIM provisioning | Enterprise only |
Collaboration model
| Feature | Bitwarden | KeePassXC |
|---|---|---|
| Shared vaults / collections | Yes — Collections | File-level only (.kdbx on shared storage) |
| Per-item permissions | ||
| External / one-time secure share | Yes — Bitwarden Send | |
| Group-based sharing | Via KeeShare or multiple .kdbx files | |
| Activity / audit log | Teams and above |
Security & transparency
| Feature | Bitwarden | KeePassXC |
|---|---|---|
| Zero-knowledge end-to-end encryption | ||
| Cipher | AES-256-CBC + HMAC | AES-256 / Twofish / ChaCha20 |
| Key derivation | Argon2id (default) or PBKDF2 | Argon2id (default) or AES-KDF |
| Open-source clients | ||
| Self-hosting option | Local-first by design | |
| Published independent audit | ANSSI CSPN (2025), BSI/mgm (2024–25 for KeePass), Molotnikov (2023) | |
| Publicly disclosed vault breach | No customer vault breach | No vault breach; KeePassXC NOT affected by CVE-2023-32784 (KeePass2) |
Pricing for teams: where the real difference is
Bitwarden's Teams plan is a flat $4/user/month from seat 1 to seat ∞, with Enterprise around $6/user/month adding SSO, policies and directory sync. Linear and predictable, with no seat-count cliff.
KeePassXC is free under GPL-3.0. There is no SaaS, no per-seat cost, and no vendor invoice — the trade-off is that you absorb the operational cost of sync, mobile clients and access control.
For a fast-growing team, the slope matters as much as the starting price. Model it at the size you actually expect to be in 12 months — not the size you are today.
How teams actually share credentials
Bitwarden. Organisations with Collections give per-item RBAC, Bitwarden Send handles one-time external sharing with no recipient account, and audit logs are available from the Teams tier upward.
KeePassXC. Sharing means putting a .kdbx file on shared storage (Nextcloud, SMB, Syncthing, Dropbox) and accepting that everyone with the master key sees everything. KeeShare lets you sync a subset of groups, but there's no per-user RBAC and no audit log.
The everyday question is: when a contractor joins on Monday and leaves on Friday, how much work is it to give them access to exactly the credentials they need, watch what they touched, and revoke cleanly? That's where the daylight between these two shows up.
Security architecture
Bitwarden. Bitwarden's clients and server are fully open source under AGPL/BSL — you (or any security firm) can read exactly what runs. Argon2id is the default KDF, which is materially harder to attack on GPUs than PBKDF2.
KeePassXC. Encrypts databases with AES-256, Twofish or ChaCha20, with Argon2id as the default KDF and tunable parameters. ANSSI CSPN-certified in 2025 and unaffected by CVE-2023-32784 (which hit mainline KeePass 2.x). There's no server to breach because there is no server.
If you're forced to choose on cryptography alone, modern AEAD ciphers (AES-GCM, XChaCha20-Poly1305) paired with a memory-hard KDF (Argon2id) are the bar. Both vendors are inside that range; the harder differences are open-source posture, audit history, and whether you can self-host.
Admin & governance for teams
Both products support some flavour of role-based access, forgotten-password recovery, and audit logging on the right tier. Where they diverge is on the boring-but-critical stuff: SSO, SCIM provisioning, and whether group policies can keep up with how your team actually grows.
SSO tier: Bitwarden — Enterprise only; KeePassXC — not available. SCIM tier: Bitwarden — Enterprise only; KeePassXC — not available.
If Okta, Entra ID or Google Workspace SSO is non-negotiable from day one, factor the tier price into the per-seat number — it's often the thing that flips the cheaper-on-paper option into the more expensive real-world bill.
Bitwarden
Pros
- Linear $4/user/month pricing that scales predictably
- Open-source clients and server you can audit or self-host
- Argon2id by default — stronger KDF than the industry norm
- Genuinely usable free tier for individuals
Cons
- Admin UI is functional but less polished
- SSO is gated behind Enterprise
- Some power features hide in submenus
- Self-hosting is great in theory, real work in practice
KeePassXC
Pros
- Free forever, GPL-3.0, no vendor lock-in
- ANSSI CSPN-certified in 2025 (KeePassXC 2.7.9)
- Argon2id by default with tunable hardness
- Air-gap capable; nothing leaves your network unless you put it there
Cons
- No built-in sync, audit log, SSO, SCIM or per-user permissions
- Mobile apps are third-party (KeePassium, Strongbox, KeePassDX, KeePass2Android)
- Concurrent writes over shared storage can lose data
- Offboarding requires rotating the master password and redistributing the key
A third option worth considering
Bitwarden vs KeePassXC is really a debate about how much collaboration you're willing to give up to get the trust model you want. One side is a managed SaaS with shared vaults; the other is a local file you sync yourself. Pwdly is built for the team in the middle — people who want real per-project sharing without running a sync script or paying for a heavy enterprise plan to get it.
- Per-project vaults. Most teams don't share "everything with everyone" — they share by client, repo or product. Pwdly makes that the primary unit, not an afterthought folder.
- $2/user/month, flat. No seat-count cliff, no SSO upsell on the cheapest paid plan. See the full pricing.
- XChaCha20-Poly1305 + Argon2id under the hood. The cipher explainer walks through why those defaults matter.
- Trade-offs we own. No breach monitoring (we literally can't read your data), no self-hosting yet, no browser extension on day one. The security page has the honest list.
If your team has outgrown a shared KDBX but isn't ready to hand credentials to a vendor without a clear story, Pwdly is the in-between worth trialling.
Frequently asked questions
Is Bitwarden or KeePassXC better for a small team?
Bitwarden fits best when teams who want linear pricing, open source, or self-hosting, while KeePassXC is the stronger choice when tech-savvy or air-gapped teams comfortable owning the sync layer. Model both at the seat count you expect in 12 months — the cheaper option at 5 seats isn't always the cheaper option at 25.
Which has stronger encryption — Bitwarden or KeePassXC?
Bitwarden uses AES-256-CBC + HMAC with Argon2id (default) or PBKDF2. KeePassXC uses AES-256 / Twofish / ChaCha20 with Argon2id (default) or AES-KDF. Both are zero-knowledge. In practice the cipher choice is rarely the differentiator — KDF (Argon2id vs PBKDF2), open-source clients, and audit history matter more.
Does either support SSO and SCIM on the cheapest team plan?
Bitwarden: SSO Enterprise only, SCIM Enterprise only. KeePassXC: SSO not available, SCIM not available. If SSO is non-negotiable, price it on the tier that includes it, not the entry tier.
Has either vendor had a vault breach?
Bitwarden: No customer vault breach. KeePassXC: No vault breach; KeePassXC NOT affected by CVE-2023-32784 (KeePass2). A clean record isn't a guarantee, but a known prior incident materially raises the cost of trust.
Keep comparing
- 1Password vs BitwardenTeam-focused, vendor-neutral breakdown.
- LastPass vs BitwardenTeam-focused, vendor-neutral breakdown.
- 1Password vs DashlaneTeam-focused, vendor-neutral breakdown.
- 1Password vs LastPassTeam-focused, vendor-neutral breakdown.
- Bitwarden vs DashlaneTeam-focused, vendor-neutral breakdown.
- Dashlane vs LastPassTeam-focused, vendor-neutral breakdown.
Also worth a read: The XChaCha20-Poly1305 explainer, our security model, and the free password generator.
Sources & further reading
- Bitwarden — Business pricing
- Bitwarden Security white paper
- Bitwarden — Encryption (AES-CBC + HMAC, Argon2id)
- KeePassXC — Homepage
- KeePassXC — Independent audits
- ANSSI CSPN certificate for KeePassXC 2.7.9 (2025)
- CVE-2023-32784 (KeePass2 — KeePassXC unaffected)
- KeePassXC — KeeShare
Worth fact-checking
- Vendor pricing for both Bitwarden and KeePassXC has changed more than once in the past 24 months — verify on the official site before purchasing.
- SSO / SCIM tier inclusion can change between plans; confirm with vendor sales for your exact seat count.
Last updated May 2026. Vendor pricing and features change frequently — always confirm on the official site before purchasing. Pwdly is not affiliated with 1Password, Bitwarden, LastPass, or Dashlane.