Enpass vs KeePassXC Comparison
| Feature | ||
|---|---|---|
| Overview | ||
| Rating | 6.8 | 8.0 |
| Pricing |
Show billing detailsHide billing details
| Not specified |
| Free tier | Limited free tier | Free tier |
| Established | Not specified | 2016 |
| Platforms | ||
| Security | ||
| Independent security audit | None on record | 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 |
| Source code | Closed source | Fully open source |
| Encryption | AES-256, PBKDF2-HMAC-SHA512 320KShow detailsHide detailsThe vault is a SQLite database encrypted via SQLCipher (AES-256-CBC). The Vault Key is derived from the Master Password — and, optionally, a keyfile — using PBKDF2-HMAC-SHA512 at 320,000 iterations, with a unique random salt per database. | 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. |
| Vault 2FA | None | Hardware keys |
| Second-secret model | No | No |
| Past data breach | No | No |
| Telemetry | On unless you opt out | No telemetry |
| Features | ||
| Hosting | Local, no cloud | Local, no cloud |
| Passkeys | Stores for sites | Stores for sites |
| Built-in email aliases | No | No |
| Company | ||
| Owner | Enpass Technologies Inc. | 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. |