Comparisons · Cloudflare email guide

DomainSend vs cloudflare-email

cloudflare-email is one Worker with no build step. DomainSend is hosted, so you do not share one dashboard password for the whole inbox.

DomainSend inbox list in the web app, showing fictional sample mail

DomainSend vs cloudflare-email is a hosted product versus a tiny self-hosted Worker. The repo is MIT, with 0 GitHub stars. It is one Worker, D1 plus R2, Hono, and no build step. You can run it multi-domain or catch-all. DomainSend is the hosted inbox: account, app, domain. DomainSend operates the Worker, D1, and R2.

Short answer: DomainSend is a web inbox for Cloudflare-powered email — a hosted inbox with its own accounts, while cloudflare-email is a single shared-password Worker you deploy.

Three domains free

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.

Create free account
Lo-fi corkboard illustration with EDGE_ROUTER.EXE pinned above Email for Cloudflare domains

Hosted inbox or a stack you operate

DomainSend 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. DomainSend operates the Worker, D1, and R2.

cloudflare-email 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.

DomainSend inbox list with fictional mail for hello@paperlantern.example
The DomainSend inbox list in the web app. Messages are fictional sample mail, not a customer inbox and not the marketing homepage.

Side by side

Same job, different operator. Price on the DomainSend side is the domain plan, not a claim that self-hosting is free.

DomainSendcloudflare-email
Where it runsHosted. Create an account and open the app.Self-hosted. You deploy and operate it.
Who operates Worker, D1, and R2DomainSend operates the Worker, D1, and R2.You do.
SetupConnect 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.One Worker, D1, R2, and Hono, with no build step. One shared dashboard password.
InboxBrowser inbox: read, folders, search, compose, attachments, labels, and privacy controls.Searchable dashboard. Tap-to-copy OTP when AI classification is on. Multi-domain or catch-all.
SendSend from your domain in the same app.Reply and forward only if Email Service is configured. AI calls leave Cloudflare only if an OpenAI or MiniMax key is set.
PriceFirst 3 domains free. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited.No product price. You pay for the Worker you deploy. 0 GitHub stars, MIT.
GitHub README for MalikZu/cloudflare-email
The public GitHub README for MalikZu/cloudflare-email.

What the DomainSend 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.

DomainSend web app with a fictional message open from Northwind Booth
A message open in the DomainSend web app. The mail is fictional sample data (paperlantern.example), captured from this repo so the screenshot is the real UI.
DomainSend sign-in form at app.sendwithflare.com
The public sign-in form at app.sendwithflare.com. Use it to create an account. It is not the inbox.

What cloudflare-email is actually good at

The small surface is the point. There is a searchable dashboard. When AI classification is on, OTP codes are tap-to-copy. Reply and forward work only if Email Service is configured. Login is one shared dashboard password. AI calls leave Cloudflare only if an OpenAI or MiniMax key is set.

That is a reasonable personal dashboard if you want no build step and you accept one shared password. It is not a hosted multi-user inbox. DomainSend’s accounts are the product’s, and send is part of the app rather than an Email Service switch you wire yourself.

Which one to pick

Pick cloudflare-email when you want the bits in your account and you will operate them. Pick DomainSend 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 DomainSend comparisons

The same hosted-versus-self-host question, for the rest of the field:

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.

Ready for a real Cloudflare inbox?

DomainSend is free for your first three domains. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited.

Create free account
Lo-fi corkboard illustration with EDGE_ROUTER.EXE pinned above Email for Cloudflare domains

Sources and context

FAQ

Does cloudflare-email have separate user accounts?

The documented login is one shared dashboard password.

Can it reply if Email Service is off?

Reply and forward work only if Email Service is configured.

What does DomainSend cost?

First three domains are free. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited.

Three domains free. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited.

Create free account