Trust Envelope

A Weekend Project That Admits It Doesn't Know What It Is

When ebfe1 posted Trust Envelope on Show HN, the title was disarmingly honest: "Yes, I vibed coded something But not sure what to do with it." The post sat at 2 points, 2 comments — nearly invisible. A yellow banner on the site reads: "Under construction & unstable — This is an early testing phase. Expect bugs and changes." No manifesto, no roadmap, no pitch deck. In a Show HN landscape full of confident launches, this kind of candor is rare.

The Problem: Words You Can't Say Alive, Can't Take When You Die

The core idea is straightforward: write letters, record voice messages, or leave videos, encrypted and stored, to be delivered to specific people under specific conditions after you die. What elevates it beyond typical digital-estate tools is the delivery trigger: not just "X days after death," but life events — "your child's wedding day, their first heartbreak, the day they become a parent." Most end-of-life tech focuses on asset distribution. Trust Envelope focuses on emotional time capsules. You can't stand up from the grave at your daughter's wedding, but you can pre-record a message that arrives that morning.

The Build: Vibe-Coded Full Stack, Encryption as Core Promise

The author calls it "vibed coded" — built with AI coding assistants (likely Cursor or Copilot). The product supports text, audio, and video, all end-to-end encrypted, with only ciphertext stored server-side. Probably Next.js full stack plus a crypto library like libsodium or Web Crypto API. No public repo, no detailed docs. But the E2E encryption promise raises the hardest question: key management. Who decrypts after the user dies? Is the key pre-shared with recipients, or is there a trusted third party? The site doesn't answer this — and it's the question on which the entire value proposition depends.

Community Response: Gentle Skepticism and Genuine Empathy

The two comments each captured a different lens. DostLeFan wrote: "vibe coding something doesn't automatically mean it's bad or poorly made. But today, it's undeniable that we can't rely 100% on something built entirely by AI," then added (the comment trails off): "this is exactly what's bea..." — clearly wanting to say the beauty is in the intention itself. syllogistic offered: "At the very least this sort of thing can be cathartic. I hope it helped you in your situation and the process itself made it worth it, even if it doesn't become a thing." Neither commenter poked at the tech stack. Both were responding to something personal between the lines — ebfe1 likely built this because they lost someone.

Honest Limitations: It's More of a Letter to Itself

The hard questions pile up fast: who covers long-term hosting costs? How do you verify death and trigger delivery? How do encryption keys survive their owner? Does this count as a will — does it need notarization? None of these are answered. But here's the counterpoint: maybe that's exactly the value of vibe-coded indie projects in the AI era. Not every project needs to become a company. Some projects matter because they got built at all. ebfe1 turned an emotional intuition into a clickable product in a weekend. Even if it goes offline tomorrow, the process itself already answers the question buried in that HN title.