Self-Hosted Password Manager: Run Your Own Node
Self hosting a password manager used to mean one thing: running a sync server at home and inheriting its whole job list. VaultKeepR approaches the problem differently. The vault is encrypted on your device, so the only question self hosting answers is where the ciphertext lives. This page walks through the three modes, what each one costs you in operations, and how they compare to the Vaultwarden route.
What Self Hosting Actually Means Here
The encryption happens before anything is stored. Your master secret goes through Argon2id (time cost 3, memory cost 64 MiB, parallelism 4) on your device, and the vault is sealed with XChaCha20-Poly1305. No mode, hosted or self hosted, gives any storage layer the ability to read your entries. Self hosting only changes who holds the encrypted blob and who keeps it available.
That reframing matters because the traditional self hosting pitch trades your data privacy for a new operational burden. Here the privacy does not depend on the trade. You pick the mode based on convenience and uptime preferences, not on trust.
Mode 1: Managed Sync, Encrypted Storage
The default mode keeps a managed encrypted copy of your vault in the cloud and a managed pointer at /api/vault-cid that tells your devices where to find the latest version. Be precise about what that means: the service exists, and it cannot read the vault. It stores ciphertext and a content address, nothing else.
Zero configuration, cross-device sync out of the box, and the same encryption as every other mode. The trade is availability: if the managed storage is unreachable, devices fall back to their local encrypted copy until it returns.
- No setup: sync works on first launch.
- Vault storage and pointer are managed, encryption keys are not.
- Every device keeps a local encrypted copy for offline reading.
Mode 2: Your Own Node
For full ownership you run vaultkeepr-node (v0.1.0), an open source IPFS node published on GitHub releases with sha512 checksums for each build. You self host both the storage and the pointer: the node pins your encrypted vault and announces its IPNS name.
Configuration is a single vaultkeepr-node.json file:
rpcUrl: the RPC endpoint the node exposes. Bind it to your LAN and sync from any device at home.token: the RPC token. It is mandatory, the node refuses unauthenticated RPC calls.gatewayUrl: a public IPFS gateway used as fallback when direct peers are unreachable.
Cross-device sync works peer to peer: publish the vault from one device to your node, resolve it from another by IPNS name, and use the public gateway as a fallback path. You handle the operational basics of a long running process, but there is no database server, no TLS certificate, and no multi user surface to patch: the node speaks IPFS and stores encrypted blobs.
Mode 3: Encrypted Export, No Infrastructure
The most standalone option skips infrastructure entirely. Export your vault to a .vkvault file, an encrypted archive sealed with the same XChaCha20-Poly1305 parameters, and move it yourself: USB key, your own cloud drive, a disk backup. Import it on any device with your master secret and the vault is intact.
This is also your exit path. The format is documented, so no mode holds your data hostage, and exports double as offline backups you control end to end.
Managed sync
Cloud encrypted storage plus a managed pointer. Nothing to operate, nothing to back up. The service cannot read the vault.
Your own node
vaultkeepr-node pins the ciphertext and announces it over IPNS. LAN sync, RPC token required, public gateway fallback.
Encrypted export
A .vkvault file moved by hand. No infrastructure, no accounts, just an encrypted archive and your master secret.
The Vaultwarden Comparison, Honestly
Vaultwarden is a competent lightweight reimplementation of the Bitwarden server, and running it is a real option. But look at the job description. You commit to a Docker container, a database on persistent storage, TLS certificates in front of it, backups of that database, and version upgrades when they ship. It is a server in the full sense, because the Bitwarden architecture needs one.
- Vaultwarden: the sync server is the product. Uptime, backups and patching are yours.
- VaultKeepR: the vault is an encrypted file. Managed sync needs no setup, the node is a single binary with a token, and the export needs nothing at all.
Which Mode Should You Pick
Start with managed sync: it is the default because it fits most people and the service cannot read the vault. Move to your own node when you want the ciphertext on hardware you control, or when you want sync that keeps working without any vendor. Keep .vkvault exports as a backup habit regardless of mode, because a file you can restore anywhere is the cheapest insurance there is.
Step by step instructions for the node live in the self hosting guide on the documentation site, and the code is at github.com/VaultKeepR/vaultkeepr-node. You can download VaultKeepR and try any mode without committing, or read the comparisons page first.