Can I use else.events with Postmark?

Yes. Configure Postmark as your delivery provider in else.events. Events are routed and rendered by else.events, then delivered through Postmark.

Should I cancel Postmark if I use else.events?

No. Postmark is an excellent delivery provider. else.events is the workflow layer in front of it. They work together.

Can else.events replace Postmark entirely?

else.events does not have its own email infrastructure. It routes through your configured provider — which can be Postmark, SMTP or another service.

Does else.events support Postmark templates?

else.events manages its own templates and renders them before sending. You use else.events templates, not Postmark templates, when routing through else.events.

Tool comparison

Postmark vs else.events — delivery vs workflow layer

Postmark is a best-in-class transactional email delivery API. else.events is the event-driven workflow and template management layer that sits in front of your email provider. They solve different problems.

Start building your email workflow See how it works

What each tool was built for

Postmark: reliable delivery at scale

Postmark is designed for transactional email delivery — fast, reliable, with strong deliverability and clear activity logs.

else.events: event-driven workflow layer

else.events receives domain events from your app, matches rules, selects the right template and routes to your delivery provider.

The gap between them

Postmark sends what you tell it to. Deciding which template to use, which locale to render, which tenant's brand to apply — that logic has to live somewhere.

Where developers end up

Without a workflow layer, that logic spreads through your codebase: conditional sends, hardcoded subjects, locale switches, template strings inside services.

Use both — they complement each other

else.events handles event routing, rule matching and template management. Postmark handles delivery. Together they cover the full email stack.

Event-driven routing

Send domain events from your app. else.events decides which template to use based on event type, plan, locale and tenant.

Template management outside your codebase

Edit templates without deploying. Postmark delivers whatever else.events renders.

Rule-based logic without application code

Route by plan, locale or payload field. No conditionals in your services.

Provider-independent

Switch from Postmark to SMTP or any other provider by changing a workspace setting — no code changes.

How they work together

Your app sends an event — else.events routes and renders — Postmark 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 rules, selects the correct localized template and sends the rendered email through Postmark — no application-level conditional logic required.

Postmark vs else.events — feature by feature

Capability	Postmark	else.events	else.events + Postmark
Transactional email delivery	✓ (best-in-class)	✗ (uses your provider)	✓ (via Postmark)
Event-driven routing	✗	✓	✓
Rule-based template selection	✗	✓	✓
Template management UI	Basic	✓	✓
Locale support per template	Manual	✓	✓
Domain event logs	✗	✓	✓
Multi-tenant support	✗	✓	✓
Webhook delivery events	✓	✓	✓

else.events is not a Postmark replacement. It is the workflow layer in front of Postmark.

Frequently asked questions

Can I use else.events with Postmark?: Yes. Configure Postmark as your delivery provider in else.events. Events are routed and rendered by else.events, then delivered through Postmark.
Should I cancel Postmark if I use else.events?: No. Postmark is an excellent delivery provider. else.events is the workflow layer in front of it. They work together.
Can else.events replace Postmark entirely?: else.events does not have its own email infrastructure. It routes through your configured provider — which can be Postmark, SMTP or another service.
Does else.events support Postmark templates?: else.events manages its own templates and renders them before sending. You use else.events templates, not Postmark templates, when routing through else.events.

Add a workflow layer to your Postmark setup

Event routing, template management, rule-based logic and structured logs — on top of Postmark.

Works with Postmark out of the box
Free during public beta
No code changes when switching providers later