VaultKeepR vs KeePass
Compare KeePass and VaultKeepR by encryption, storage, access, and export format. The notes below distinguish supported settings and account models.
Swipe or scroll sideways to see all columns. With a keyboard, focus the table and use the left and right arrow keys.
| Comparison | VaultKeepR | KeePass |
|---|---|---|
| Encryption and key derivation | XChaCha20-Poly1305 + Argon2id | AES-256 / ChaCha20; AES-KDF / Argon2 (database-dependent) |
| Storage location | Local encrypted vault / IPFS sync | Local file (.kdbx) |
| Access & Auth | Password + Secret Key / compatible passkey | Master Password / Key File |
| Open-source license | Yes | Yes |
| Public implementation for review | Public SDK; not an external security audit | Yes |
| Pricing | Free local vault and IPFS sync; Premium extras | Free (Open-source) |
Why users choose KeePass
- • Local encrypted database
- • Configurable database encryption and KDF
- • Open-source code
What to check with KeePass
- • You manage database copies and synchronization
- • Client compatibility depends on the database format
- • Keep the password and any key file backed up separately
Encryption and key derivation
KeePass supports AES-KDF and, in KeePass 2.x, Argon2d and Argon2id. AES-256 and ChaCha20 protect supported database formats. Available combinations depend on the database version, client, and settings; KeePass should not be described as a PBKDF2-only service.
VaultKeepR encrypts vault contents with XChaCha20-Poly1305 and uses Argon2id for password-based key derivation. Argon2id raises the cost of offline guessing, but protection still depends on the unlocking secret, KDF parameters, and device security.
Vault copies and remote availability
KeePass stores an encrypted database as a local .kdbx file. You choose where the file lives and whether to copy or synchronize it through another service. KeePass does not require a vendor-hosted vault; protect the database copies and any separate key file.
VaultKeepR keeps an encrypted local vault and syncs an encrypted vault blob through IPFS. Shamir recovery fragments are separate from that blob. Remote access depends on gateways, continued pinning, and the configured storage services, including S3 backup. Keep a local copy or export that you can unlock.
Account and unlocking methods
A KeePass database can use a master password, a key file, or a combination supported by the client. An email account is not required to unlock a local database. Losing the required key material without a usable backup can leave the database inaccessible.
VaultKeepR does not require an email-based vault account. Unlock methods depend on the app and compatible hardware. Removing email registration does not prevent phishing, compromised-device access, or metadata linkage.
Recovery and independent backups
The local vault and IPFS sync are free. Shamir 3-of-5 fragmented recovery is part of Premium. Set it up before losing access; recovery requires the necessary fragments and recovery information.
If you lose the unlocking secrets without a usable recovery setup or another accessible vault copy, you can lose access to the vault. An email reset cannot recreate a lost encryption key. Test recovery and keep independent backups before relying on them.
Sources and scope
Facts checked on . Features depend on the client, format, KDF settings, and account model. Pricing can change by region, billing period, and promotion. USD prices are not converted to EUR here.
VaultKeepR references: Architecture, threat model, recovery, pricing.
Frequently asked questions
How can I transfer my passwords from KeePass?
Open and unlock the database in KeePass 2.x. Use File > Export and select KeePass XML (2.x). The encrypted .kdbx database is not the import file. Import the XML file in VaultKeepR and check the transferred entries. An unencrypted export exposes your secrets. Use a trusted device, verify the transferred entries, and delete the unencrypted export after verification.
Can I access my passwords offline?
You can read a local vault without an internet connection once it is available on that device and you can unlock it. Syncing or downloading a remote copy requires network access. A new device needs a vault copy and a supported unlocking method.
Is VaultKeepR really free?
The local vault and IPFS sync are free. Shamir 3-of-5 fragmented recovery is part of Premium. Set it up before losing access; recovery requires the necessary fragments and recovery information.
Does VaultKeepR work with passkeys and biometrics?
VaultKeepR supports WebAuthn passkey unlocking through PRF on compatible browsers and authenticators. Biometric unlocking and autofill depend on the app, device, and OS support. Check your setup before relying on a passkey as your only way back into the vault.
Where is my data actually stored?
VaultKeepR keeps an encrypted local vault and syncs an encrypted vault blob through IPFS. Shamir recovery fragments are separate from that blob. Remote access depends on gateways, continued pinning, and the configured storage services, including S3 backup. Keep a local copy or export that you can unlock.
Switching managers is also a good time to close the accounts you no longer use. Our guides cover how to delete accounts on 15 major services.
Try a local-first vault
Use the transfer method for KeePass above, then verify the imported entries. Keep a backup and your unlocking material available.