We're getting close...
If you joined recently: first update covered authentication and security foundation. Second update showed the vault—folders, file uploads, browser-side encryption. Catch up here.
Now: the thing that makes this a dead man's switch actually works.
Contacts and verification
You can add trusted contacts. They get an invitation, verify their email and phone, and that's it, no account needed on their end.
Each contact can be a vault recipient (gets your files), an escalation contact (we ask them if you're okay), or both.
The check-in system
You set an interval. We check in via email, SMS, and WhatsApp (let us know if you feel we should add other channels). You click a link. That's it.
If you don't respond, we try again. Still nothing: we reach out to your escalation contacts. If they confirm something's wrong, your vault recipients get access.
The whole escalation flow is built. Multi-channel notifications, one-click responses, final warnings, timed release.
Everything is tested heavily. When you're building something people trust with their most sensitive files, "it works on my machine" isn't good enough. It needs to be secure, stable, and still working years from now.
MVP nearly complete
All the core pieces are done. Vault, contacts, check-ins, escalation, release. What's left is polish and real-world testing.
Which means: beta soon.
I'll be inviting waitlist subscribers in small batches over the coming weeks. If you want to be in one of the first batches, then make sure you subscribe to the waitlist.
Coming next
A comparison of Trustbourne vs notary-managed digital vaults like IZIMI. Same problem at first glance, very different approaches. What works, what doesn't, and why I built something new.