// built to vanish
disposable, programmable email for people who read headers.
// the drawer of shame
Every developer has the same drawer of shame: a dozen test inboxes, half of them shared, all cluttered with “verify your account” emails from six months ago.
You sign up, alt-tab to your inbox, squint for the 6-digit code, paste it before it expires, and do it again on the next test run.
ephemail started with one stubborn belief: receiving a test email should be as easy as making an HTTP request. No new mailbox. No shared QA account with a password taped to a Slack channel. No screenshots of codes. Just an address that exists the moment you need it and disappears the moment you don't.
// what we believe
data you don't keep can't leak. inboxes expire, messages clear, nothing lingers longer than it has to.
rest api, realtime delivery, wait-for-message, webhooks, sdks. the best test inbox is one your code can drive.
sandboxed rendering, hashed keys, tenant isolation, short retention. safety is a default, not a toggle.
// who it's for
qa engineers automating signup & verification flows
developers building login, 2fa, and magic-link systems
teams who need a sane shared place for test mail
anyone who wants a throwaway address that won't follow them home
// founder note
amine gharby
“I built ephemail because I was tired of fighting my own inbox to ship software. The same papercut kept showing up: waiting on email I couldn't control.
ephemail is the tool I wished existed — fast, private, and made for the terminal, not the marketing calendar. If it saves you the drawer of shame, it's doing its job.”
— amine gharby, founder, ephemail