Matt Alcorn

Emberlay - Make sure your family has answers when they need them most

by
Emberlay is an encrypted vault that gives your family access to important documents when you can't be there — hospitalization, incapacity, or death. Upload files, choose trusted partners, print a physical Legacy Key. When they need access, they claim it through a cool-down period that protects against unauthorized use. Zero-knowledge encryption means we can't read your files. No AI scanning. Per-file permissions. $30/year, 7-day free trial, two-minute setup.

Add a comment

Replies

Best
Matt Alcorn
Maker
📌
Hey everyone! I'm Matt, the maker. I built Emberlay because I realized that if something happened to me tomorrow, my family would have no idea where to find anything. Insurance policies buried in email. The will in a filing cabinet my wife has never opened. Account credentials scattered across apps. Medical directives... somewhere. Most of us have this problem. We just don't think about it until it's too late. The core idea: upload your important documents to an encrypted vault, choose who gets access if you can't be there, and print a physical Legacy Key they'll use to claim it. A cool-down period means you're always notified and can cancel unauthorized attempts. What makes it different from a shared Google Drive or password manager: - Files are encrypted on your device before upload (zero-knowledge — I literally can't read your data) - Trusted partners can't passively browse your vault. They have to initiate a claim, and you get notified. - Per-file permissions: your spouse sees everything, your attorney sees the will, your business partner sees credentials - No AI scanning your documents. Ever. - Works for hospitalization and incapacity — not just death Where it is today: The core product is solid — vault, encryption, trusted partners, claims, per-file access, cool-down periods, Legacy Key. $30/year, 7-day free trial. I'm a solo founder (design, engineering, and support are all me), so feedback directly shapes what gets built next. I'd love to hear: - How are you handling this today? Do you have a system for making sure the right people can access the right things? - What would a tool like this need before you'd trust it with your most important documents? - What's kept you from setting something like this up before? Happy to answer any questions about the architecture, the encryption, or the product decisions. Thanks for checking it out!