Building Calder: why I started a developer-first email API
Every project I shipped needed transactional email, and every time I wired up a provider I rebuilt the same three things. Calder is my attempt to build them once, properly.
Every project I shipped needed transactional email, and every time I wired up a provider I rebuilt the same three things. Calder is my attempt to build them once, properly.
Calder started as an annoyance. Every project I shipped needed transactional email, password resets, receipts, notifications, and every time I wired up a provider I ended up rebuilding the same three things: templates, delivery tracking, and a dashboard that tells me what actually happened to the email I sent.
Email is the only feature users judge by its absence. A broken checkout page gets reported. A password reset that never arrives just becomes a user who never comes back. Yet in most codebases email is the last thing wired up, usually with a provider SDK copy-pasted from a tutorial and a prayer.
I wanted the opposite: email as a first-class primitive, designed the way I'd design any other API. One call in, a predictable event stream out.
Calder's first primitive is a single POST: a template, a recipient, and variables. Everything else, rendering, sending, retries, webhooks, hangs off that one shape.
The system behind it is deliberately boring, too: an API app, a dashboard app, an async worker for sending and retries, and shared packages for the database, queue, providers and observability. Example curl first, so nothing depends on a published SDK:
curl -X POST https://api.calder.dev/v1/emails \
-H "Authorization: Bearer $CALDER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "password-reset",
"to": "[email protected]",
"variables": { "name": "Ada", "resetUrl": "https://…" }
}'One call. Rendering, retries and delivery events hang off it, and the events come back as webhooks, sent, delivered, bounced, complained.
Tip
Start with the boring primitive. If the core call feels inevitable, the rest of the product designs itself.
Calder is not "done", and I'd rather tell you that than pretend:
Note
When your README has a "launch availability" section, keep it honest. The fastest way to lose a developer's trust is a feature list that's really a roadmap.
The bet is settled though: email deserves the same engineering respect as payments. Build it once, build it properly.
Daniel Oluwadare · Emerald
Software engineer on TestFlow, and the person writing everything here. I build in public and post what I learn.
14 Nov 2026 · 3 min
Why my GitHub bot moved from WhatsApp to Telegram
A bot that pipes GitHub events into a chat I actually read. The WhatsApp version worked; Telegram made it maintainable. Here's the trade, and the architecture underneath.
6 Nov 2026 · 4 min
Building TestFlow: what a real exam backend taught me about users
1,500+ questions, 1,300+ students, and a lecture timetable that does not care about my deploy schedule. The backend decisions that made TestFlow survive contact with real students.
22 Oct 2026 · 1 min
TypeScript patterns I actually use in production
No clever type gymnastics, just the handful of patterns that have saved me from real bugs in real codebases.