Back to blog
building

NoDramaMail was built on warpkit in one evening

By Team

We send email for several products through Amazon SES. SES is cheap and reliable, and it tells you almost nothing. An email is accepted, and after that you are on your own. If it bounced, you find out when a user writes in, or when AWS sends a warning about your bounce rate.

So we built NoDramaMail: a dashboard that receives every SES event and shows what happened to each email. The first working version took one evening. This post is about why that was possible.

What had to be written

The part that is NoDramaMail's own is small:

  • A receiver for the delivery reports SES sends, which checks each one is real and stores it.
  • Queries for the event feed, the message timeline and the rates.
  • The pages that show them.
  • A nightly job that deletes old events, and one that checks the rates and sends an alert.

What did not have to be written

Everything else came with the warpkit template:

  • Sign-in. Email codes, sessions and rate limits were already there.
  • A database per user. One account can never read another's events.
  • Background jobs. The retention and alert jobs are two handlers added to a queue that already existed.
  • API keys. For the coding agent integration.
  • Tests and CI. New code went into a setup that already checked every change.

None of those are interesting to build, and all of them take days when you start from nothing. With them in place, the evening went to the product.

What happened next

The second day went to the part we underestimated: setting up SES itself. Verifying a domain, signing, delivery reporting, a sending login and a production access request, across several AWS consoles. We replaced all of it with one step.

NoDramaMail now watches the email of our own products. What we miss while using it decides what gets built next: acting on bounces, deliverability checks, and providers beyond SES.