Resend: developer-first email delivery
Resend provides a clean REST API and SDKs for sending transactional emails with good deliverability and a React Email integration.
Tool comparison
Resend vs else.events — clean API vs workflow layer
Resend is a clean, developer-first email sending API. else.events is the event-driven workflow and template management layer that sits in front of your email provider — including Resend.
What each tool solves
else.events: workflow and template management layer
else.events receives domain events, matches rules and selects the right template before handing off to your delivery provider.
Template logic still lives in your app
Resend sends what you pass to it. Deciding which template to use, which locale to render, which variables to inject — that logic is yours to write and maintain.
Growing complexity over time
Teams that start with Resend often accumulate conditional email logic in services, scattered template strings and no central view of what emails exist.
Use else.events as the layer in front of Resend
else.events handles event routing, rule matching and template management. Resend handles delivery. Configure Resend as your provider in else.events.
Event-driven, not call-driven
POST a domain event from your app. else.events decides the rest — template, locale, variables, provider.
Templates outside your codebase
Manage and preview templates in else.events. Resend delivers whatever is rendered.
Rule-based routing without application logic
Match by event type, plan, locale or payload field without conditionals in your code.
Switch providers without code changes
Change your delivery provider from Resend to Postmark or SMTP in workspace settings — no application code change.
Resend vs else.events — what each covers
| Capability | Resend | else.events | else.events + Resend |
|---|---|---|---|
| Email delivery API | ✓ (developer-first) | ✗ (uses your provider) | ✓ (via Resend) |
| React Email support | ✓ (native) | ✗ | ✗ |
| Event-driven routing | ✗ | ✓ | ✓ |
| Rule-based template selection | ✗ | ✓ | ✓ |
| Template management UI | ✗ | ✓ | ✓ |
| Locale support per template | Manual | ✓ | ✓ |
| Domain event logs | ✗ | ✓ | ✓ |
else.events can use Resend as its delivery provider. They complement each other.
Frequently asked questions
- Can I use else.events with Resend?
- Yes. Configure Resend as your delivery provider in else.events. Domain events flow through else.events for routing and templating, then Resend delivers the email.
- Does else.events support React Email like Resend does?
- else.events has its own MJML-based template editor. React Email templates are a Resend-specific feature. If React Email is a hard requirement, you may need a different setup.
- Can I switch from Resend to another provider?
- Yes. Provider configuration is a workspace setting in else.events. Switching from Resend to Postmark or SMTP does not require code changes in your application.
- Is else.events only for developers who use Resend?
- No. else.events works with any SMTP-compatible provider or Postmark. Resend is one option among several.
Add workflow and template management to your Resend setup
Event routing, rule-based logic, template management and structured logs — in front of your delivery provider.
- Works with Resend
- Free during public beta
- Switch providers without code changes