Comparisons · Cloudflare email guide

FlareMail vs Quickinbox

Quickinbox is a full web client on your Workers account. FlareMail is hosted, so you do not provision D1 and R2.

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

FlareMail vs Quickinbox is hosted versus a Workers app you run. Quickinbox is self-hosted, MIT, with 407 GitHub stars. It is a full web client on Workers with D1 and R2. FlareMail does not ask you to create those resources. You open the app and connect a domain. One step sits outside the app: an Email Routing rule to the flaremail-api Worker.

Short answer: FlareMail is a web inbox for Cloudflare-powered email — a hosted inbox, while Quickinbox is a self-hosted Workers client you deploy and wire to DNS.

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.

3 DOMAINS FREE · $10/MO PRO
Lo-fi corkboard illustration with EDGE_ROUTER.EXE pinned above Email for Cloudflare domains

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.

Quickinbox 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.

FlareMail inbox list with fictional mail for hello@paperlantern.example
The FlareMail 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 FlareMail side is the domain plan, not a claim that self-hosting is free.

FlareMailQuickinbox
Where it runsHosted. Create an account and open the app.Self-hosted. You deploy and operate it.
Who operates Worker, D1, and R2FlareMail 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.Self-hosted. The setup wizard budgets about 30 minutes, mostly DNS.
InboxBrowser inbox: read, folders, search, compose, attachments, labels, and privacy controls.Full web client: threads, attachments, multi-domain, and multi-user, plus REST, CLI, and hosted MCP with OAuth.
SendSend from your domain in the same app.Resend by default, or Cloudflare Email Service. Cloudflare sending requires a Workers paid plan. Optional web push and Telegram.
PriceFirst 3 domains free. Pro is $10/month for 12 domains, then $1 per extra domain. Agency is $60/month unlimited.No FlareMail fee. You pay Cloudflare and the sending provider you configure.
GitHub README for DivinPrince/quickinbox
The public GitHub README for DivinPrince/quickinbox. This comparison does not sign in to the demo.

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
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
The public sign-in form at app.sendwithflare.com. Use it to create an account. It is not the inbox.

What Quickinbox is actually good at

Quickinbox’s strengths are the product surface and the interfaces around it. Threads, attachments, multi-domain, and multi-user are in the client. It also exposes REST, a CLI, and a hosted MCP with OAuth. Optional web push and Telegram are documented. The provider is Resend by default, or Cloudflare Email Service. The Cloudflare sending path requires a Workers paid plan.

The setup wizard budgets about 30 minutes, mostly DNS. That is a fair budget for a self-hosted mail stack. FlareMail’s setup guide says about five minutes, because the Worker, D1, and R2 are already running.

Which one to pick

Pick Quickinbox 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:

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?

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
Lo-fi corkboard illustration with EDGE_ROUTER.EXE pinned above Email for Cloudflare domains

Sources and context

FAQ

How long does Quickinbox say setup takes?

The setup wizard budgets about 30 minutes, mostly DNS. FlareMail’s setup guide says about five minutes, plus one Email Routing rule outside the app.

Does Quickinbox include MCP?

Yes. REST, a CLI, and a hosted MCP with OAuth are part of the project.

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.

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