Work/getrandom.email
EmailCustom Software Development

getrandom.email

getrandom.email provides temporary inboxes and paid addresses for ongoing use. We built the signup-free service, subscriptions and mailbox API, with deletion recovery, permanent address reservation and checks on incoming delivery.

getrandom.email: Disposable inboxes and addresses for ongoing use
2 s
approx. send-to-inbox time
30 days
to undo a deletion
API
programmatic inbox access

An address for now, with an option to keep it

A temporary address lets someone try a service without sharing their everyday inbox. We built getrandom.email with an address available immediately, without registration, and incoming messages appearing automatically. The free mailbox lasts thirty minutes. Paid subscribers can retain addresses and manage them from a dashboard.

The pricing page: a free tier with a thirty-minute mailbox and no signup beside a nine-dollar tier with mailboxes that stay and API access.
View full size

What happens when an address is deleted?

A deleted paid mailbox stops accepting mail, but its owner has thirty days to restore it before the contents are destroyed. The address remains reserved after that window and is never reassigned. This prevents a later user receiving messages, such as password resets, intended for the previous address holder.

An inbox other software can use

Paid subscribers can also access their mailboxes through an API, so their software can work with incoming mail without someone opening the website. The reference documents the operations available to an API key, while the dashboard remains available for managing the same addresses.

The API documentation page, offering a reference generated from the code itself and a narrowed schema covering only the endpoints a key can call.
View full size

Checking delivery beyond the website

An inbox can look normal even when incoming delivery has failed. We added an hourly check that sends a message from outside the service through the normal mail route and waits for it to arrive. If it does not, the service alerts its operator. This checks the receiving path as well as whether the application is online.

Tech stack

Technologies we used

Server-side
PythonDjangoDjango NinjaCeleryPostgreSQLRedis
Client-side
Next.jsReactTailwind CSSTypeScript
Integrations
CloudflareStripe
Infrastructure
Docker ComposeAnsibleGHCRGitHub Actions
Next projectSecurity labs with LSCP
→

Have a similar challenge?

Work directly with the people building your software. Leave your contact details and we’ll reply within 24 hours.

Discuss your projectSee our work