STARTUP MAIL / FIELD GUIDE

Documentation

Set up a company inbox for people, products, and agents—without adopting the rest of an office suite.

Startup Mail gives an address on your own domain a web inbox, optional forwarding, team access, and a developer interface. Incoming and outgoing messages stay in the same threads no matter which interface handles them.

Choose a path

Set up an inbox

Connect a domain and receive your first message.

Build with the API

Read, send, reply, and react to mail from code.

Forward mail

Keep Gmail or Outlook as your daily inbox.

Connect an agent

Expose scoped mailbox tools over MCP.

The product model

Everything starts with a workspace. A workspace owns domains, mailboxes, teammates, API keys, webhooks, billing, and usage. A verified domain can have one or more mailboxes such as hello@tiny.studio or founder@tiny.studio.

Mailboxes are either shared with the workspace or private to an owner and explicitly invited people. Humans use the web inbox or forwarding. Software uses the REST API, TypeScript SDK, signed webhooks, or MCP. All of those paths respect the same mailbox permissions.

What Startup Mail is for

Startup Mail is for direct conversations and transactional email people requested or reasonably expect: support replies, receipts, account alerts, booking confirmations, and agent-assisted workflows.

It is not a newsletter, campaign, drip sequence, or cold-outreach product. Read the acceptable use policy before sending from a new workspace.

Product boundaries

No calendar, documents, meetings, or team chat.
No IMAP, POP, Exchange, or general SMTP account.
Forwarding does not synchronize folders, read state, or labels.
No marketing lists, audience management, or bulk campaigns.
DNS changes can take time to propagate outside Startup Mail.