Does else.events support white-label email branding?

Yes. Each tenant can have its own brand variables — logo, primary colour, sender name, reply-to address. Templates reference these variables at render time.

Can different tenants use different email providers?

Yes. A rule can specify which provider to use based on tenant ID or any payload field. Enterprise tenants can bring their own SMTP.

Is this different from white-label email?

Multi-tenant and white-label describe the same technical need from different audiences. else.events supports both patterns.

One event, different brands — multi-tenant email for SaaS

Route emails per tenant, apply tenant-specific brand variables and deliver through tenant-specific providers — all from a single event-driven workflow.

Build your multi-tenant email workflow Explore rule-based routing

Multi-tenant email is harder than it looks

Tenant-specific branding requires custom code

Injecting the right logo, colour and sender name per tenant means per-tenant switch statements or database lookups in your email-sending service.

Template variations multiply your maintenance burden

Maintaining slightly different templates per tenant — or per plan within a tenant — grows into a combinatorial nightmare.

Provider routing per tenant is fragile

Enterprise tenants often want emails from their own SMTP. Routing to the right provider per tenant requires custom middleware.

else.events handles multi-tenant routing by rules

Tenant ID in the event payload

Include a tenant_id field in your event payload. Rules match on it to select the right template and provider.

Brand variables per tenant

Define logo, primary colour, sender name and reply-to per tenant. Templates inherit them at render time — no code change.

Provider routing per tenant

Route tenant A to Postmark, tenant B to their own SMTP. Configured in rules, not in application code.

One integration, every tenant

Your app sends the same event shape for every tenant. else.events resolves the brand, template and provider.

// multi-tenant event

Same event, different output per tenant

{
  "type": "user.signed_up",
  "tenant_id": "acme-corp",
  "user": { "email": "newuser@acme.com", "name": "Sarah" },
  "data": {
    "plan": "Pro",
    "workspace_name": "Acme Corp"
  }
}

else.events matches tenant_id = acme-corp, applies Acme Corp brand variables (logo, colours, sender name) and delivers through the tenant configured provider.

Frequently asked questions

Does else.events support white-label email branding?: Yes. Each tenant can have its own brand variables — logo, primary colour, sender name, reply-to address. Templates reference these variables at render time.
How does tenant routing work?: Include a tenant_id in your event payload. Rules match on it to select the right template and provider. No code change required when adding a new tenant.
Can different tenants use different email providers?: Yes. A rule can specify which provider to use based on tenant ID or any payload field. Enterprise tenants can bring their own SMTP.
Is this different from white-label email?: Multi-tenant and white-label describe the same technical need from different audiences. else.events supports both patterns.

Multi-tenant email without the custom middleware

One event shape for every tenant. Rules and brand variables handle the rest.

Free during public beta
Brand variables per tenant
Provider routing by rule