What template format does else.events use?

Templates are written in MJML — a responsive email markup language that compiles to HTML. You get a visual preview and a code editor.

Can non-developers edit templates?

Yes. The template UI is designed for product managers and designers who understand HTML basics. Deployments are not required for any change.

Is there version history?

Yes. Every saved version is stored. You can compare versions, see what changed and roll back to any previous state.

How do brand variables work?

You define global variables (logo URL, primary colour, app name, footer address) at workspace level. Each template can reference them as {{ brand.logo_url }} or {{ brand.primary_color }}.

Manage SaaS email templates without touching your codebase

Edit copy, update branding, add a new locale or preview changes — none of it requires a pull request or a deployment.

Start managing your templates See how it works

Template management is broken when templates live in your repo

Every copy change requires a deploy

Fixing a typo, updating a CTA or adjusting tone triggers a full release cycle.

No preview without running the app

Verifying how a template looks requires spinning up a local environment or waiting for staging.

Locales multiply the maintenance burden

Supporting German or French means duplicating templates and keeping them in sync manually.

Brand updates are risky

Changing a logo or primary colour across all templates is a manual, error-prone process.

A proper home for your SaaS email templates

Edit without deploying

Templates live in else.events. Update subject lines, body copy or CTAs from the UI — live immediately.

Versioning and history

Every change is versioned. Roll back to any previous version with one click.

Locale support built in

Add a German variant to any template. else.events selects the right locale at render time based on your event payload.

Brand variables

Define your logo URL, primary colour and app name once. Every template inherits them automatically.

Preview before sending

Render any template with a test payload before it goes live. Desktop and mobile preview.

Why keeping templates outside your codebase matters

Product teams move faster

Copy changes, A/B subject lines and seasonal updates do not wait for engineering capacity.

Lower deployment risk

Email template changes are isolated from application releases. Nothing to break.

Consistent branding

Brand variables propagate across all templates. One update, every email.

Audit trail

Version history shows who changed what and when. Useful for compliance and debugging.

Frequently asked questions

What template format does else.events use?: Templates are written in MJML — a responsive email markup language that compiles to HTML. You get a visual preview and a code editor.
Can non-developers edit templates?: Yes. The template UI is designed for product managers and designers who understand HTML basics. Deployments are not required for any change.
Is there version history?: Yes. Every saved version is stored. You can compare versions, see what changed and roll back to any previous state.
How do brand variables work?: You define global variables (logo URL, primary colour, app name, footer address) at workspace level. Each template can reference them as {{ brand.logo_url }} or {{ brand.primary_color }}.

Your templates, out of your codebase

Start with one template. Add locales, versions and brand variables as you grow.

Free during public beta
MJML-based responsive templates
Version history included