Email API for agencies — per-client domains, per-domain keys, one dashboard
Agencies typically run email infrastructure for a portfolio of clients — different domains, different billing relationships, different audit postures. Flowmails gives every client their own domain-scoped configuration inside one platform: each client's domains, route tables and API keys are separate, and the agency's dashboard brokers the connection without ever holding a client's provider credential. Per-domain API keys are scoped to a single domain, so a leaked key can't pivot to another client. Reviews get easier because the data boundary is a domain boundary enforced by `domain_id`, and a client can be moved off the platform with its own history intact.
What hurts today
The agencies and studios pain points
Hosted ESPs give you a single multi-tenant account — cross-tenant pivots are a real risk
Per-domain setup is the same per-client regardless of ESP, but data auditability isn't
Per-tenant API key isolation is missing from most hosted transactional platforms
How Flowmails answers
What you get instead
Per-domain scoping — one client's key cannot touch another client's domain
Per-domain API keys can't pivot across clients
White-label option on Enterprise drops the Flowmails brand from the dashboard
FAQ
Common questions from agencies and studios
Other personas