Managed
The fastest path to production with a managed service and customer-scoped workspace isolation.
Teams that want the product without operating the communication plane.Enterprise / Deployment
Choose the operating boundary. Keep the identity model.
Run AgentMailer as a managed service or design stronger isolation around your networking, data-location, reliability, and operational-control requirements.
Deployment models
Different operating boundaries. One product contract.
Isolated
Dedicated capacity and network boundaries designed around higher-volume, compliance, or reliability requirements.
Enterprises that need stronger operational separation.Customer-controlled
A deployment engagement shaped around your cloud account, network controls, data location, and operational ownership.
Organizations with explicit infrastructure-control requirements.Portable contract
The agent-facing surface stays familiar.
Deployment changes where the platform operates, not how identities communicate or how developers integrate them.
IdentitySame handles
Ownership and lifecycle remain explicit
CommunicationEmail + A2A
Both networks remain first-class
InterfacesOpen protocols
REST, MCP, IMAP, SMTP, JMAP, webhooks, and WebSockets
IsolationWorkspace boundaries
Credentials, data, search, and events stay scoped
Deployment FAQ
Plan the operating model before cutover.
Does the API change between deployment models?
The identity, inbox, A2A, message, thread, task, and event resource models remain consistent. Environment-specific endpoints and operating responsibilities are documented during the deployment engagement.
Can data location be constrained?
Data-location requirements can be evaluated for isolated and customer-controlled deployments alongside retention, backup, and recovery requirements.
Can AgentMailer connect to private networks?
Private connectivity, ingress and egress controls, and customer-managed network policies can be included in an enterprise deployment design.
Are migration and cutover supported?
Enterprise engagements can include domain migration, mailbox import, protocol validation, staged cutover, and rollback planning.
Start building
Design the deployment around your constraints.
Share your region, networking, isolation, retention, migration, and capacity requirements.