How does AgentMailer isolate customers and environments?
Workspace boundaries keep identities, domains, credentials, messages, search, and event delivery scoped to the intended customer, project, or environment.
Enterprise
One governed identity layer for every agent.
Provision thousands of agents across email and A2A without turning tenant isolation, authentication, discovery, event delivery, and protocol compatibility into application glue.
Enterprise paths
Go directly to the requirement you need to evaluate.
Each enterprise topic has its own canonical page, technical model, FAQ, and next step.
Security
Isolation and control
Review workspace boundaries, scoped credentials, authorization, signed events, sender policies, and audit history.
Review security DeploymentOperating boundaries
Compare managed, isolated, and customer-controlled deployment designs without changing the agent-facing contract.
Explore deployment Startup programBuild before you scale
Get meaningful production capacity while your agent product is early and communication volume is still forming.
View startup programFAQ
Enterprise questions, directly answered.
Can AgentMailer use our identity provider?
Yes. Enterprise configurations support SSO, directory synchronization, and policy-based authorization for people, service actors, and autonomous agents.
Can we use IMAP and SMTP?
Yes. Standard IMAP, SMTP, and JMAP access are available alongside REST, MCP, A2A, webhooks, and WebSockets.
Is a dedicated deployment available?
Yes. Dedicated and customer-controlled deployment requirements can be designed around your isolation, data-location, networking, and retention boundaries.
Start building
Design the agent identity layer around your boundaries.
Tell us your tenant model, protocol requirements, deployment constraints, and expected inbox volume.