Run your own IPFS node (free, no account)
VaultKeepR syncs your vault through IPFS, the decentralized storage network. Publishing goes through the managed VaultKeepR cloud by default. You can also run your own IPFS node with vaultkeepr-node, a one-script Kubo installer.
The node runs on your own machine. Self-hosting is a standard VaultKeepR feature: free, without an account, and not part of Premium. Your vault stays encrypted end to end (XChaCha20-Poly1305, Argon2id); the node only ever receives and serves the encrypted JSON.
Requirements
Section titled “Requirements”- Linux, macOS, or Windows (PowerShell)
- about 50 MB for the Kubo binary, a few GB free for the node’s datastore
- the node running when you sync (publish and first read)
Install
Section titled “Install”Linux / macOS:
curl -fsSL https://github.com/VaultKeepR/vaultkeepr-node/releases/latest/download/install.sh -o install.shbash install.shWindows (PowerShell):
Invoke-WebRequest https://github.com/VaultKeepR/vaultkeepr-node/releases/latest/download/install.ps1 -OutFile install.ps1.\install.ps1The script downloads Kubo, the reference IPFS implementation, verifies the SHA-512 checksum, and configures a private node: the RPC API on 127.0.0.1:5001 and the gateway on 127.0.0.1:8080, both loopback only; an auth token that every RPC call must carry; and AllowedPaths restricted to /api/v0.
Then start it:
bash start.sh # Linux / macOS.\start.ps1 # WindowsThe connection file
Section titled “The connection file”The installer writes vaultkeepr-node.json next to the scripts, with the RPC URL, the token, and the gateway URL. Anyone who has the token can publish to your node, so keep the file to yourself.
To sync from another machine on your LAN, install with bash install.sh --lan so the RPC and the gateway listen on your local network, then copy vaultkeepr-node.json to that device.
Connect an app
Section titled “Connect an app”- Open Settings, then Advanced (extension), or Settings, then Advanced settings (iOS, Android).
- Under Personal IPFS node, press Paste with
vaultkeepr-node.jsonin your clipboard. - Press Test: the app checks that the node answers with your token.
- Press Save. The card confirms the personal node is active.
The first personal sync generates a dedicated IPNS key on your node, vaultkeepr-vault, and publishes your vault’s encrypted JSON to it. Later syncs republish the same name with the new ciphertext, so every device follows the same address.
Leave the fields empty and save to go back to the managed cloud at any time. Both modes carry the same encrypted JSON.
How sync behaves
Section titled “How sync behaves”Publishing goes to your node. The upload takes about 0.2 s, then the IPNS publish takes 30 to 60 s the first time, and a few seconds after that. Reads resolve your IPNS name through your node first, and fall back to public gateways when the node is off. If a publish fails, your local vault is untouched.
A second device uses the same vaultkeepr-node.json: paste it there, sync, and it picks up the latest version.
What the node sees
Section titled “What the node sees”The encrypted vault JSON, its CIDs, and your IPNS records. The node never receives your master password or your encryption key, and site names and logins stay inside the ciphertext. You can check all of this yourself: the bundle scripts are short and readable, and Kubo is open source.
Uninstall
Section titled “Uninstall”bash uninstall.sh # Linux / macOS.\uninstall.ps1 # WindowsThis removes the binary, the config, and the datastore, including the IPNS key. Your vault stays on your devices, and re-exports and the managed cloud keep working as before.