Aeion Notifications + Email Providers
Aeion Notifications is the orchestrator; the providers are the bare delivery relays. SendGrid and Resend send natively via their HTTP APIs; Mailgun, Postmark, AWS SES, and any other relay connect through generic SMTP. Pick one active provider per tenant and swap it in Company Settings without a code change — automatic retry with exponential backoff covers transient failures, and delivery-status webhooks from SendGrid, Mailgun, Postmark, and SES all feed the same `notification.email.*` event stream regardless of which provider sent the bytes.
Supported Email Providers
`
Provider Configuration + Retry Behavior
```typescript
Per-Domain Authentication Setup
```bash
Bounce + Complaint Event Tracking
```typescript
FAQ
Yes. Per-tenant credentials. Aeion never has cross-tenant access.
Yes. Per-tenant authenticated domain. Per-tenant DKIM keys.
No cross-provider failover exists — retries target the same configured provider, with exponential backoff (default 3 attempts: 1s, 2s, 4s delays via `EMAIL_RETRY_ATTEMPTS`/`EMAIL_RETRY_DELAY_MS`). If the configured provider is down, sends fail after retries exhaust until you reconfigure.
SendGrid's Categories are exposed via Aeion's `tags` option on a send. Provider-specific features beyond that (Mailgun tagging, etc.) aren't wired up since those providers connect via generic SMTP, not a native API adapter.
Aeion doesn't maintain its own cross-provider suppression list. Recipient opt-out is a per-user, per-channel preference (a master toggle for the "email" channel), separate from any bounce/complaint-driven suppression your provider manages on its own side.
No — the webhook routes parse whatever payload is POSTed. There's no HMAC/signature verification today, so treat the webhook URL itself as the access control (don't publish it) rather than relying on provider request-signing.
Each tenant supplies its own provider API key or SMTP credentials via Company Settings — isolation comes from tenants using separate provider accounts, not from Aeion provisioning sub-accounts on a shared one.
That's managed on the provider's side (SendGrid/Mailgun/etc. dashboards) — Aeion doesn't schedule or monitor IP warm-up.
No automatic per-region routing — a tenant configures one active provider. If you need EU data residency, choose a provider with EU infrastructure (e.g. Mailgun EU) as that tenant's configured provider.
Cost follows whichever single provider you pick. SES is typically cheapest per email at volume; SendGrid/Postmark cost more but prioritize deliverability and native-API features. Since only one provider is active per tenant, weigh cost vs. deliverability up front, or swap providers via Company Settings if volume patterns change.
Yes. Per-tenant SMTP credentials, configurable TLS certificate validation, and optional connection pooling.