Home / Software Alternatives

Bitwarden Alternatives (Self-Hosted): The Server Is the Product

Modern server rack with blue lighting in a secure data center environment.

Photo: panumas nikhomkhai / Pexels

Two bills: the license and the operation

Every self-hosted comparison lists features and stops before the part that decides whether you will still be self-hosting in a year. Running a vault server means HTTPS certificates, updates, backups you have actually restored once, and a plan for the evening the container is down and nobody can log into anything. The license bill is the easy half: Vaultwarden and Passbolt Community are $0, the official Bitwarden server mixes free and paid tiers, and a managed Vaultwarden host charges about EUR 9 a month flat. Against Bitwarden Teams at $4 per user per month billed annually, that flat managed price breaks even at roughly three seats, and self-hosting on a $5 VPS breaks even sooner. The operations bill is where the candidates separate, so this guide grades footprint, update burden, and failure behavior before features.

CandidateFootprintThe operations catchLicense bill
VaultwardenOne small container, runs on a Raspberry PiUnofficial server; you are the support desk$0 (AGPL-3.0)
Official Bitwarden serverMulti-container stack, real RAM appetiteSome features gated behind paid tiersFree and paid tiers
Passbolt CommunityLAMP-style stack, moderateTeam-shaped setup and maintenance$0 (AGPLv3)
KeePassXCNo server at allSync and sharing become file discipline$0 (GPLv3)
HashiCorp Vault / OpenBaoSerious infrastructureSolves machine secrets, not human logins$0 open core

Vaultwarden: the default self-hosted answer

Vaultwarden exists because the official server is heavy and this one is not. It is a community reimplementation of Bitwarden's server API in Rust, packaged as a single small container that idles happily on a Raspberry Pi class device, and every official Bitwarden client (browser extension, mobile, desktop) connects to it exactly as it connects to Bitwarden's cloud. Most premium-style features, including TOTP generation and organization sharing, work without a license fee, because the server simply does not gate them. The honest caveats are structural. It is unofficial: the audited code in this arrangement is Bitwarden's clients, not this server, and its maintainer pool is small. Updates, TLS, backups, and disabling open registration after your users exist are your jobs. For a household or a solo operator with a home server already running, Vaultwarden is the verdict, and the managed option (about EUR 9 a month flat from specialist hosts) exists for people who want the shape without the sysadmin shifts. The license audit behind it is in our open source comparison.

Interactive tool

Comparison Builder

Pick two or three products and see them side by side on the numbers that decide the purchase.

MeasureVaultwardenBitwardenPassbolt
Starting paid priceFree$1.65 per user/mo, billed annually$4.9 per user/mo, billed annually
Free optionFree plan: the software is free and open source under AGPL-3.0; the only cost is the server it runs onFree plan: always free, unlimited passwords on unlimited devicesFree plan: the self-hosted Community Edition is free forever with unlimited users under AGPLv3
PlansVaultwarden (Self-Hosted): freeFree: free · Premium: $1.65/user/mo annual · Families: $3.99/user/mo annual · Teams: $4/user/mo annual · Enterprise: not publishedCommunity Edition (Self-Hosted): free · Pro: $4.9/user/mo annual · Enterprise: not published
PlatformsLinux, Windows, macOSWebWeb, Windows, iOS, Android, Linux
Best forindividuals and families self-hosting a vault, home server owners, Bitwarden users who want their sync on their own hardwarebudget users, privacy-focused teams, self-hosterstechnical teams that self-host, companies that need a team vault under their own control, open-source password management for business
StrengthsTiny footprint: one container instead of the official server stack; Works with the official Bitwarden mobile, desktop, and browser clients; Most premium-style features are enabled without a license feeFree tier has no device or password limits; Open source and auditable; Self-hosting availableBuilt 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 forUnofficial and unaudited as a server: the audited code is Bitwarden's clients, not this server; No vendor support; updates, TLS, and backups are yours; A password server you run badly is worse than a vendor cloud run wellInterface is plainer than paid rivals; The built-in authenticator and file attachments sit on Premium, not FreeSelf-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: Vaultwarden at Free per month flat. Real free plan: Vaultwarden, Bitwarden, 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.

The official server and Passbolt: the two legitimate stacks

The official Bitwarden server is the choice when unofficial is a word your organization cannot accept. You gain vendor support, the audited server codebase, and a supported upgrade path; you pay with a multi-container deployment that wants real resources, and with the discovery that some capabilities sit behind paid self-hosted tiers, so the license bill is not automatically $0. Passbolt Community is the team-shaped alternative: AGPLv3, free with unlimited users, OpenPGP-based sharing designed for groups rather than households, and a Pro edition ($4.90 per user per month billed annually, 10-user minimum) that adds SSO and provisioning when the team outgrows the free core. Its operations profile sits between the two Bitwardens: a conventional web stack, more setup than one container, less than the official fleet. Choose the official server for supportability, Passbolt for team sharing semantics, Vaultwarden for footprint.

KeePassXC: delete the server

The most reliable self-hosted vault is the one with no server in it. KeePassXC stores your passwords in one encrypted KDBX file, and self-hosting becomes a file sync decision: put the file in a folder you already sync (Nextcloud, Syncthing, a plain SFTP cron) and every device opens its own copy. There is nothing to patch at 2 a.m., no certificate to expire, and no public endpoint for anyone to attack, which is a security property no server can claim. The costs are collaboration and convenience: two people editing the vault simultaneously creates merge work, sharing means sharing the file and its password, and browser autofill depends on the KeePass family integrations rather than a live service. For a solo operator or a couple, this is frequently the correct answer to a query that assumed a server, and it is $0 forever. Our free tier audit grades its feature completeness against the hosted free plans.

Machine secrets are a different job

A recurring reader of this query is not moving family logins at all; they are storing API keys, certificates, and service tokens, and a password manager is the wrong shape for that work. HashiCorp Vault and its open fork OpenBao exist for machine secrets: dynamic credentials that expire, access policies per service, and audit logs of every read. They are serious infrastructure with serious operational weight, and running one to store your Netflix password is a category error in the other direction. The split is simple. Humans with browsers and phones: Vaultwarden, the official server, Passbolt, or KeePassXC. Services with tokens and TTLs: Vault or OpenBao, budgeted as infrastructure. Articles that rank these five as one list are selling confusion, so this guide refuses to.

The verdict

Vaultwarden ($0 plus a small server) is the default self-hosted Bitwarden alternative for households and small groups. The official Bitwarden server is the pick when vendor support is a requirement. Passbolt Community ($0, unlimited users) is the team verdict. KeePassXC ($0, no server) is the answer for solo operators who can trade live sync for zero maintenance. The checklist below is the readiness test: if you cannot tick the backup and update lines honestly, the hosted plans in our general Bitwarden alternatives guide are the safer recommendation.

Interactive tool

Self-Hosting Readiness Checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 6 complete

0% done

Related guides

The shortlist does not end here. These related guides cover the sibling tools, matchups, and pricing questions closest to this one.

Frequently asked questions

How much does it cost to self-host Vaultwarden?

The software is free (AGPL-3.0). The running cost is the smallest server you already trust: a Raspberry Pi at home costs electricity, a small VPS typically costs a few dollars a month, and managed Vaultwarden hosting from specialist providers runs about EUR 9 a month flat. Against Bitwarden Teams at $4 per user per month billed annually, the managed option breaks even at roughly three seats and the VPS option at one or two, before you price your own maintenance time, which is the honest line item most comparisons omit.

Is Vaultwarden safe even though it is unofficial?

The arrangement's security rests on three legs: Bitwarden's official clients (the audited part of the system) do the cryptography on your device, Vaultwarden's server code is open (AGPL-3.0) and inspectable, and your operational hygiene (HTTPS, updates, backups, registration closed) decides the rest. Its residual risks are a smaller maintainer pool and no vendor security response team. For a household that is a reasonable trade; for a regulated company it is the reason the official server exists. Neither answer is a slogan; it depends on who is accountable when something breaks.

What breaks if my self-hosted vault goes down?

Your clients keep working offline with their cached vaults, so a dead server is an inconvenience (no sync, no new logins shared, no Send) rather than a lockout, as long as every user stays logged in on at least one device. The dangerous failure is data loss without backups, which is why the readiness checklist in this article puts a tested restore before migration. Export an encrypted backup of the vault on a schedule and keep one copy off the server itself.

Should a team pick Passbolt or self-hosted Bitwarden?

Pick Passbolt Community when the team's core activity is sharing credentials among staff: its OpenPGP sharing model, unlimited free users, and team-first design fit that job, and Pro ($4.90 per user billed annually) adds SSO when needed. Pick self-hosted Bitwarden (official or Vaultwarden) when the team is really a collection of individuals who each need a full personal vault with some sharing attached, or when the official Bitwarden clients are a hard requirement. The price difference is smaller than the shape difference.

Can KeePassXC really replace a server for a small team?

For two or three technical people, yes: one KDBX file in a synced folder, a shared master password, and the discipline to let the sync finish before editing. Past that size, simultaneous edits, per-person revocation, and audit needs outgrow the file model, and a real server (Passbolt or Bitwarden) earns its keep. The failure mode to avoid is pretending the file model scales because it worked for two people in the first month.

Photo credits: panumas nikhomkhai (Pexels). Photos are served from this site; follow the credit to the library page for the original.