No template management
SES has basic template support but no versioning, no locale management and no non-technical editor UI. Template logic lives in your code.
The workflow layer above SES
Amazon SES alternative — or the workflow layer your SES setup is missing
Amazon SES gives you raw, cost-effective email sending infrastructure. else.events adds what SES does not have: event-driven routing, rule-based template selection, a template management UI and structured domain event logs.
What Amazon SES leaves to you
No rule engine
SES sends what your application tells it to. Conditional routing based on plan, locale or tenant must be implemented in your application code.
No domain event context
SES logs show delivery status. They do not show which domain event triggered the send or which business rule matched.
Configuration complexity
SES requires managing verified identities, sending limits, DKIM, bounce and complaint handling — infrastructure burden that grows as you scale.
Add else.events above SES — or replace SES entirely
Use SES as your delivery provider in else.events — or switch to Postmark, Resend or SMTP. else.events adds the workflow layer regardless of which provider you choose.
Event-driven routing above SES
POST domain events from your app. else.events matches rules, selects templates and routes to SES — no application-level email logic.
Template management UI
Manage, version and preview templates in else.events. SES delivers the rendered output. No deployment for copy changes.
Switch away from SES without code changes
Change your delivery provider setting in else.events. Application code stays the same.
Structured domain event logs
Every log entry shows the domain event, matched rule and SES delivery outcome — full traceability.
How it works with SES
Your app fires an event — else.events routes — SES delivers
{
"type": "invoice.payment_failed",
"user": { "email": "customer@example.com", "name": "Alex" },
"data": {
"plan": "Pro",
"amount": "29.00",
"currency": "EUR",
"update_payment_url": "https://app.example.com/billing"
}
}else.events matches this event against your rules, selects the correct localized template and delivers through SES — without touching a line of application code.
Amazon SES vs else.events — what each covers
| Capability | Amazon SES | else.events | else.events + SES |
|---|---|---|---|
| Email delivery infrastructure | ✓ (low cost, high volume) | ✗ (uses your provider) | ✓ (via SES SMTP) |
| Event-driven routing | ✗ | ✓ | ✓ |
| Rule-based template selection | ✗ | ✓ | ✓ |
| Template management UI | Basic | ✓ | ✓ |
| Locale support per template | ✗ | ✓ | ✓ |
| Domain event logs | ✗ | ✓ | ✓ |
| Setup complexity | High (DKIM, identities, limits) | Low | Medium |
else.events can use SES via SMTP as a delivery provider. You can keep your existing SES setup and add else.events in front.
Frequently asked questions
- Can else.events work with Amazon SES?
- Yes. Configure SES via SMTP in else.events. Domain events are routed and templates rendered by else.events, then SES delivers the email.
- Does else.events require me to leave Amazon SES?
- No. else.events is provider-agnostic. You can keep SES as your delivery provider and add else.events in front for event routing, template management and logs.
- What is the main reason to add else.events above SES?
- SES handles delivery well but has no event-driven routing, no rule engine and no template management UI. else.events adds the workflow layer your application-level email logic currently handles.
- Can I switch from SES to another provider later?
- Yes. Change your provider setting in else.events. Application code stays the same — no SES-specific patterns to rework.
Add the workflow layer your Amazon SES setup is missing
Event routing, rule-based template selection, template management UI and structured logs — on top of SES or any other provider.
- Works with SES via SMTP
- Free during public beta
- Switch providers without code changes