Compare Startup Mail and Cloudflare Email Service for custom-domain mail, Workers, agents, forwarding, persistent inboxes, APIs, SMTP, and pricing.
Startup Mail publishes this comparison. Check our product docs and the linked official sources. We say when the other product is the better fit.
Loading article…
Startup Mail and Cloudflare Email Service can both send and receive custom-domain email. They give you different starting points.
Choose Startup Mail when you want a persistent mailbox that people and software can use at once. Choose Cloudflare when email belongs inside an application you are building, especially one that already runs on Workers or the Agents SDK.
Startup Mail is a hosted mailbox product. It stores messages and attachments, groups replies into threads, and provides a web inbox. People can work in that inbox or receive forwarded mail in Gmail and Outlook. Software can use the same mailbox through REST, SDKs, webhooks, or MCP.
Cloudflare Email Service is a set of email infrastructure primitives. Email Routing forwards incoming mail to a verified address or passes it to a Worker's email() handler. Email Sending sends transactional mail through a Workers binding, REST API, or authenticated SMTP. Cloudflare's Agents SDK adds native methods for agents to receive and reply to email.
Cloudflare gives developers more control. Startup Mail gives them less mailbox infrastructure to build.
| Capability | Startup Mail | Cloudflare Email Service |
|---|---|---|
| Custom-domain sending and receiving | Yes | Yes |
| Persistent mailbox and threads | Built in | You build and operate the storage |
| Human web inbox | Yes | No built-in working inbox |
| Shared and private mailboxes | Yes | Not a built-in mailbox model |
| Forwarding | Gmail and Outlook with a protected reply path | Verified destination addresses |
| Programmatic access to received mail | Signed webhooks, then REST, SDKs, or MCP | Workers email() handler |
| Outbound code path | REST, SDKs, and MCP | Workers binding, REST, official SDKs, SMTP, and MCP |
| SMTP submission | No | Yes, over implicit TLS on port 465 |
| Native Cloudflare Workers binding | No | Yes |
| Agents SDK integration | Use REST, SDKs, webhooks, or MCP | Native onEmail(), sendEmail(), and replyToEmail() |
| Access controls | Organization, tenant, or mailbox scoped | Scoped tokens and binding restrictions; mailbox authorization is your work |
| Drafts and scheduled sends | Built in | Build with application and Cloudflare platform services |
| Approval building blocks | Drafts, policies, and web review | Build them |
| Marketing campaigns | No | No; Email Service is for transactional email |
Cloudflare details come from its Email Service overview, pricing page, Email Routing Workers API, SMTP reference, and Agents SDK email guide. We checked them on 25 August 2026.
Startup Mail suits a company that needs addresses such as founder@, hello@, or support@ without building an inbox around them.
An incoming message is stored as part of a mailbox thread. A teammate can read it in the web inbox. A founder can get a forwarded copy in Gmail or Outlook. An agent can fetch the thread or draft a reply. The mailbox remains the shared record.
Startup Mail also supplies the parts that make a mailbox usable over time:
This is useful when a human may need to inspect, edit, approve, or take over a conversation. You do not need to design a database schema, build an inbox interface, or recreate mailbox permissions.
Startup Mail is the better fit for:
Cloudflare is stronger when you want to decide what every incoming message should do.
Email Routing can forward mail to a verified address. It can also invoke a Worker. The Worker receives the envelope sender, recipient, headers, and raw MIME stream. Your code can forward, reply, reject, parse, or store the message.
That model works well for routing rules and event-driven systems. A Worker might turn an email into a support ticket, reject an unwanted sender, place an attachment in R2, or send structured data to another service.
Cloudflare's email storage example uses KV and Queues. Its wider platform also offers D1, R2, and Durable Objects. These services make a persistent inbox possible, but you own the schema, threading, access rules, retention, search, interface, and failure handling.
Choose Cloudflare for:
Cloudflare is the better choice for these jobs. Its Workers binding avoids a separate HTTP API call, and its low sending price is attractive for application email.
Cloudflare Email Sending supports three main interfaces.
Workers can call a native send_email binding. Applications on other platforms can use the REST API with a Cloudflare API token. Existing tools can submit mail through authenticated SMTP on port 465.
Cloudflare also provides official Node, Python, and Go SDKs for its REST API. Its Cloudflare API MCP server can find and invoke Cloudflare API endpoints, including Email Service. These options suit Workers, conventional backends, and coding agents.
Startup Mail does not support SMTP or a native Workers binding. It uses REST, its TypeScript SDK, a Python source package, webhooks, and mailbox-focused MCP tools.
If an existing application can only speak SMTP, Cloudflare wins. If the application needs to list stored threads, read mailbox history, create a draft, or hand work to a person, Startup Mail exposes those mailbox operations directly.
Cloudflare's Agents SDK treats email as a native communication channel.
An Agent class can implement onEmail() for incoming messages. It can call sendEmail() or replyToEmail() for outbound mail. Routing helpers can map an address or a signed reply address to the right Durable Object instance.
This is a good fit for an agent that already runs on Cloudflare and owns its workflow. The agent can keep state in a Durable Object and use other Cloudflare services without crossing platforms.
Startup Mail takes a service-based approach. An agent calls a mailbox API or MCP server and receives signed webhook events. It can use a mailbox-scoped key so one agent cannot read another mailbox. Drafts, schedules, and recipient policies are already part of the mail system.
Choose Cloudflare when you want email woven into an Agents SDK application. Choose Startup Mail when you want the agent to use a mailbox that a person can also open and control.
Cloudflare Email Routing can send hello@example.com to a verified Gmail or Outlook address. Inbound routing is available on Free and Paid plans.
This solves a common need: receive mail at a custom address without paying for another hosted inbox. It does not create a stored mailbox with folders, shared state, private grants, drafts, or a working inbox. If you route to a Worker, the Worker must do something with the message. Cloudflare does not retain it as a user mailbox for later work.
Startup Mail stores the original before it forwards a copy. A signed, expiring reply address can route the person's response back through the right Startup Mail mailbox and thread.
Choose Cloudflare's free routing when forwarding is enough. Choose Startup Mail when the custom address must remain a durable system of record.
Cloudflare Email Routing is available on Workers Free and Workers Paid. Cloudflare lists inbound routing as unlimited, though a Worker that handles a message still uses normal Workers resources.
Email Sending is in public beta. Sending to arbitrary recipients requires Workers Paid, which has a $5 monthly minimum. The Email Service price includes 3,000 outbound emails per account each month, then costs $0.35 per 1,000. Sending to verified destination addresses is free on all plans and does not use the quota.
Email Service requires the domain to use Cloudflare's authoritative DNS. New sending accounts begin with an adaptive daily quota that can rise with safe use. A normal send is limited to 5 MiB and 50 combined recipients across to, cc, and bcc.
Startup Mail costs $12 per year, billed annually, for 1,000 email events each month. An incoming delivery, each outbound recipient, and each forwarded copy count as events.
The cheaper service depends on the job.
Cloudflare has the lower unit price for transactional sending, especially if you already pay for Workers. Free inbound routing is hard to beat when you only need forwarding. Startup Mail includes the hosted mailbox, web interface, human permissions, storage workflow, and agent controls in its price.
Do not compare only the number beside “email.” If you need a mailbox, include the time and platform usage needed to build and run that layer.
Yes.
A Worker can send application notifications through Cloudflare while Startup Mail handles founder@ and support@. A Cloudflare Agent can also call Startup Mail's REST API when it needs a persistent mailbox and human review.
This split keeps machine notifications away from company correspondence. It also adds another provider, another set of credentials, and another place to inspect delivery problems.
Use both when the workloads are genuinely different. Do not add the second system merely to save a small amount on low-volume mail.
Choose Startup Mail if you want a finished custom-domain mailbox for people, agents, or both.
Choose Cloudflare Email Service if you want email infrastructure inside an application and are ready to build the state and interface around it.
For forwarding or transactional email from Workers, Cloudflare is often the better choice. For persistent conversations, a human web inbox, shared access, and agent approval, Startup Mail is the clearer fit.
For some workloads. Both can send and receive custom-domain email. Startup Mail replaces the mailbox layer, while Cloudflare supplies routing and sending primitives for an application.
It does not provide a built-in web inbox for everyday mail. Email Routing can forward an incoming message or send it to a Worker. You can build storage and an interface with other Cloudflare services.
Yes. An Email Routing rule can invoke a Worker's email() handler. The handler can inspect the raw message, forward it, reply, reject it, parse it, or save it elsewhere.
Yes. Email Sending supports authenticated SMTP over implicit TLS on port 465. It also supports a Workers binding and REST API. Startup Mail does not offer SMTP.
Cloudflare is better when the agent runs on the Agents SDK and you want to build the email workflow yourself. Startup Mail is better when the agent needs a persistent mailbox, limited mailbox credentials, drafts, policies, and a human web inbox.
Sending to verified destination addresses is free. Sending to arbitrary recipients requires Workers Paid. The current allowance is 3,000 outbound emails per month, followed by usage charges. Email Sending remains in public beta.