Revault vs. Vaultaire
Both apps focus on private files and pattern-based access. The practical differences are where you use them, how cloud copies move, and what recovery and sharing mean.
Reviewed October 28, 2026 · Sources belowThe feature breakdown
| What matters | Revault | Vaultaire |
|---|---|---|
| Platforms | Web, native iOS, and native Android implementations. Native store distribution depends on release availability. | iPhone and iPad. [1] |
| Account requirements | No Revault account on mobile. The web app uses a passkey account. Native cloud sync requires the corresponding Apple or Google account. | No identity account or email sign-up; cloud features use iCloud. [1] |
| Cryptography | AES-256-GCM; device pattern plus a random device secret; PBKDF2-SHA-256 wrapping and HKDF-SHA-256 streaming file encryption. | AES-256-GCM with pattern-based key derivation and a random master key. [1] |
| Cloud storage | Local storage by default. Optional private iCloud on iOS or Google Drive appDataFolder on Android. The web cloud is separate. | Encrypted iCloud backup, enabled by default with an off switch; CloudKit sync and sharing. [2] |
| Recovery | A separate vault recovery key plus an encrypted cloud copy or .qvault backup. A web account reset cannot decrypt a vault. | A recovery phrase and documented protected recovery paths; support cannot bypass encryption. [2] |
| Sharing | Native file and vault snapshots use unrestricted private CloudKit invitations on iOS, or controlled server invitations with a separate share secret across iOS and Android. Web-cloud files use encrypted links. | Read-only shared vaults receive encrypted updates through CloudKit. A separate one-time phrase claims access; expiry and open limits are enforced by the recipient app. [3] |
| Emergency pattern | Safe Exit opens a designated vault and removes other local vault access and cached data. Cloud copies remain; forensic erasure is not guaranteed. | Duress mode removes local non-duress indexes and recovery mappings; backups and other copies may remain. [2] |
A vault that starts on your device.
You want an account-free native vault on iOS or Android, with a separate web app and portable encrypted backups.
A different workflow fits better.
You primarily use iPhone or iPad and want Vaultaire’s CloudKit vault sharing and pattern-oriented workflow.
Know the tradeoffs.
Revault shares independent file or vault snapshots. Controlled server shares can limit access sessions and expiry, but cannot revoke copies already exported. It does not send ongoing shared-vault updates. Platform clouds stay separate; use the independently encrypted phone migration flow to move between iOS and Android.
No app can protect unlocked files from a compromised device. Exporting a decrypted file creates a copy outside the vault; deleting access cannot recall copies someone already saved. Keep recovery secrets and tested backups separately.
Revault’s security modelSources & scope
Primary documentation checked on October 28, 2026. Comparisons describe the documented personal product, not every enterprise plan or add-on. No price ranking is included because pricing varies by region and store.
- Vaultaire: product and security overview
- Vaultaire: terms, cloud, recovery, sharing and duress behavior
- Vaultaire: secure sharing and its limits
Revault statements describe the implementation in this project; native store availability depends on release. Revault has not undergone an independent security audit. Vaultaire is a trademark of its respective owner. No affiliation or endorsement is implied.