FlareMail vs AgentBox is a human inbox versus an agent control plane. AgentBox is self-hosted, MIT, with 7 GitHub stars. The control plane is often deployed to Vercel, with mail on your Cloudflare account. It is receive-only: sending and replying are not included. FlareMail is a hosted inbox where send is part of the app.
Short answer: FlareMail is a web inbox for Cloudflare-powered email — a hosted inbox that can send, while AgentBox is a receive-only agent control plane you deploy.
Cloudflare email inbox in your browser. First three domains free. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited.
3 DOMAINS FREE · $10/MO PRO
Hosted inbox or a stack you operate
FlareMail is for people who already run on Cloudflare and do not want to provision the mail stack. You create an account, open the app, and connect a domain. The setup guide says about five minutes. One step sits outside the app: an Email Routing rule to the flaremail-api Worker. FlareMail operates the Worker, D1, and R2.
AgentBox is the self-hosted path in this comparison. You clone it and you keep it running. That can be the right trade when the mail must live in your Cloudflare account, or when a feature below is the reason you are here.
Side by side
Same job, different operator. Price on the FlareMail side is the domain plan, not a claim that self-hosting is free.
| FlareMail | AgentBox | |
|---|---|---|
| Where it runs | Hosted. Create an account and open the app. | Self-hosted. You deploy and operate it. |
| Who operates Worker, D1, and R2 | FlareMail operates the Worker, D1, and R2. | You do. The control plane is often deployed to Vercel. Mail uses your D1 and optional R2. |
| Setup | Connect a domain in the app. The setup guide says about five minutes, with one step outside the app: an Email Routing rule to the flaremail-api Worker. | Self-hosted control plane, often on Vercel, with mail on your Cloudflare account. Email Routing is enabled by hand. A Vercel deploy button is in the README. |
| Inbox | Browser inbox: read, folders, search, compose, attachments, labels, and privacy controls. | Agent inboxes via POST /v1/inboxes and long-poll GET /v1/inboxes/:id/messages?wait=30. Built-in MCP. Multi-domain. D1 plus optional R2. About one Email Routing rule per inbox, and about 200 rules per domain. |
| Send | Send from your domain in the same app. | Receive-only. Sending and replying are not included. |
| Price | First 3 domains free. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited. | No send product to price. You pay Vercel and Cloudflare for what you deploy. 7 GitHub stars, MIT. |
What the FlareMail screen actually is
The inbox list above is the web app from this product, with obviously fake mail so the screenshot does not use a customer account. The sign-in form at app.sendwithflare.com is only the account door. It is not the inbox.
What AgentBox is actually good at
AgentBox is honest about the job. You create inboxes with POST /v1/inboxes and long-poll GET /v1/inboxes/:id/messages?wait=30. MCP is built in. It is multi-domain, with D1 and optional R2. The README says about one Email Routing rule per inbox, and about 200 rules per domain. Email Routing must be enabled by hand in the dashboard. A Vercel deploy button is in the README.
The captured README describes agent-native inboxes and receive-only OTP or verification style mail. That is a strength for agents. It is not a compose window. If the message needs a reply from a person, AgentBox is the wrong tool on purpose, and FlareMail is the hosted place to write it.
Which one to pick
Pick AgentBox when you want the bits in your account and you will operate them. Pick FlareMail when you want the inbox without becoming the person who provisions Worker, D1, and R2.
Start on onboarding and use the setup guide. First three domains are free. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited.
Other FlareMail comparisons
The same hosted-versus-self-host question, for the rest of the field:
- FlareMail vs Mailflare
- FlareMail vs Agentic Inbox
- FlareMail vs Quickinbox
- FlareMail vs Orange Inbox
- FlareMail vs Email Explorer
- FlareMail vs Postern
- FlareMail vs Doota
- FlareMail vs cf-mail
- FlareMail vs Reccado
- FlareMail vs cloudflare-email
Create an account on onboarding, then follow the setup guide. The guide’s outside step is an Email Routing rule to the flaremail-api Worker.
FlareMail is free for your first three domains. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited.
3 DOMAINS FREE · $10/MO PRO
Sources and context
- Cloudflare Email Service routes incoming emails to custom addresses, Workers, or external destinations.
- Cloudflare routing rules can send mail to an email address, send it to a Worker, or drop it.
- Cloudflare Workers can send email through send_email bindings.
- Cloudflare documents sending and routing as related but separate email setup paths.
- Cloudflare Email Routing can route mail to Workers for custom handling.
FAQ
Can AgentBox reply to mail?
No. It is receive-only. Sending and replying are not included.
How does an agent read an AgentBox inbox?
Create an inbox with POST /v1/inboxes and long-poll GET /v1/inboxes/:id/messages?wait=30. MCP is built in.
What does FlareMail cost?
First three domains are free. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited. Send is included in the hosted app.
Three domains free. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited.
3 DOMAINS FREE · $10/MO PRO