Give each customer, brand or environment its own keys, domains and reporting, without running your own mail servers.
Multi-tenant email for SaaS with an agent-ready API and AI support triage
One tenant sends spam and affects everyone
Per-workspace limits and suppression stop a single sender from hurting the rest.
Customers want their own sending domain
Domain onboarding and verification flows work through the API.
Email changes ship with every release
Templates with versions let product and support update content safely.
Send invites triggered by a teammate, with delivery events returned to your app so the inviter sees whether the message bounced and can correct the address.
Notify admins when a threshold is crossed, using priority sending so alerts are not queued behind digests, and record delivery for your audit trail. Alerts remain auditable.
Run weekly summaries per workspace and user, throttled so a large tenant's digest does not use capacity that smaller tenants need at the same moment.
Let customers verify their own domain through an onboarding flow and send under their brand, with SPF and DKIM checks completed before first use. Unverified domains stay blocked.
Enter a user's email and ask why an invite did not arrive. The copilot reads the message log and summarises the delivery path. It cannot resend or edit anything without staff approval.
Spot workspaces whose bounce or complaint patterns drift from normal and surface them for review. Your team decides whether to warn, throttle or leave the tenant alone.
An MCP-compatible surface lets approved internal agents provision workspaces or check domain status using scoped keys. High-impact actions can require a human approval step. Every call is logged.
Draft translated or reworded versions of product emails for review. Product owners edit and approve each version before it goes live in a versioned template.
AI features are assistive and advisory, so your engineering and support teams review suggestions and keep control of tenant, template and sending decisions. [Confirm which AI features are available at launch.]
Separate keys, limits and reports per customer so one noisy sender cannot hurt others and you can see usage clearly.
Never send as a customer domain until SPF and DKIM pass. Block unverified domains at the API to protect shared reputation.
Keep product emails in versioned templates so support and product can update copy safely and roll back if a change causes problems.
Use webhooks to show delivered, bounced or deferred next to the action, which cuts support tickets about missing email.
Apply default sending caps and raise them on request, so a compromised account cannot send a large volume before anyone notices.
Use an email API with a workspace or sub-account per tenant, each with its own keys, limits and reporting. Authenticate sending domains, route events back through webhooks, and apply per-tenant suppression so one customer's bad data does not affect others.
Yes, with a domain onboarding flow: the customer adds DNS records, you verify SPF and DKIM, and only then enable sending. The API can automate this, so your product guides each customer through setup without manual support. [Confirm domain onboarding endpoints.]
Isolate tenants with separate workspaces, apply sending limits, suppress bounces and complaints automatically, and monitor each tenant's rates. Move high-risk or high-volume tenants to their own IP pool if their behaviour starts to affect others. Review limits as each tenant grows.
Store templates outside application code with versions, variables and a review step. That lets product and support edit content without a deploy, while engineers keep control of the data passed in and can roll back a bad change. Tag each release so changes are traceable.
Subscribe to webhook events and store delivered, bounced and deferred status against the related record in your database. Your interface can then show a status badge or a resend prompt without ever reading a mailbox. This also cuts repetitive support tickets noticeably.
Most SaaS teams use the HTTP API for application sends because it supports metadata, idempotency and richer errors. SMTP is useful for legacy systems, plugins and third-party tools. Both can run in the same workspace. Many teams run both at once without conflict.
They can, through an MCP-compatible interface using scoped keys. You decide which actions agents may take, such as read-only status checks versus drafting sends, and can require human approval for anything sensitive. [Confirm which AI features are available at launch.]
A copilot can read the message log for a user and explain the delivery path in plain language, such as a bounce reason or a deferral. Staff review the summary and decide any follow-up. [Confirm which AI features are available at launch.]
[Add a customer quote or result from a SaaS customer]
[Name, title, company]Tell us about your volume and setup and we will walk you through the right configuration.
Create an account, add your domain and send your first email.