Can else.events use Resend for delivery?

Yes. Configure Resend as your SMTP provider in else.events. Events are routed and templates rendered by else.events, then Resend delivers.

Does else.events replace Resend completely?

else.events does not have its own sending infrastructure. It is the workflow layer in front of your delivery provider — which can be Resend.

What if I like React Email from Resend?

else.events uses MJML-based templates. If React Email is a hard requirement, else.events may not be the right fit. For teams that want a workflow layer without framework lock-in, else.events is a good alternative.

How hard is it to switch from Resend to else.events?

You add the else.events event API call to your backend and configure your provider (including Resend if you want to keep it). Template migration depends on how many templates you have.

Going beyond the sending API

A Resend alternative that adds workflow and template management

Resend is a great developer-first sending API. else.events adds what comes next: event-driven routing, rule-based template selection, locale support and a template management UI — on top of any delivery provider.

Start building your email workflow See how event-driven email works

What a sending API alone does not solve

Template selection logic in your code

With Resend, you decide which template to use in application code. As email use cases grow, that logic multiplies across services.

No rule engine

Routing by plan, locale or tenant with Resend requires conditionals in your application. There is no configuration layer.

No template management UI

Resend has no built-in template editor or versioning. Templates live in your codebase or in React Email files.

Provider lock-in

React Email and Resend-specific patterns make it hard to switch providers later without reworking your email layer.

else.events: workflow and template management for SaaS product emails

Use else.events for event routing, rule matching and template management. Use Resend — or any other provider — for delivery.

Event-driven routing

POST domain events from your app. else.events decides the template, locale and provider — no application-level conditional logic.

Rule-based template selection

Route by event type, plan, locale or tenant without modifying application code.

Template management UI

Create, preview and version templates in else.events. Non-technical team members can update copy without deploys.

Provider-agnostic

Configure Resend, Postmark, SMTP or any supported provider. Switch without changing application code.

Resend vs else.events — what each adds

Capability	Resend	else.events
Email delivery API	✓	Uses your provider
Event-driven routing	✗	✓
Rule-based template selection	✗	✓
Template management UI	✗	✓
Locale support	Manual	✓
Multi-tenant support	Manual	✓
Provider lock-in	Moderate	None

else.events can use Resend as a delivery provider. You can use both together.

Frequently asked questions

Can else.events use Resend for delivery?: Yes. Configure Resend as your SMTP provider in else.events. Events are routed and templates rendered by else.events, then Resend delivers.
Does else.events replace Resend completely?: else.events does not have its own sending infrastructure. It is the workflow layer in front of your delivery provider — which can be Resend.
What if I like React Email from Resend?: else.events uses MJML-based templates. If React Email is a hard requirement, else.events may not be the right fit. For teams that want a workflow layer without framework lock-in, else.events is a good alternative.
How hard is it to switch from Resend to else.events?: You add the else.events event API call to your backend and configure your provider (including Resend if you want to keep it). Template migration depends on how many templates you have.

Beyond the sending API — event-driven SaaS email workflows

Event routing, rule-based template selection and a template management UI — on top of any delivery provider.

Works with Resend as a provider
Free during public beta
No application code changes when switching providers