Is else.events only a CMS or does it send emails too?

Both. else.events manages your templates and also handles routing and delivery through your configured provider (Postmark, SMTP, etc.).

Can I use else.events just for template rendering without sending?

The primary use case is end-to-end: event in, email out. Template-only rendering without delivery is not the designed flow.

How do locales work at render time?

Include a locale field in your event payload (e.g. "locale": "de"). else.events selects the matching template variant. If no variant exists, the fallback locale is used.

What happens if I update a template while emails are in flight?

Template changes are applied immediately to new events. Events already being processed use the template version active at processing time.

Content management for product emails

A headless CMS for your SaaS emails

Manage transactional email templates outside your application. Edit via UI or API, add locales, version everything — rendered on demand per event.

Start building your email CMS Explore template management

Product emails need content management, not just sending infrastructure

Email providers give you sending, not content management

Postmark, Resend and SendGrid deliver emails. They do not give you a proper home for template content, versions and locales.

Headless CMS tools are not built for transactional email

Contentful or Sanity manage web content. Rendering an MJML template from a Stripe webhook is not what they are designed for.

Inline code templates do not scale

Template strings in your NestJS service or Rails mailer work for one template. Not for 20 templates across 5 locales.

else.events as your headless email CMS

Templates managed via UI or API

Create and update templates through the else.events dashboard or via the management API. No repo access needed.

Locale variants per template

Add English, German or any other locale variant. The event payload selects the right one at render time.

Render on demand

Send an event, else.events renders the template with your payload data and delivers through your provider.

Brand variables as global content

Logo, colours, app name and footer — defined once, inherited by every template.

Frequently asked questions

Is else.events only a CMS or does it send emails too?: Both. else.events manages your templates and also handles routing and delivery through your configured provider (Postmark, SMTP, etc.).
Can I use else.events just for template rendering without sending?: The primary use case is end-to-end: event in, email out. Template-only rendering without delivery is not the designed flow.
How do locales work at render time?: Include a locale field in your event payload (e.g. "locale": "de"). else.events selects the matching template variant. If no variant exists, the fallback locale is used.
What happens if I update a template while emails are in flight?: Template changes are applied immediately to new events. Events already being processed use the template version active at processing time.

Move your email templates out of your codebase

Start with one template. Render it from a domain event. Everything else follows naturally.

Free during public beta
UI and API access
Locale support built in