Version control for your transactional email templates

Every template change is versioned. See the history, roll back instantly, or keep multiple versions in parallel — without touching your codebase.

What goes wrong when templates have no version history

No audit trail for template changes

A template was updated. Open rates dropped. There is no way to see what changed, when or who changed it.

Rolling back means digging through git history

If templates live in your repo, a rollback is a commit and a deploy. If they live in a provider UI, there is no rollback at all.

Breaking changes go live without review

A poorly tested change to the payment failed template goes live immediately, affecting all users until discovered.

No connection between template version and email performance

Open rates changed after a deploy. Which template changed? Which version is now live? No easy answer.

Full version history — roll back, compare, control what goes live

Every save creates a new version

Template edits are non-destructive. The previous version remains available and can be restored instantly.

Roll back in one click

Revert to any previous version without a deployment or a code change. The change takes effect for new events immediately.

Version recorded in delivery logs

Each email delivery log records which template version was used. Cross-reference version changes with delivery metrics.

Approval flow on the roadmap

Future: require a review before a new template version goes live, for teams with strict email quality processes.

Frequently asked questions

How many versions of a template are retained?
All versions are retained while your workspace is active. There is no automatic pruning of old versions.
Can I compare two versions side by side?
A diff view for template versions is on the roadmap. Currently you can browse the version history and restore any previous version.
Does a rollback affect emails already in flight?
No. A rollback changes which template version is used for new events. Emails already queued or delivered are not affected.
Can I have a staging version and a production version of the same template?
Workspace-level environments are on the roadmap. Currently you can use a separate staging workspace for pre-production testing.

Template version control — no git required

Every template change versioned. Roll back instantly. Delivery logs linked to each version.

  • Free during public beta
  • Instant rollback without deployment
  • Version recorded in every delivery log