Open sourceINFO

Open Source Password Manager 2026: Open Server Code, No Vendor Lock-in

Bitwarden, KeePassXC, Vaultwarden and Proton Pass compared on what is really open (clients, server code), which export formats let you leave without lock-in, and which one to pick.

By Eric Gerard · Editor · PwdFortress9 min readPhoto via Pexels

"Open source" is one of the most reassuring labels a password manager can carry - and one of the most misunderstood. This guide explains what it actually means, why it matters for something as sensitive as your passwords, which managers are genuinely open source in 2026, and how to pick one. It's also honest about what open source does not guarantee.

Want to run it on your own server? See our self-hosted password manager guide.

Open source is one criterion among several. Our 4-question password manager quiz (who it is for, budget, privacy, where your passwords are today) gives you a single recommendation with its real price, including the free option when it is enough.

Open-source apps without anything to self-host: Proton Pass publishes its client apps under the GPL (its server is not open source) and has a free plan with unlimited devices and passkeys.

Black Friday 2026 (read on 17 November 2026): the Proton Pass partner page our link opens takes 60% off the first year of Pass Plus ($23.88 for the first 12 months, then $35.88 a year) and Pass Family ($33.48 for 6 accounts, then $59.88 a year), with the 30-day money-back guarantee. The order page shows the price for your country, so check it before paying. See the Proton Pass Black Friday offer

What is the best open source password manager in 2026?

  • Open source = the code is public and auditable. Anyone can read how the app encrypts and stores your vault.
  • Best all-round: Bitwarden - open source (GPL), independently audited, unlimited free tier, self-hostable.
  • Best fully offline: KeePassXC - local encrypted file, no cloud, GPL-licensed.
  • The original: KeePass - the long-standing Windows project that started the ecosystem (KeePass vs Bitwarden).
  • Self-hosted route: Vaultwarden - community server that speaks the Bitwarden protocol.
  • Partly open: Proton Pass - client apps are open source; the server is not.

What does "open source" actually mean for a password manager?

An open source password manager publishes its source code under a free licence (commonly the GPL). That gives you three concrete benefits:

  • Auditability. Security researchers - and you, if you read code - can inspect exactly how the app derives your encryption key and stores your vault. Closed apps ask you to trust their description; open ones let you verify it.
  • No vendor lock-in on the format. Open projects use documented vault formats, so you're not trapped if you want to move or self-host.
  • Verifiable trust. When encryption is implemented in the open, weaknesses tend to be found and fixed faster, and the community can confirm there's no hidden backdoor.

One important clarification: open source is about code transparency, not about price or hosting. An open source manager can still offer paid tiers, and it can run in the cloud or on your own server. The two ideas often overlap, but they're not the same thing.

A laptop screen displaying syntax-highlighted source code in a dark code editor - open source code anyone can read and audit.
A laptop screen displaying syntax-highlighted source code in a dark code editor - open source code anyone can read and audit.

Which password managers are genuinely open source?

LicenseOpen serverCloud syncSelf-hostableBest for
BitwardenGPLYesOfficial syncYesThe default pick, open source without giving up sync
KeePassXCGPLNo server at allNone, a local .kdbx fileN/AFull file ownership, fully offline
KeePassGPLNo server at allNone, a local .kdbx fileN/AThe original, and the format the family shares
VaultwardenOpen sourceYes (Rust re-implementation)YoursYes, even on a Raspberry PiSelf-hosting with the official Bitwarden apps
Proton PassGPL clients onlyNoOfficial syncNoStrong free tier, but "partly open"

Bitwarden - the default open source pick

Bitwarden is open source under the GPL, with its clients, server and SDK published on GitHub. It has been independently audited (including a Cure53 review), offers a genuinely unlimited free tier across unlimited devices, and can be self-hosted. For most people who want open source without giving up convenience or cross-device sync, it's the natural choice. Our full Bitwarden review goes deeper.

KeePassXC - best fully offline

KeePassXC is a community-driven, cross-platform manager (GPL-licensed) that stores everything in a single encrypted .kdbx file. There's no cloud and no server - you keep the file and sync it yourself if you want. It's the most private, most local option, ideal for power users who want full file ownership. The trade-off is a steeper learning curve and manual sync. Wondering how it relates to the original project? Both read the same database file - see KeePass vs KeePassXC for what actually separates them.

KeePass - the original

KeePass is the long-standing, open source Windows project (GPL) that defined the .kdbx format the whole KeePass family uses. It's lighter on polish than KeePassXC's modern cross-platform interface, but it remains a respected, audited foundation that a large ecosystem of compatible apps builds on.

Vaultwarden - open source self-hosting

Vaultwarden is a community-built, Rust-based server that re-implements the Bitwarden API. It's open source, runs in a single lightweight container (even on a Raspberry Pi), and works with the official Bitwarden apps - so you get an open, self-hosted vault without running Bitwarden's heavier official server. See our self-hosted password manager guide for where it fits.

Proton Pass - partly open

Proton Pass open-sourced its client apps (web, mobile and browser extensions) under the GPL, which means the code that runs on your devices can be inspected. Its server, however, is not open source - so it's "partly open" rather than fully open like Bitwarden. It's still end-to-end encrypted and has a strong free tier; just know the distinction. We compare the two in Proton Pass vs Bitwarden. For the full security picture, including the audits and encryption specifics, read is Proton Pass safe.

Try Proton Pass free - open-source apps →Free plan, no card · unlimited devices · passkeys included · nothing to self-host · Black Friday: 60% off Pass Plus the first year→

Which ones let you leave without vendor lock-in?

Open code is half of the answer. The other half is whether you can walk away with your vault, and whether the service keeps working if the company changes its prices or shuts down.

Open clientsOpen server codeCan run without the vendorExport formats
KeePassXCYes (GPL)No server neededYes, the vault is a local .kdbx fileNative .kdbx, CSV, KeePass XML, HTML
KeePassYes (GPL)No server neededYes, same .kdbx formatNative .kdbx, CSV, KeePass XML
BitwardenYes (GPL)Yes, on GitHubYes, self-host Bitwarden or switch to Vaultwarden with the same appsJSON, encrypted JSON, CSV, .zip with attachments
VaultwardenUses the Bitwarden appsYes (AGPL, Rust)It is the self-hosted optionSame exports as Bitwarden
Proton PassYes (GPL)NoNo, sync depends on Proton's serversJSON, CSV, PGP-encrypted export

How to read it:

  • Least lock-in: KeePassXC. There is no account to close. The .kdbx file is the vault, and KeePass, KeePassXC, KeePassDX (Android) and Strongbox (iOS) all open it.
  • Open and synced: Bitwarden. If Bitwarden the company ever stopped suiting you, you could point the same apps at your own Vaultwarden server instead of migrating. Our Bitwarden export guide shows which format keeps what.
  • Partly open: Proton Pass. The apps are auditable and the export is complete, but you cannot host the server yourself. That is a fair trade if you want aliases and nothing to maintain, not if "no lock-in" means "no dependency on one company".

Why choose an open source password manager?

  • You hold the most sensitive data you own. For a password vault, "trust me" is a weak promise. Open code lets that trust be checked rather than assumed.
  • Audits plus open code reinforce each other. Independent audits (like those Bitwarden has published) verify a snapshot; open source keeps the code under continuous community review between audits.
  • Freedom to leave. Open formats and self-host options mean you're never hostage to one company's pricing or terms.
Try Bitwarden - open source & audited →GPL-licensed · independently audited (Cure53) · unlimited free tier · self-hostable via Vaultwarden→

What are the limits of open source password managers?

Open source is a real advantage, but it isn't a guarantee on its own:

  • Open code ≠ automatically audited. Anyone can read the code; that doesn't mean experts already have. The strongest reassurance is open source plus a published independent audit.
  • You still need a strong master password and MFA. No amount of open code helps if your master password is weak or reused. See how to create a strong password.
  • Self-hosting shifts responsibility to you. Running your own server (Vaultwarden, Bitwarden self-host) means you own updates, TLS and backups. A misconfigured self-hosted vault can be less safe than a reputable managed one.
  • "Open" can be partial. As with Proton Pass, only part of the stack may be open. Check whether it's the client, the server, or both.

How do you choose between them?

  • Want open source that "just works" everywhere? Bitwarden - open, audited, free tier, optional self-host.
  • Want zero cloud and full file control? KeePassXC (or KeePass on Windows).
  • Want to self-host an open vault? Vaultwarden, with Bitwarden's clients.
  • Want end-to-end encryption with open client apps and built-in aliases? Proton Pass - just note its server isn't open.

The bottom line

In 2026 the safest open source choice for most people is Bitwarden: its code is public, it's been independently audited, the free tier is genuinely unlimited, and you can self-host it. KeePassXC and KeePass win for fully offline, file-based control, and Vaultwarden brings open self-hosting. Treat Proton Pass as partly open. And remember the honest caveat: open source is a powerful trust signal, but a strong master password and MFA still do most of the heavy lifting.

Going further

Editorial overview based on the publicly documented licensing, audit and architecture of each manager as of 2026. Commercial links carry the rel="sponsored nofollow" attribute; an affiliate commission may apply at no extra cost to you.

Frequently asked questions

What is an open source password manager?

It's a password manager whose source code is published under a free/open licence (for example GPL), so anyone can read it, audit it, and verify how it stores and encrypts your data. Bitwarden, KeePassXC and KeePass are the best-known examples. 'Open source' refers to code transparency - it doesn't automatically mean self-hosted or free, though many open source managers are both.

Is an open source password manager safe?

Yes, when it uses client-side (zero-knowledge) encryption so the provider never sees your vault. Open source adds transparency: the code can be inspected and several of these tools have had independent security audits. But safety still depends mostly on a strong, unique master password and enabling MFA - open code is a trust advantage, not a magic shield.

Which open source password manager is best?

For most people, Bitwarden: open source under GPL, independently audited, with a genuinely unlimited free tier and the option to self-host via Vaultwarden. KeePassXC is the best fully offline, file-based choice. KeePass is the original Windows project. Proton Pass open-sourced its client apps, though its server is not open.

Which open source password manager has no vendor lock-in?

KeePassXC and KeePass have the least lock-in: the vault is a .kdbx file in a documented format that dozens of apps can open, with no server to depend on. Bitwarden comes next: clients and server are open, you can move to a self-hosted Vaultwarden server and keep the same apps, and the vault exports to JSON or CSV. Proton Pass has open client apps but a closed server, so leaving means exporting (JSON, CSV or PGP-encrypted) and importing elsewhere.

Is Bitwarden really open source?

Yes. Bitwarden's clients, server and SDK are published on GitHub under open source licences, and the project has undergone independent security audits (including by Cure53). Vaultwarden is a separate, community-built server that re-implements the Bitwarden API and is also open source.