Skip to content

Provision and govern email for every client's agents - from one place

Run agents for a roster of clients? Give each one its own real mailbox, control who can do what, and hand the right view to the right client - without standing up email infrastructure per account. Sairaph Mail runs the whole fleet under one tenant, governed by design.

Shell

A scoped key per agent - least privilege by default.

Per-client email doesn't scale by hand

Doing this yourself means a domain, DNS, and DKIM per client, a relay that won't get the whole roster blocklisted, an inbox server to read each agent's replies, and a secrets store for it all - multiplied by every client you onboard. And the moment you have more than one client, governance is the real problem: you can't have one all-powerful key that touches every mailbox; you need to scope and revoke access per agent, keep one client's mail isolated from another's, and hand a clean view to a client without exposing the rest.

How it works

  1. 01One tenant for the agency

    You hold the account. Mailboxes, domains, and billing all live under it.

  2. 02Provision per client with the management key

    Use the dashboard-issued sm_mgmt_ key to create mailboxes and provision across the fleet as you onboard each client. It's never callable by a connected agent.

    Shell
  3. 03Scope a key per agent

    Each agent gets a per-inbox key with the narrowest role it needs and an optional expiry. Revoke it the moment a client offboards.

  4. 04Isolate and hand off

    Per-customer encryption and per-mailbox suppression keep clients separate; the dashboard gives each client a clean view of just their own mail.

Scope, send, read - under one tenant

Issue a scoped key per agent, then each mailbox sends and reads over the same REST contract (or MCP).

Scope a key

The sm_mgmt_ key is dashboard-issued and never agent-callable.

Governance built into the platform

Every plan ships the controls a fleet needs - not gated to enterprise.

  • Scoped, expiring API keys
  • Per-customer encryption
  • EU data residency
  • Managed domain, DKIM & deliverability
  • Native MCP server
  • REST API
  • Optional two-factor authentication

Frequently asked questions

  • A mailbox per customer (multi-tenant)

    The per-customer isolation pattern in depth.

    Learn more
  • Provision an agent fleet

    Stand up email for many agents under one tenant.

    Learn more
  • For AI agent developers

    The contract a machine can act on safely.

    Learn more

Run the whole fleet from one place

Provision, scope, and govern email for every client's agents under one tenant - with a dashboard you can hand to clients.

EU data residencyPer-customer encryptionNative MCP