# FlareMail vs Reccado Reccado is an edge-native inbox you deploy. FlareMail is hosted and already includes send. HTML: https://sendwithflare.com/articles/flaremail-vs-reccado/ **Keyword:** flaremail vs reccado **Audience:** developers who want realtime Cloudflare mail and a cautious MCP ## Short answer FlareMail is a web inbox for Cloudflare-powered email — a hosted inbox, while Reccado is a self-hosted Durable Object mailbox with an MCP that can draft but not send. First three domains are free; Pro is $10/month for 12 domains; Agency is $60/month unlimited. FlareMail vs Reccado is hosted versus a Durable Object mailbox in your account. Reccado is self-hosted, MIT, with 4 GitHub stars. It uses Workers, one Durable Object per mailbox, R2, D1, and Queues. FlareMail does not ask you to create that layout. The codebase is not public. ## 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. Reccado 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. ## 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. ![FlareMail compose window in the web app, From set to hello@paperlantern.example](/assets/articles/flaremail-compose.webp) *Compose in the FlareMail web app. The From address is fictional sample data, captured from this repo so the screenshot is the real UI.* ![FlareMail 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 Reccado is actually good at Reccado’s interesting parts are realtime and restraint. WebSockets are realtime. Search uses FTS5. Routing rules are multi-domain. MCP at /mcp is read, search, and draft only, with no send tool. A human confirms before send. A scoped transactional API is the documented exception. An optional Telegram bridge is there. The Deploy to Cloudflare button does not seed the first mailbox. Arbitrary-recipient sending needs Workers Paid. You still operate the stack after the button. That confirm-before-send split is a real design choice, not a missing button. ## Which one to pick Pick Reccado 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](/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 FlareMail comparisons The same hosted-versus-self-host question, for the rest of the field: - [FlareMail vs Mailflare](/articles/flaremail-vs-mailflare/) - [FlareMail vs Agentic Inbox](/articles/flaremail-vs-agentic-inbox/) - [FlareMail vs Quickinbox](/articles/flaremail-vs-quickinbox/) - [FlareMail vs Orange Inbox](/articles/flaremail-vs-orange-inbox/) - [FlareMail vs Email Explorer](/articles/flaremail-vs-email-explorer/) - [FlareMail vs Postern](/articles/flaremail-vs-postern/) - [FlareMail vs Doota](/articles/flaremail-vs-doota/) - [FlareMail vs cf-mail](/articles/flaremail-vs-cf-mail/) - [FlareMail vs cloudflare-email](/articles/flaremail-vs-cloudflare-email/) - [FlareMail 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 **Can Reccado’s MCP send mail?** No. MCP at /mcp is read, search, and draft only. There is no send tool. A human confirms before send, with a scoped transactional API as the exception. **Does the deploy button create the first mailbox?** No. The Deploy to Cloudflare button does not seed the first mailbox. **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. ## Related - [FlareMail vs cloudflare-email](/articles/flaremail-vs-cloudflare-email/index.md) - [Cloudflare Email Routing SMTP: How Sending Fits Into a Cloudflare Mail Setup](/articles/cloudflare-email-routing-smtp/index.md) - [Cloudflare Email Routing Worker Inbox: Using Workers as the Mail Backbone](/articles/cloudflare-email-routing-worker-inbox/index.md) ## Start [Onboarding](https://sendwithflare.com/onboarding/) · [Pricing](https://sendwithflare.com/pricing.md) · [Setup guide](https://sendwithflare.com/help/setup-guide/)