Vaultwarden vs 1Password for a Family: Self-Hosted Savings or a Service Nobody Has to Maintain

Marisol Vega

Marisol Vega

November 20, 2026

Vaultwarden vs 1Password for a Family: Self-Hosted Savings or a Service Nobody Has to Maintain

You are trying to get a whole household onto one password manager. Someone in the family already runs a small server, and Vaultwarden looks like a way to give everyone shared vaults without another subscription. On the other side sits 1Password Families, which costs money every year but asks nothing of you beyond paying the bill. The real question is not which app has more features. It is whether you want to be the person who keeps the family’s passwords online, backed up and patched for the next five years.

Two very different products that solve the same family problem

1Password Families is a hosted subscription. 1Password runs the servers, ships the apps for Windows, macOS, Linux, iOS, Android and the browser extensions, and handles account recovery tools for the family organizer. Its product page says the plan “includes 5 users,” with unlimited shared vaults and admin controls for managing who sees what.

Vaultwarden is not a password manager app at all. Its GitHub README describes it as “an alternative server implementation of the Bitwarden Client API, written in Rust and compatible with official Bitwarden clients.” The project states plainly that it is “not associated with Bitwarden or Bitwarden, Inc.” Your family installs the normal Bitwarden apps and browser extensions, then points them at your server’s address instead of Bitwarden’s cloud. Vaultwarden is licensed under AGPL-3.0 and is usually run as a single Docker container with an SQLite database.

With 1Password you are buying a finished service. With Vaultwarden you combine free client apps from one organization with a free server from a separate volunteer project, and you are the operator in the middle.

What 1Password Families costs in 2026, and what Vaultwarden really costs

1Password raised its consumer prices for renewals on or after March 27, 2026, as reported by MacRumors and 9to5Google. The Families plan now lists at $5.99 per month billed yearly, which works out to $71.88 a year, up from $59.88. 1Password’s own page currently shows an introductory discount for new customers buying directly with annual billing, bringing the first year down to $4.49 a month. Five people are included. For larger households, 1Password staff on the company’s community forum have said additional family members cost $1 per person per month, though the official pricing page does not spell that out, so confirm it before you plan around a family of seven.

Vaultwarden’s software is free, and so are the official Bitwarden clients. Features that Bitwarden’s own cloud reserves for paid plans, such as organizations for sharing, collections, groups, emergency access and hardware-key two-factor authentication, are listed in Vaultwarden’s README as supported. There is no per-user fee and no member cap beyond what your hardware can handle.

The money you save is not the whole bill, though. A Vaultwarden instance needs:

  • A machine that is on all the time, whether a mini PC, a NAS that runs containers or a small VPS.
  • A domain or other hostname with a valid TLS certificate. The README notes the web vault “requires the use of HTTPS and a secure context for the Web Crypto API,” so plain HTTP on a LAN address is not an option.
  • A way for phones to reach it away from home: a reverse proxy exposed to the internet, or a VPN such as WireGuard or a mesh overlay that every family device stays connected to.
  • Backups that are tested and stored somewhere other than the server itself.
  • Your time for updates, which matters because the project regularly publishes security fixes; the 1.36.0 release notes, for example, list advisories related to its SSO login.

If you already run a homelab with a reverse proxy, monitoring and off-site backups, adding Vaultwarden costs very little. If you would build all of that just for passwords, $72 a year looks fair.

Four phones and cups of tea on a family table

How the security models differ

Both products encrypt vault data on the device before it is sent to a server, so the server stores ciphertext rather than readable passwords. The difference is in what protects that ciphertext if the server is compromised, and who is responsible for the server.

1Password’s account password plus Secret Key

1Password combines your account password with a Secret Key generated on your device when the account is created. According to 1Password’s support documentation, the Secret Key “works with your 1Password account password to encrypt and protect your data,” and the company keeps no copy: “We don’t have a copy of your Secret Key or any way to recover or reset it for you.” The key is stored on devices you have signed in on and printed in your Emergency Kit PDF. Because an attacker who stole 1Password’s server data would also need each user’s Secret Key, a weak family member’s password is far less exposed to offline guessing than it would be with a password alone.

The trade-off is one more thing to keep safe. For families, the practical safety net is the organizer: 1Password’s Families page says administrators can help other members recover their accounts using admin tools on 1Password.com.

Vaultwarden’s master password and your server hardening

Bitwarden clients derive the encryption key from the master password using a key derivation function (PBKDF2 or Argon2id, selectable in account settings). There is no equivalent of a Secret Key, so if someone copies your Vaultwarden database, the strength of each family member’s master password is what stands between them and the vault. Encourage long passphrases and turn on two-factor authentication, which Vaultwarden supports through authenticator apps, email, FIDO2/WebAuthn security keys, YubiKey and Duo.

Everything around the encryption is your job: keeping the container updated, limiting exposure of the admin page, configuring the reverse proxy correctly and protecting the server’s disk and backups. Vaultwarden’s backup guide points out that config.json can contain sensitive values such as the admin token and should be encrypted before it is uploaded anywhere. Organizations and emergency access do give you a recovery path for family members, but only if you set them up before someone forgets a password.

Features side by side

Area 1Password Families Vaultwarden with Bitwarden clients
Price $5.99/month billed yearly ($71.88/year) after the March 2026 increase Free software; you pay for hardware, domain and time
People included 5, more for an extra fee No fixed limit
Who runs the server 1Password You
Key protection Account password plus Secret Key Master password with PBKDF2 or Argon2id
Family sharing Unlimited shared vaults with admin controls Organizations with collections, groups and member roles
Breach and weak-password alerts Watchtower No Watchtower equivalent built into the server
Passkeys Stored in the vault; Watchtower flags sites that support them Stored through Bitwarden clients since Vaultwarden 1.30.0
Travel protection Travel Mode No equivalent
Account recovery Family organizer can help members recover Emergency access and organization admin, if configured
Offline use Desktop and mobile apps keep a local copy; changes sync later Clients cache the vault read-only

A few of those rows need context. Watchtower, per 1Password’s Families page, flags known data breaches, weak and reused passwords, and websites you use that support passkeys. Travel Mode, which 1Password’s support site says is “included with every 1Password subscription,” removes every vault from your apps and browser extension except those you mark as safe for travel, and is switched on from Manage Account on 1Password.com. It matters if anyone in the family crosses borders where devices may be inspected.

On the Vaultwarden side, passkey storage arrived with the 1.30.0 release, whose notes list “Working passkeys storage” (#4025). Because the Bitwarden apps do the work, passkey behavior follows whatever the official clients support. Vaultwarden releases also continue to add SSO support, which matters more to small teams than to most families.

When the server goes down, or the service does

This is where the two options feel most different day to day. With 1Password, an outage is the company’s problem, and 1Password staff on its community forum have explained that the desktop and mobile apps cache your data locally, so you can still view items and edits sync once the connection returns. The browser extension is more dependent on a connection. With Vaultwarden, the outage is your problem, and it tends to happen at inconvenient times: a power cut at home, a full disk, an expired certificate, or a container that did not come back after an update.

The Bitwarden clients soften this. Bitwarden’s help documentation on using the apps offline says any unlocked client keeps working in read-only mode when it cannot reach the server, including a self-hosted one. You can unlock with your master password and copy credentials, but you cannot add or edit items, attachments or Sends until the connection returns. Bitwarden also says offline sessions expire after 30 days, or 90 days on mobile clients. A device that was fully logged out, rather than locked, needs the server to sign in again. We covered this behavior in detail in how long the Vaultwarden app keeps working on a phone if the server is off for a week.

So a short outage is usually survivable: everyone can still log in to their bank. The real risk is a long outage combined with lost data. If the disk dies and your last good backup is months old, every password changed since then is gone from the server. Vaultwarden’s wiki lists what must be backed up: db.sqlite3 and the attachments folder are required, while config.json and the rsa_key* files are recommended, because losing the keys logs every user out. The wiki recommends SQLite’s .backup command for a consistent copy of the database, and since version 1.32.1 Vaultwarden also has a built-in /vaultwarden backup command. For a broader view of what self-hosting costs you here, see Vaultwarden vs Bitwarden Cloud: what you actually lose when the box goes dark.

A brass padlock on an old wooden garden gate

Living with each one as a family

Usability is less about features than about who gets the support calls. 1Password’s apps are designed as one product, and onboarding a family member means sending an invite and helping them save the Emergency Kit. If a child forgets the account password, the organizer can step in through the admin tools.

Vaultwarden onboarding has one extra step that trips people up: before logging in, every family member has to change the server setting in the Bitwarden app from the default cloud to your self-hosted URL. Get that wrong and they create an account on Bitwarden’s servers by accident. After that, the experience is the normal Bitwarden experience, which many people find perfectly good, and shared items live in an organization with collections such as “Streaming,” “Utilities” or “Kids’ school accounts.”

Consider also who in the household could take over. If the person who runs the server is unavailable for weeks, can anyone else renew a domain, restart a container or restore a backup? With 1Password, the answer only requires knowing who pays the bill. If you are weighing other self-hosted approaches with even less server dependence, Vaultwarden vs KeePassXC with Syncthing for a family password vault covers the file-based alternative.

Moving between them without losing shared items

Neither choice locks you in permanently, but each direction has caveats that are easy to miss.

From 1Password to Vaultwarden

Bitwarden’s help page for importing from 1Password lists support for .1pux, .1pif and .csv files, with .1pux requiring 1Password 8.5 or later. In the 1Password 8 desktop app you select the items in a vault and choose File, then Export; Bitwarden notes that only 1Password 8 can export multiple vaults at once. Import the file through the web vault that Vaultwarden serves, under Tools. Bitwarden warns that importing does not check for duplicates, that some item types cannot be imported and must be re-created or attached manually, and that you should delete the export file afterward because it is unencrypted.

From Vaultwarden to 1Password

1Password’s guide for importing from Bitwarden requires an encrypted, password-protected .json export; it says unencrypted JSON and account-restricted exports are not supported, and that CSV files can only be imported in the 1Password apps. Two limitations matter for families. First, according to that guide, passkeys are not imported and items in shared collections are not imported, so you need to export each organization’s items separately and handle passkeys by registering new ones on each site. Second, the guide says the import fails if the Bitwarden account uses Argon2id, and you must switch the account’s key derivation to PBKDF2 before exporting. If you set up Vaultwarden accounts with Argon2id, plan for that step.

Whichever direction you go, do a test import into an empty vault first, compare item counts, and check a handful of entries with custom fields, TOTP codes and attachments before telling the family to switch.

Matching the choice to your household

Vaultwarden makes sense when most of these are true:

  • You already run an always-on server with HTTPS, remote access and automated, off-site backups that you have actually restored.
  • Your household has more than five people, or you also want to share credentials with extended family without paying per seat.
  • You are comfortable applying updates promptly when security releases appear.
  • Someone other than you could take over the server, or you have written down how.

1Password Families makes more sense when:

  • Nobody in the house wants to be on call for a password server.
  • You value the Secret Key design because some family members will not use strong master passwords.
  • Someone travels internationally and would use Travel Mode.
  • You want organizer-led account recovery without configuring it yourself.

A middle path exists too: Bitwarden’s own hosted service uses the same clients as Vaultwarden, so you can start there and move to your own server later with an export and import.

More articles for you