Skip to main content

Command Palette

Search for a command to run...

VaultKeepR Free and optional Premium: what you pay for

The Free vault needs no subscription. Premium recovery and other paid features are optional; crypto Lifetime is a separate offer.

Updated
•3 min read•View as Markdown
VaultKeepR Free and optional Premium: what you pay for

A free vault, with optional paid features

VaultKeepR's Free plan provides the core password vault without an email address. It does not have a 100-password quota. You can use Free without subscribing; Premium is optional.

A subscription is a payment model, not evidence that a provider can decrypt your vault or erase your passwords when you cancel. Compare the published downgrade and export policies of each service rather than assuming they all behave the same way.

What Free and Premium mean

Free covers the basic encrypted vault and the public extension and mobile clients. Shamir recovery is a Premium feature, not a free recovery service.

Premium is offered at €2.49 per month or €17.99 per year. The €299 crypto Lifetime option is a separate one-time offer. It should not be described as the only way to get Premium. Check pricing before buying, including the features and limits of the selected plan.

The storage still has operating costs

The client encrypts vault snapshots before upload. Storage can involve IPFS gateways, pinning services, hosted APIs and S3-compatible backends. These services handle ciphertext, while timing, size, CIDs and on-chain activity may remain observable. IPFS content addressing does not guarantee persistence: retain an independent encrypted backup and test retrieval. The sync documentation and threat model describe those dependencies.

Using IPFS does not make hosting, pinning or support free. It also does not guarantee access if a service disappears. Keep an encrypted export that you can restore independently.

Create the vault in a supported client

The public clients are the Chrome and Firefox extensions and the iOS and Android apps, available from Download. Creating a vault does not require an email address or an external wallet such as MetaMask. The passkey and smart-account flow is described in the passkey documentation; available unlock methods depend on the client and authenticator.

Use the client setup guide for your platform. You do not sign up for the vault with an email address, and you do not need to connect MetaMask to start.

Plan recovery separately

VaultKeepR Premium uses Shamir 3-of-5 recovery for the vault encryption key. The five configured channels are the device, remote storage, a trusted contact or QR handoff, a smart contract, and the API. Any three valid fragments can reconstruct the key; losing too many fragments or the recovery identifier can prevent recovery. See the current SDK defaults, channel distribution, and recovery guide. This recovers a vault key, not a hardware passkey or each seed phrase stored in the vault.

Configure and test recovery with a non-sensitive vault before relying on it. If you stay on Free, maintain a backup and protect the credentials required to restore it.

Moving from another manager

Export only on a trusted device. An unencrypted CSV exposes its contents to anyone who can read the file. Import into a supported VaultKeepR client, check representative entries and attachments, and test access on another device before removing the export or closing the old account.

The migration documentation contains the maintained procedure. Migration time and supported fields depend on the source format and client.

Start with the plan you need

Download VaultKeepR to use the Free vault. Choose a paid plan only if its additional features fit your needs. The price of a plan and the confidentiality of a vault are separate questions.

More from this blog

V

VaultKeepR - Password Manager Zero Knowledge - No Account - No Email

86 posts

Building a password manager with no email signup, no account, and zero-knowledge encryption. The engineering behind VaultKeepR, open source: Argon2id and XChaCha20-Poly1305 in TypeScript, Solidity contracts on Base, wallet-based identity, CRDT sync, IPFS storage, fragmented recovery, digital legacy. Working code, threat models, Foundry tests, and the trade-offs we argue about. MIT, reuse it.