Skip to content

Self-Hosted Password Manager Without a Server

2026-11-11 · 5 min read · self-hosting, password-manager, privacy, ipfs

VaultKeepR cover: A self-hosted password manager without running a server

A self-hosted password manager without a server to run exists, but almost none of the search results describe it. The classic answers, Vaultwarden and friends, are excellent software that still hand you a server to operate: a VPS or a home machine, Docker, a hostname, a TLS certificate, updates and backups. There is another family, decentralized storage, where your encrypted vault is published to a network and no one operates a server, not even you.

What self-hosted actually means for a vault

Self-hosted means the storage and the authentication move from a vendor's infrastructure to infrastructure you control. It does not require you to run a server, even if most guides stop at that assumption. For a password vault, the real questions are three:

  • Where does the encrypted vault file live?
  • Who serves it to your phone when you need a password?
  • Who patches, backs up and renews the TLS certificate?

If the answer to all three is "me", you are on the classic self-hosting route. If the answer is "the network, by content identifier", you are in the decentralized family. Both keep your vault out of a vendor's cloud. They differ in who carries the operational load.

Why people want self-hosting

The motivations are consistent across every forum thread on the topic:

  • Control. The vault sits where you decided, not where a vendor chose. No silent policy change can move it.
  • Confidentiality. Fewer parties see your metadata, your login times, your account email. Some managers expose more of it than people expect.
  • Cost. A VPS for a small family vault costs a few euros per month, sometimes less than a commercial subscription.

These are good reasons. The catch is that the first two buy you a third one nobody asked for: operations. A self-hosted server that falls behind on patches or loses its disk is a worse outcome than a vendor you merely distrust. Backups of an encrypted vault are simple, a copy of a file, but they only work if you actually make them.

The four families of self-hosted password managers

1. Vaultwarden: the community server

Vaultwarden is an unofficial server implementing the Bitwarden client API in Rust, compatible with official Bitwarden clients. It is lighter than the official Bitwarden self-host deployment, which makes it the default recommendation on every self-hosting forum. The price is the full server checklist: a host, Docker or a binary, HTTPS (the project requires it for the web vault, so plan a reverse proxy), updates and backups. You can read the full comparison in Bitwarden vs Vaultwarden.

2. Bitwarden_RS: a name, not a project

Search results still mention Bitwarden_RS. It is not a separate project anymore: it is the former name of Vaultwarden, renamed at the v1.21.0 release, as the repository explains. If a guide recommends "Bitwarden_RS" in 2026, it is a stale guide. Follow it to the same Vaultwarden repo.

3. pass: the unix approach

pass stores each secret as an encrypted file in a plain directory, encrypted with GPG, and expects you to manage the tree yourself. There is no server component at all, which is the point: synchronization happens through git or however you move files. It is loved by people who already live in a terminal and already have opinions about git remotes. If you do not, the setup and the habit of manually reconciling devices become the product.

4. Decentralized: the storage is the network

VaultKeepR belongs to a newer family. Your vault is encrypted locally with XChaCha20-Poly1305, derived from your master password with Argon2id, then published to IPFS, a content-addressed network. Your devices fetch it by its content identifier, so there is no hostname to renew and no vendor cloud to trust. The difference with Vaultwarden is structural: nobody operates a server, not even you. The trade-off is different: you depend on the IPFS network being reachable, and you want your own node for reliability.

You can read how the architecture works in what zero-knowledge encryption means.

How to choose between them

Use the same criteria for any family:

Criterion Vaultwarden pass VaultKeepR
You operate a server Yes No, but you manage files No
Sync across devices Built in Manual (git or files) Built in, three modes
Clients Official Bitwarden CLI and community apps Chrome extension, iOS, Android
Recovery if you lose the master password None, restore a backup None, restore GPG keys Shamir 3-of-5
What you must maintain Host, TLS, updates, backups GPG keys, file sync Your node, if you run one

Pick Vaultwarden if you already run services at home, enjoy it, and want Bitwarden clients. Pick pass if you want plain files and you already trust your git workflow. Pick a decentralized manager if you want the vault off vendor clouds and off your own server. More context on that route is on the self-hosted overview.

Cross-device sync with your own IPFS node

This is the part that surprises people coming from server-based self-hosting: your storage can be yours without being a server you babysit.

With VaultKeepR, the vaultkeepr-node project (v0.1.0) is a small IPFS node you run on a machine you own, a home server or a VPS. You configure it with a vaultkeepr-node.json file: rpcUrl, token, gatewayUrl. It publishes your encrypted vault with publishToNode, unpins old versions with unpinFromNode, and your other devices resolve the current version via IPNS, the mutable naming layer of IPFS. If the node is down or you are away, a public gateway resolves the same content as a fallback. The RPC token is mandatory, and you can bind the node to your LAN.

What you do not get, and should not expect: a magic network that stores your data for free. IPFS pins need a pinning service or your own node to persist. The trade is explicit: your node stores your encrypted vault, the network routes it.

Two other sync modes exist and cost nothing extra: a managed encrypted sync (VaultKeepR's cloud stores only the ciphertext and the managed pointer) and a manual encrypted file export in .vkvault format, moved between devices by hand, USB, or any storage you like. All three are compared in access your vault from another device.

Migrating without leaving plaintext behind

Whatever you come from, the path is the same:

  1. Export your current manager's data as CSV (or its native encrypted export).
  2. Import it into the new manager.
  3. Verify on a second device that the entries match, especially TOTP seeds and attached files.
  4. Delete the unencrypted export. This step is the migration. A CSV of all your passwords left in a downloads folder undoes every security decision you just made.

The honest summary

Vaultwarden is excellent, and if you enjoy operating a server it will serve you well. pass is honest and minimal, at the price of doing everything yourself. VaultKeepR's position is narrower: it is for people who want the vault under their own control without a server under their own care. The cryptographic core is public under MIT, so you do not have to take the architecture on faith.

Download VaultKeepR or read more about the zero-knowledge model first.

FAQ

Can you self-host a password manager without running a server?
Yes. Beyond the classic route of running a Bitwarden-compatible server like Vaultwarden in Docker, there are two other families: local file managers like pass, where you handle synchronization yourself, and decentralized managers like VaultKeepR, where your encrypted vault is published to IPFS and resolved from your other devices via IPNS. Nobody operates a server, not even you.

Direct link to this question

Is Vaultwarden still maintained?
Yes. Vaultwarden is an active community project, an unofficial server implementing the Bitwarden client API in Rust. Its old name was Bitwarden_RS, renamed with the v1.21.0 release to avoid confusion with the official Bitwarden server. What it requires from you is real operations work: a host, HTTPS, updates and backups.

Direct link to this question

What is the difference between self-hosting and decentralized storage?
Self-hosting moves the server from a vendor to your hardware, and you keep the operations burden. Decentralized storage removes the single server entirely: your encrypted vault is published to IPFS, a content-addressed network, and your devices find it by its content identifier. There is no hostname, no TLS certificate and no backup script of your own to maintain.

Direct link to this question

How do I sync my vault between devices without a server?
With VaultKeepR you publish your encrypted vault to your own IPFS node, then resolve it from your other devices through IPNS, the naming layer of IPFS. If your node is unreachable, a public gateway serves the same content by identifier. A managed encrypted sync and a manual encrypted file export are also available.

Direct link to this question

Is a self-hosted password manager free?
The software usually is: Vaultwarden and pass are free. What you pay for is the VPS or the machine that runs them, plus your time for updates and backups. VaultKeepR's free tier includes the vault, sync, passkeys, autofill and breach monitoring, with no server to operate.

Direct link to this question

How do I migrate my passwords to a self-hosted manager?
Export your data as CSV from your current manager, import it into the new one, verify that the entries match on a second device, then delete the unencrypted export immediately. The plaintext CSV is the most dangerous file in the whole migration, so treat deleting it as part of the migration, not an optional cleanup.

Direct link to this question

Keep reading