Autopilot Unveils Self-Hosted Email Infrastructure for AI Agents

Autopilot has released self-hosted email infrastructure for AI agents on GitHub. It offers storage adapters for PostgreSQL, MongoDB, SQLite and Cloudflare D1, and delivery adapters for AWS SES and SMTP. Users can choose S3, R2 and other options for attachments. The project says it is REST API- and wire-compatible with AgentMail, and that users can use the official SDK by changing the baseUrl of the endpoint.

Autopilot touts a setup that lets users choose their database and email delivery route, along with compatibility with the AgentMail SDK. It could be an option for developers who want to integrate email capabilities into existing agent code while managing storage themselves. However, the project's claim of “unlimited” resources is its own representation; operational limits and total costs need to be checked separately.

The project's distinguishing feature is that it does not provide email capabilities as a single hosted service. Instead, it separates storage, delivery and attachment management into adapters that users can incorporate into their own environments. Storage options range from PostgreSQL to SQLite and Cloudflare D1; delivery options include SES and SMTP, and attachment storage can use S3, R2 and other services. The design therefore centers not only on the “unlimited” label but also on letting users choose where data is stored and how email is delivered. The claim of wire compatibility with the AgentMail SDK offers a migration path that could allow users to change the endpoint while keeping existing client code. In the project's example, users replace the baseUrl and leave API calls unchanged. However, the compatibility claim comes from the project itself, and the published material does not include test results showing that all features and operating conditions work equivalently. The project also provides guidance on data exports and DNS changes as part of migration, indicating that steps beyond code changes may be involved. The pricing comparison pits a hosted service listed at $20 per month for 10 inboxes, 10,000 emails per month and 10GB against Autopilot, which is labeled unlimited. But “unlimited” is the project's description, not a guarantee of actual limits or operating conditions. The example of $0.10 per 1,000 emails for SES concerns delivery costs and does not compare total costs, including storage, server operation and monitoring. Any decision to self-host should weigh the benefits of keeping data under the user's own control against the burden of configuration and maintenance. When AI agents are given email sending and receiving or thread management capabilities, this is part of the surrounding communications and business infrastructure, not the model or the robot itself. The material does not directly describe an application to physical AI, so no connection to robot control or safety can be inferred. Points to check next include delivery rates in actual operation, specific constraints on receiving and processing email, recovery from outages, authentication and access controls, and the conditions attached to “unlimited.” The information provided is not enough to assess performance or operational track record on these points.

In addition to the required core SDK, the project offers a REST server and CLI for standalone operation. In the example configuration, data is stored in Postgres, SES is used for delivery, and users set a default domain before creating inboxes and sending email. The documentation also covers deployment with Docker and Cloudflare, webhooks for inbound SES and sending events, and migration from AgentMail. The project's comparison table lists AgentMail at $20 per month, with 10 inboxes, 10 custom domains, 10,000 emails per month and 10GB of storage. Autopilot, by contrast, lists these as “unlimited” and gives an SES pricing example of $0.10 per 1,000 emails. The project also promotes a setup that stores data in the user's own database.