Alternatives
Products that do what Veault – Digital legacy management with secure inheritance and zero-knowledge does
Veault redefines digital legacy planning with client-side zero-knowledge encryption and a fail-safe inheritance system. Unlike typical password managers, Veault never holds your key. It uses a controlled unlock process where trusted contacts use secret keys to request access, tri
- 1
- 2
- 3
- 4
Secure digital legacy with automated trusted contact release
Apr 2026 · digitallegacyvault.app
- 5
- 6
- 7
- 8
- 9
- 10
- 11KE
Keeper is an embeddable secret store (Argon2id, XChaCha20-Poly1305 by default). Four security levels, audit chains, crash-safe rotation. Vault is overkill for most use cases. This is for when you ge paranoid about env and need encrypted local storage that doesn't suck. No security through obscurity, hence, It's still early, so now's the best time to find weird edge cases, race conditions, memory leaks, crypto misuse, anything that breaks. The README has a full security model breakdown if you want to get adversarial.
Apr 2026 · github.com
- 12
- 13
- 14
- 15
- 16
- 17
- 18
100% offline, AES-256 encrypted vault for your legacy
Jul 2026 · digitalwilllocker.com
- 19
- 20
- 21DB
The only way to get a trust-less random value is to have it distributed and time-locked three ways, player, server and a future-entropy. In the demo above, the moment you commit (Roll-Dice) a commit with the hash of a player secret is sent to the server and the server accepts that and sends back the hash of its secret back and the "future" drand round number at which the randomness will resolve. The future used in the demo is 10 secs When the reveal happens (after drand's particular round) all the secrets are revealed and the random number is generated using…
Feb 2026 · blockrand.net
- 22
Securely map your financial life, no credentials required
May 2026 · successionkeeper.com
- 23
- 24LO
Key management for multiple users and multiple cloud LLM/GenAI APIs is difficult to be both safe and convenient. Sharing keys among users risks leaking the key and makes it difficult to curb the leakage without interruptions. But assigning one key per user per cloud API results in too many keys to keep track of. Meet LlaMa(ster)Key, the secure and easy solution for API key management: * For each user, one master key for multiple APIs. * The master key is unique to each user. Granting and revoking a user's access won't impact other users. * The actual API keys to authenticate with cloud…
2024 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →