All your SaaS transactional emails — one place to manage them

Auth emails, billing receipts, onboarding sequences, product notifications, security alerts — scattered across handlers, services and providers. else.events brings them together.

What scattered email infrastructure looks like in practice

Auth emails sent via one provider, billing emails via another

Password resets go through SendGrid. Invoices go through a billing service. Notifications go through a custom handler. No single view.

Templates are spread across repos and services

Auth service has its own templates. Billing service has its own. Notification service has its own. No consistency, no shared tooling.

Support cannot answer "did the customer get the email?"

Without a central log across all email types, answering a basic support question requires checking multiple systems.

Every email type is a separate maintenance burden

Adding a new locale, changing branding or updating the footer requires touching every email template in every service.

else.events is the central layer for all your product emails

All event types, one workflow engine

Auth, billing, onboarding, notifications, security — all email types flow through else.events. One API, one template store, one log.

One template editor for all email types

Update the email footer once — it updates across all templates. Change branding once — it applies everywhere.

One delivery log for all emails

Search by user, event type or date across all email types. Answer "did the customer get the email?" in one place.

One provider configuration

Switch from Postmark to SMTP for all email types in one workspace configuration change — not service by service.

All email types managed in one place

user.password_reset_requested

Auth emails

Password reset, email verification, magic link — all managed in else.events.

invoice.paid

Billing emails

Invoices, receipts, payment failures, plan changes — all from billing events.

user.signed_up

Onboarding emails

Welcome, setup reminder, feature discovery, trial nudge — from user action events.

comment.created

Notification emails

Comments, mentions, assignments, status changes — from product activity events.

security.new_login

Security alerts

New login, password changed, API key created — from security events.

Frequently asked questions

Can else.events replace multiple email providers?
else.events is a workflow layer, not a sending infrastructure provider. It routes emails through your configured provider (Postmark, SMTP, etc.). But it does centralise all email types through a single configuration and log.
What if different teams own different email types?
Workspace members can be scoped to specific template groups in future plans. Currently all members of a workspace can view and edit all templates.
Can I migrate existing email templates into else.events incrementally?
Yes. Start with one email type — for example, billing emails — while keeping others as-is. Migrate additional types as you go.
Does centralising emails create a single point of failure?
else.events is designed for reliability with provider failover on the roadmap. For critical emails, your SMTP configuration can serve as a fallback provider.

All your SaaS emails — one place to manage, debug and ship

Centralise every product email in else.events. One API, one template store, one log.

  • Free during public beta
  • All email types in one workspace
  • One delivery log across all events