# DomainSend vs Mailflare Mailflare keeps mail in your Cloudflare account. DomainSend runs the Worker, D1, and R2 for you. HTML: https://domainsend.app/articles/flaremail-vs-mailflare/ **Keyword:** flaremail vs mailflare **Audience:** people who want a Cloudflare inbox and are deciding whether to host it ## Short answer DomainSend is a web inbox for Cloudflare-powered email — a hosted inbox, while Mailflare is the self-hosted project you deploy and operate yourself. First three domains are free; Pro is $10/month for 12 domains; Agency is $60/month unlimited. DomainSend vs Mailflare is a hosting choice. Both are Cloudflare inboxes. Mailflare is self-hosted (Docker is also an option), AGPL-3.0, with 4,321 GitHub stars. Mail stays in your D1 and R2. DomainSend is hosted: you create an account, open the app, and connect a domain. DomainSend operates the Worker, D1, and R2. The codebase is not public, so there is no clone-and-deploy path. ## 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. Mailflare 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 Mailflare is actually good at Mailflare’s real strengths are the ones you get by owning the stack. Personal and shared mailboxes, search, folders, stars, snooze, and routing rules are in the product. Calendar and booking pages are there too. Each domain can send through Resend or Amazon SES as well as Cloudflare. Cloudflare Email Sending on that path needs a paid Workers plan. Resend’s free tier is 3,000 emails a month. The trade is operations: you deploy it, you keep it running, and you pay Cloudflare (and whichever sender you attach) yourself. There is no DomainSend subscription on that path, and there is no hosted Mailflare plan in the facts above. ## Which one to pick Pick Mailflare 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 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 cloudflare-email](/articles/flaremail-vs-cloudflare-email/) - [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 **Is Mailflare the same product as DomainSend?** No. Mailflare is a self-hosted inbox you deploy. DomainSend is a hosted inbox. DomainSend operates the Worker, D1, and R2. **Does Mailflare store mail in my Cloudflare account?** Yes. Mail stays in your D1 and R2. That is the point of the self-hosted path. **What does DomainSend cost if I do not want to self-host?** 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 Agentic Inbox](/articles/flaremail-vs-agentic-inbox/index.md) - [DomainSend vs cf-mail](/articles/flaremail-vs-cf-mail/index.md) - [Cloudflare Email Routing IMAP: Does Cloudflare Support IMAP? What to Use Instead](/articles/cloudflare-email-routing-imap/index.md) ## Start [Onboarding](https://domainsend.app/onboarding/) · [Pricing](https://domainsend.app/pricing.md) · [Setup guide](https://domainsend.app/help/setup-guide/)