KeePassXC vs RoboForm Comparison
| Feature | ||
|---|---|---|
| Overview | ||
| Rating | 8.0 | 7.4 |
| Pricing | Not specified |
Show billing detailsHide billing details
|
| Free tier | Free tier | Limited free tier |
| Established | 2016 | 2000 |
| Platforms | ||
| Security | ||
| Independent security audit | Synacktiv (ANSSI CSPN) 2025Show audit detailsHide audit detailsFirst-level security certification of KeePassXC 2.7.9 on Windows — full source-code review, penetration testing of every security function, and cryptographic and random-number-generator analysis | None on record |
| Source code | Fully open source | Closed source |
| Encryption | AES-256, Argon2dShow detailsHide detailsThe database is encrypted with AES-256 by default (Twofish and ChaCha20 are also selectable) in the KDBX 4 format, with an HMAC-SHA-256 integrity check that detects tampering. The master key is derived with Argon2d by default — a memory-hard function that resists GPU and ASIC cracking — with the older AES-KDF still available. The composite master key can combine a password, a key file, and a YubiKey or OnlyKey challenge-response secret. | AES-256, PBKDF2-SHA256 1MShow detailsHide detailsThe vault is encrypted client-side with AES-256 using a key derived from the Master Password via PBKDF2 with SHA-256 and a random 32-byte salt, at 1,000,000 iterations by default — the same order of magnitude as the highest iteration counts in this category, though PBKDF2 remains a non-memory-hard KDF unlike Argon2. Only a one-way, server-side password derived from the Master Password is ever sent to RoboForm's servers; all encryption and decryption happens locally. |
| Vault 2FA | Hardware keys | TOTP + hardware keys |
| Second-secret model | No | No |
| Past data breach | No | No |
| Telemetry | No telemetry | Opt-in |
| Features | ||
| Hosting | Local, no cloud | Cloud |
| Passkeys | Stores for sites | Stores + unlocks |
| Built-in email aliases | No | No |
| Company | ||
| Owner | KeePassXC TeamShow detailsHide detailsVolunteer, community-run open-source project under the keepassxreboot organization on GitHub — no company and no venture funding behind it. Development is paid for by donations. Forked from KeePassX in 2016; the KeePass lineage goes back to 2003. | Siber Systems, Inc.Show detailsHide detailsPrivately held and independently operated since RoboForm's original 2000 release; not venture-backed and never acquired. Headquartered in Fairfax, Virginia, led by CEO Vadim Maslov. Siber Systems also makes GoodSync, a file-synchronization product, alongside RoboForm. |