Documentation / the starting point
Understand your new home for email.
The essentials, from your everyday email app to the assistant helping you build your business. Start with a plain-English prompt, or explore the architecture below.
Find your starting pointStart with the foundations.
People and agents
Understand who owns a mailbox and who is allowed to use it.
Read the overviewYour favorite email app
See how IMAP and SMTP fit into the MailSwarm architecture.
Read the overviewGive an agent a mailbox
Learn the boundaries around API, CLI, and MCP access.
Read the overviewBring your own identity
Keep ownership of your domain and its mail routing.
Read the overview01 / identities
Distinct identities. One mail foundation.
A workspace contains authorized mailbox identities. A human and an agent can each have their own identity, with access granted for that identity. An agent does not automatically inherit access to everyone else’s mail.
PostgreSQL and S3 are the source of truth for mailboxes and message content. Amazon SES is the internet delivery edge. Standard mail protocols and agent interfaces connect to the same underlying mail system.
02 / connection
Keep the client you know.
IMAP gives a mail client access to your mailbox. SMTP handles submission of outgoing mail. This is the foundation for using MailSwarm with apps such as Apple Mail and Thunderbird.
Connection settings and step-by-step setup instructions will be published with launch availability. The example below illustrates the settings you will need; these are reserved example hostnames, not live MailSwarm servers.
# Example configuration — not a live endpoint
IMAP host: imap.example.com
SMTP host: smtp.example.com
Identity: you@yourdomain.example
Credential: provided by your workspace administrator
# Use the confirmed ports and TLS settings from your
# workspace setup guide when connection access opens.03 / access
Permission comes before automation.
An authorized workspace owner or delegated administrator creates and manages mailbox credentials. API, CLI, and MCP access is limited to the mailbox identities and operations granted to that principal.
Agents cannot approve their own DNS changes, billing actions, permission expansion, exports, or deletion requests. The getting-started guide includes copy-ready business prompts, owner setup requirements, and first checks for authorized sessions.
Read the getting-started guide04 / domains
Your domain stays yours.
MailSwarm is built for a domain you control. Domain verification and mail routing need deliberate owner decisions. MailSwarm never automatically replaces your root MX records.
Domain setup and migration guides are coming soon. Wait for the confirmed setup instructions before changing the records used by an existing mail service.
Know where the boundaries are.
Read the principles behind workspace isolation, scoped access, and owner control.
Explore security