Open-Source 1Password Alternatives: The License Table Nobody Publishes
By the SoftSea editorial team
Photo: Bibek ghosh / Pexels
"Open source" is three questions, not one
A password manager is not one piece of software. It is a set of client apps, usually a sync server, and a vault format, and each of the three can carry a different license. Lists of open-source 1Password alternatives almost never separate them, which is how a reader ends up believing a tool is open source whose server they could not legally run, or dismissing a tool whose vault format is an open standard even though its best app is commercial. This guide separates the components for the four names that matter (Bitwarden, KeePassXC, Passbolt, and Proton Pass, with Vaultwarden as the special case) and states, for each, what is open, what is not, and what that means for the thing open source is supposed to buy you: the ability to inspect the code and to keep using it if the vendor changes direction.
1Password itself is the closed baseline: no open clients, no open server, no self-hosting at any price, at $3.99 per month billed annually for Individual. Every tool below beats it on at least one component. None of them matches its polish on all of them, which is the trade this entire category makes.
Tool
Clients
Server
Format
License summary
Bitwarden
Open source
Open source, split licenses
Proprietary vault, full export
AGPL and Bitwarden License by component
KeePassXC
Open source (GPLv3)
No server exists
KDBX, an open standard
GPLv3 throughout
Passbolt
Open source
Open source (AGPLv3)
OpenPGP-based
AGPLv3
Proton Pass
Open source
Closed
Proprietary vault, full export
Open clients only
Vaultwarden
Uses Bitwarden's clients
Open source (AGPL-3.0)
Bitwarden-compatible
AGPL-3.0, unofficial project
Bitwarden: open, with a split to understand
Bitwarden is genuinely open source and genuinely more complicated than the label. Its codebase is divided between components under AGPL and components under the Bitwarden License, a source-available license with more restrictions, and which parts fall where has shifted over the years, including a 2024 controversy over client licensing that the project publicly clarified. The practical summary for a user: the clients and server can be inspected, the server can be self-hosted (the self-hosted guide covers how), and the free plan (unlimited devices and passwords) plus Premium at $1.65 per month billed yearly make it the default open answer for most people. The practical summary for a purist: read the current license files for the components you care about, because "Bitwarden is AGPL" and "Bitwarden is proprietary" are both sentences someone on the internet is currently defending, and both are incomplete.
Interactive tool
Comparison Builder
Pick two or three products and see them side by side on the numbers that decide the purchase.
Measure
Bitwarden
KeePassXC
Passbolt
Starting paid price
$1.65 per user/mo, billed annually
Free
$4.9 per user/mo, billed annually
Free option
Free plan: always free, unlimited passwords on unlimited devices
Free plan: the whole product is free and open source under GPLv3; there is nothing to buy
Free plan: the self-hosted Community Edition is free forever with unlimited users under AGPLv3
Plans
Free: free · Premium: $1.65/user/mo annual · Families: $3.99/user/mo annual · Teams: $4/user/mo annual · Enterprise: not published
KeePassXC: free
Community Edition (Self-Hosted): free · Pro: $4.9/user/mo annual · Enterprise: not published
Platforms
Web
Windows, macOS, Linux
Web, Windows, iOS, Android, Linux
Best for
budget users, privacy-focused teams, self-hosters
local-first and offline users, anyone refusing a subscription on principle, technical users who manage their own backups
technical teams that self-host, companies that need a team vault under their own control, open-source password management for business
Strengths
Free tier has no device or password limits; Open source and auditable; Self-hosting available
No vendor cloud exists, so there is no vault server to breach; The KDBX format is an open standard read by many compatible apps; Works fully offline on every desktop platform
Built for team sharing from the first commit, not bolted on; End-to-end encryption based on OpenPGP, stated precisely by the vendor; The free edition has no user cap, unusual for a team vault
Watch out for
Interface is plainer than paid rivals; The built-in authenticator and file attachments sit on Premium, not Free
Sync is your problem: a file in cloud storage or a sync tool you run; No official mobile app; compatible third-party apps fill the gap; Sharing means sharing a file or a second database, not a shared vault
Self-hosting is the default path, so someone owns the server; Browser-first: desktop and mobile coverage is thinner than 1Password; Pro has a 10-user minimum, so tiny teams pay for seats they may not fill
Lowest entry price: KeePassXC at Free per month flat. Real free plan: Bitwarden, KeePassXC, Passbolt. Entry price is the floor, not the decision: check the plan line above for the tier that actually includes the feature you need.
All figures from vendor pricing pages, checked November 18, 2026. Some vendors price by contacts, tasks, or operations instead of seats; those notes are in the plan data and the linked pricing guides.
KeePassXC: the cleanest license story in the category
KeePassXC is GPLv3, through and through, and its architecture makes the license question simpler by deleting the server: there is no vendor cloud, no account, and nothing to license but the app. The vault format, KDBX, is an open standard implemented by many independent apps across every platform, which is the strongest continuity guarantee in this guide. If KeePassXC's maintainers stopped tomorrow, your file would open in a dozen other tools, including the native Mac apps discussed in the Mac guide. No other candidate can say that about its vault.
The costs are the known ones: sync is your arrangement, sharing is file-based, and there is no official mobile app. Those are architecture costs, not license costs, and they are exactly what some readers are buying. For the requirement "no server exists that could be breached, subpoenaed, or repriced," KeePassXC is not one option among several; it is the only entry in this article that fully satisfies it.
Passbolt: AGPL team sharing
Passbolt is the open-source answer shaped for teams: AGPLv3, built on OpenPGP, designed for sharing rather than adapted to it. Its Community Edition is free self-hosted with unlimited users, and Pro ($4.90 per user per month billed annually, 10-user minimum) adds SSO, LDAP, escrow recovery, and activity logs. For the open-source business case it is the most complete package here, and the business guide evaluates it on admin criteria. Its license story needs no asterisk, which in this article is high praise.
Proton Pass: open clients, closed server, honest labeling
Proton Pass publishes its apps as open source and runs a closed server, and says so. That combination buys real but partial assurance: the code that touches your plaintext on your device can be inspected, while the service that stores and syncs ciphertext cannot be self-hosted or independently operated. For many users that is the right trade (the free plan covers unlimited logins and devices with 10 aliases; Pass Plus is $2.99 per month billed yearly), especially combined with Proton's audits and Swiss jurisdiction. For readers whose definition of open source is "I could run the whole system," Proton Pass does not qualify, and this guide will not stretch the term to include it. The license audit checklist below includes the server question explicitly, because it is the one marketing most often blurs.
Vaultwarden: the unofficial asterisk
Vaultwarden, the lightweight Bitwarden-compatible server written in Rust under AGPL-3.0, is open source with a different caveat: it is not the vendor's code. The audited, reviewed software in a Vaultwarden deployment is Bitwarden's official clients; the server they talk to is a community reimplementation, unaudited to the same standard. That does not make it bad (it is widely used and sensibly built), but an honest license table must separate "open" from "official," because the security argument for open source is inspection, and inspection has actually happened to different degrees for different components. The self-hosted guide weighs Vaultwarden against the official server operationally.
Interactive tool
Open-Source License Audit
Check off each step as you finish it. Your progress stays on this page.
0 of 7 complete
0% done
The verdict
For most people who want open source without a hobby attached: Bitwarden, accepting the split-license reading as a known complexity. For the purest license and the strongest continuity: KeePassXC, accepting the file-based life. For teams: Passbolt, AGPL throughout, with Pro buying the admin layer. For privacy features with open clients: Proton Pass, understanding the server is closed. And for everyone: verify the license files in the repositories on the day you decide, because this category's licenses have changed before (the Bitwarden client debate, and NocoDB's 2026 move in the adjacent database category) and a license claim, like a price, carries a check date.
Related guides
This decision rarely stands alone. The guides below cover the closest questions on the chart, each with prices checked on the vendor pages.
What is the best open-source alternative to 1Password?
Bitwarden for most users: open-source clients and server, a free plan with no device or password limits, and Premium at $1.65 per month billed yearly. KeePassXC is the better answer when the requirement is a fully GPL stack with no server at all, and Passbolt is the better answer for teams that want AGPL licensing with business admin features. The component table in this article exists because "best" depends on which part (client, server, format) you most need to be open.
Is Bitwarden fully open source?
Its code is public and open source, but under two licenses: AGPL for much of it and the more restrictive Bitwarden License for certain components, with the split having changed over time and drawn public debate. You can inspect the code and self-host the server. If your requirement is a single copyleft license across the whole stack, KeePassXC (GPLv3) and Passbolt (AGPLv3) are the cleaner answers. Check the current license files in the repositories for the components you depend on.
Is Proton Pass open source?
Its client apps are open source; its server is not, and there is no self-hosting option. That gives you inspectability of the code that handles your passwords on your device, which is meaningful, but not the ability to run the system yourself. Proton is transparent about this split. Whether it counts as an "open-source password manager" depends on whether your definition requires the server, and this guide's position is that the distinction should be stated rather than argued away.
What does the KDBX format buy me?
Continuity and choice. KDBX is an open standard vault format read by many independent applications (KeePassXC, Strongbox, Secrets, and others) on every platform. Your vault is a file those apps compete to open, so no single project's fate, pricing, or licensing change can strand your passwords. It is the strongest form of the open-source promise available in this category, stronger than any single app's license, because it survives all of them.
Is Vaultwarden safe to use?
It is widely used, open source under AGPL-3.0, and works with Bitwarden's official apps. The honest caveat is that it is an unofficial reimplementation of the server: the heavily reviewed code in the setup is the clients, not this server, and there is no vendor support behind it. For an individual or family with good backup and TLS hygiene, the risk profile is reasonable and commonly accepted. For a business, the official Bitwarden server or Passbolt is the defensible choice, as the business guide sets out.
Does open source actually make a password manager more secure?
It makes it more inspectable, which is a precondition for trust rather than a guarantee of it. Open code can be audited, and in Bitwarden's and KeePassXC's cases has been, but an unexamined open codebase is not safer than an audited closed one. The concrete benefits for a user are continuity (the software survives its vendor), verifiability (claims about encryption can be checked), and exit (self-hosting and open formats). Weigh those, rather than treating the label as a security rating.
Photo credits: Bibek ghosh (Pexels). Photos are served from this site; follow the credit to the library page for the original.