# 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. HTML: https://domainsend.app/articles/flaremail-vs-cloudflare-email/ **Keyword:** flaremail vs cloudflare-email **Audience:** someone who wants a small searchable Cloudflare dashboard and is looking at a zero-star repo ## 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. First three domains are free; Pro is $10/month for 12 domains; Agency is $60/month unlimited. 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. ## 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. ## Side by side Same job, different operator. Price on the DomainSend side is the domain plan, not a claim that self-hosting is free. ## 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](/assets/articles/flaremail-message.webp) *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](/assets/articles/flaremail-signup.webp) *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](/onboarding/) and use the [setup guide](/help/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: - [DomainSend vs Mailflare](/articles/flaremail-vs-mailflare/) - [DomainSend vs Agentic Inbox](/articles/flaremail-vs-agentic-inbox/) - [DomainSend vs Quickinbox](/articles/flaremail-vs-quickinbox/) - [DomainSend vs Orange Inbox](/articles/flaremail-vs-orange-inbox/) - [DomainSend vs Email Explorer](/articles/flaremail-vs-email-explorer/) - [DomainSend vs Postern](/articles/flaremail-vs-postern/) - [DomainSend vs Doota](/articles/flaremail-vs-doota/) - [DomainSend vs cf-mail](/articles/flaremail-vs-cf-mail/) - [DomainSend vs Reccado](/articles/flaremail-vs-reccado/) - [DomainSend vs AgentBox](/articles/flaremail-vs-agentbox/) Create an account on [onboarding](/onboarding/), then follow the [setup guide](/help/setup-guide/). The guide’s outside step is an Email Routing rule to the flaremail-api Worker. ## 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. ## Related - [DomainSend vs AgentBox](/articles/flaremail-vs-agentbox/index.md) - [Cloudflare Email Routing Send Email: From Receiving Mail to a Complete Workflow](/articles/cloudflare-email-routing-send-email/index.md) - [How to Use Cloudflare Email Routing as an Inbox Without Rebuilding Email From Scratch](/articles/how-to-use-cloudflare-email-routing-as-an-inbox/index.md) ## Start [Onboarding](https://domainsend.app/onboarding/) · [Pricing](https://domainsend.app/pricing.md) · [Setup guide](https://domainsend.app/help/setup-guide/)