One platform. Built for four kinds of outbound team.
Cold email shops, agencies managing many clients, SaaS companies sending transactional + lifecycle at scale, and platform teams who want to own their infrastructure.
- Providers supported
- 15+Providers supported
- Bring your own
- BYOPBring your own
- Per workspace
- RBACPer workspace
- First-class
- APIFirst-class
Cold email at volume, without burning one domain
Single-provider cold email melts reputation. Quota limits, IP concentration, and reputation swings force teams to manually rotate — or to accept flat delivery.
See Cold Email page- Rotate sends across providers, IP pools, and sending domains automatically
- Per-list and per-domain suppression to isolate cold lists from transactional
- Quota-aware routing so sends queue instead of fail when a provider caps out
- Multi-provider reporting: see which provider, domain, and pool is actually working
One platform, many clients, zero bleed
Agencies juggle logins, duplicate templates, and share provider accounts across clients. When one client triggers a complaint spike, every other client pays for it.
See Agencies page- Workspaces per client, with isolated lists, domains, and sending credentials
- Custom roles so client contacts see what they should and nothing else
- Per-workspace billing, usage caps, and audit logs
- Re-usable template and automation libraries across clients
Transactional + lifecycle email without vendor lock-in
Most SaaS teams send through one ESP for speed, then get stuck when pricing changes, deliverability slips, or a region demands a different provider.
See API page- Swap providers without rewriting application code — the API stays the same
- Run lifecycle automations, campaigns, and transactional sends side-by-side
- Route by message type: transactional on one pool, marketing on another
- Observe everything via webhooks, audit logs, and per-provider analytics
Bring your own providers. Keep control of the pipeline
Platform engineers want multi-provider strategy, failover, and deep observability — but don't want to build an orchestration layer from scratch.
See Email Routing- Attach AWS SES, SendGrid, Mailgun, Postmark, SMTP, and more via BYOP
- Priority-based routing with automatic failover on provider errors
- API-first: every UI action has an API and webhook equivalent
- Deep audit trails, custom roles, SSO, and domain-level controls
Start on your stack. We fit around it.
Plug in the providers you already pay for, give the team the controls they need, and ship outbound the way your business actually works.