Templates · in development
Emails your designer would sign off on.
Versioned templates with variables, previews, and one-click publishing — so 'can you tweak the receipt?' stops meaning a code deploy. We're finishing the delivery core first, then this.
Write once, render everywhere
Define a template with named variables, preview it with real sample data, then publish a version. Sending references the template and version — rolling back is one click, not one deploy.
- Variables with safe defaults, no broken {{ }} in inboxes
- Every version kept, every send traceable to its version
- Test sends to yourself before anything goes live
Bring any HTML in the meantime
Templates don’t block you. Send fully-rendered HTML today — React Email, MJML output, hand-rolled tables, whatever your stack produces. When templates land, your existing sends keep working untouched.
$ curl https://api.calder.click/v1/emails
-d '{"html": "<p>…</p>"}' // any HTML you likeGet started
Go get your first delivery.
Not your first signup form, not your first dashboard tour — your first email, landing in an inbox, with the webhook to prove it. Test keys are free and can’t hurt anything. The only thing standing between you and that little delivered tag is one POST request.