No event-driven routing
Postmark sends what you tell it to send. Deciding which template to send based on plan, locale or tenant is your problem.
Not a replacement. A layer on top.
More than a Postmark alternative — a workflow layer for SaaS email
Postmark excels at reliable delivery. else.events adds event-driven routing, template management, rules and structured logs on top — and can use Postmark as its provider.
What Postmark alone does not give you
Templates managed in Postmark or in your code
Postmark has a basic template editor. But connecting the right template to the right event, plan and locale is manual work.
No rule engine
You cannot tell Postmark "if plan = Free AND locale = de, use this template". That logic has to live in your application.
Logs without domain context
Postmark activity logs show delivery status. They do not show you which domain event triggered the email or which rule matched.
else.events adds what Postmark does not have
Use else.events as the workflow layer in front of Postmark — or replace Postmark with any SMTP-compatible provider.
Event-driven by design
Fire domain events from your app. else.events routes to the right template via rules — Postmark delivers.
Template management outside your codebase
Create, version and preview templates in else.events. Postmark handles delivery; else.events handles the content.
Rule-based routing
Match by event type, plan, locale, tenant or any payload field. No conditional logic in your application.
Structured delivery logs
Every event, matched rule and Postmark delivery status in one place with full domain context.
Postmark vs else.events vs else.events + Postmark
| Capability | Postmark alone | else.events alone | else.events + Postmark |
|---|---|---|---|
| Reliable transactional delivery | ✓ (best-in-class) | ✗ (no own infra) | ✓ (via Postmark) |
| Event-driven routing | ✗ | ✓ | ✓ |
| Rule-based template selection | ✗ | ✓ | ✓ |
| Template management UI | Basic | ✓ | ✓ |
| Locale support per template | Manual | ✓ | ✓ |
| Domain event logs | ✗ | ✓ | ✓ |
else.events and Postmark complement each other. else.events is not a Postmark replacement — it is the workflow layer in front of it.
Frequently asked questions
- Does else.events work with Postmark?
- Yes. Configure Postmark as your delivery provider in else.events. Events flow through else.events for routing and templating, then Postmark delivers the email.
- Should I cancel Postmark if I use else.events?
- No. Postmark is an excellent delivery provider. else.events adds a workflow and template management layer on top. They work together.
- Can I switch from Postmark to another provider later?
- Yes. Provider configuration is a workspace setting. Switching from Postmark to SMTP or another provider does not require changing your application code.
- Does else.events replace Postmark templates?
- else.events manages your templates and renders them before sending. You do not use Postmark templates when routing through else.events — templates live in else.events.
Use Postmark for delivery. Use else.events for everything else.
Event routing, template management, rules and logs — on top of your existing delivery provider.
- Works with Postmark
- Free during public beta
- No code change to switch providers later