Change the email without a deploy.
Templates live in a Git-backed project, written in TSX. Save is a commit, publish is a version your sends use, and every change can be reviewed as a diff, whether you or your agent made it.
When templates live in app code, every copy change waits for a deploy. When they live in a separate tool, they drift from what the code sends.
- VERSIONSversioned in a Git-backed project
- YOUR AGENTsaves with templates_save_workspace
- PUBLISHEDa41f9c2 is the one that sends
Write, edit, review, and roll back.
Write or start from the gallery.
TSX with email components that handle table layout and older Outlook for you, or a gallery starting point.
Edit where you like.
Your editor with local preview, the AI email editor, or your coding agent over MCP.
Review and publish.
Check the diff, render the fixtures, and publish that exact commit. Sends pick up the new version with no code change.
Roll back.
Restore an earlier version and publish it, or pin a send to a specific version.
You edit, you approve, the send stays put.
Your agent edits, you approve
Over MCP your agent opens the project, makes the change, and shows you the diff. You publish the version you reviewed.
Pass data, get the finished email
Templates render on the server from the data you send. The send call never changes.
One brand everywhere
Logo, colors, and footer come from your brand settings, so every template matches.
For the rest of the team
The AI email editor lets anyone change copy and see the result, no account needed to start.
Common questions.
Do I have to write TSX?
No. Start in the AI email editor or from the gallery. TSX is there when you want the template in code review.
How do I roll back?
Restore the earlier version into a draft, preview it, and publish it. Or pin a send to a specific published version.
Can my coding agent change templates?
Yes. Through hosted MCP it can open the project, edit, show the diff, and save. You decide what gets published.
Where do the templates live?
In a Git repository for your project. You can clone it and work in your own editor.
The rest of the email API.
Send email in one typed call
Transactional email from the SDK, REST, CLI, or your agent through MCP. Retries are safe.
Replies land in your app
Receive on your domain, parsed and threaded to the email it answers, delivered as a signed webhook.
Change the email without a deploy
Versioned templates in Git. Review the diff, publish that version.
Know why an email did or didn't land
SPF and DKIM on your domain, suppression you can see, events for every send.
Send the announcement too
Campaigns go to a list of contacts from the same templates and domain.
An inbox for your AI agent
A mailbox your agent reads and replies from, with a key that reaches only it.