Comparison
Cloudflare Email Service routes (paid and currently in beta) and sends mail on your domain from a Worker, the REST API or SMTP. Omucloud gives that same domain real mailboxes you sign into — from any browser or from your phone, with no keys, no code and nothing to deploy. Free, with as many addresses as you need.
Who sends the reply
You need to code
env.EMAIL.send() from a Worker, or the REST API, or SMTP — on the Workers paid plan. There is no inbox to open; the mail is handled by software you write.
OmucloudJust open app & Send
Sign in on the web or on your phone, read the message, hit reply. It leaves from your own address, DKIM-signed by your domain, with nothing to deploy and no key to hold.
The older Cloudflare
Cloudflare had only been offering forwarding route. Not a real mailbox. Cannot send replies from your phone.
Mail on a domain is two journeys, and both products make both of them. The difference is what has to sit on the way back.
Cloudflare · ImprovMX
Three hops in, and the way back runs through code you deploy
Nothing in this lane is a mailbox. Mail arrives somewhere else, and the reply is written by a program you wrote and are responsible for.
Omucloud
Two hops in, and the way back is the same mailbox
The reply is sent by the account that received it, from your own address, DKIM-signed by your domain — by a person, from an inbox.
How is Omucloud different
A web app, ready now
Sign in from any browser on any machine and your mail is there — nothing to deploy, nothing to host, no dashboard to wire up first. The address works the moment the domain verifies.
Mobile first, and an iOS app
Built for a phone before a desktop: a bottom tab bar, a card feed and a full-screen composer. It already runs in a mobile browser, and the iOS app arrives on 1 September 2026.
No API, no keys, no plan
There is nothing to integrate. No Worker to write, no SDK to install, no key to rotate and no paid tier underneath it — the product is the mailbox, not a service your code calls.
Invitations that actually work
Invites are read as standard iCalendar, so a meeting sent from Google Calendar or Outlook is recognised in the message, and your answer goes back to the organiser as a proper reply.
On invitations, precisely: Omucloud reads standard iCalendar attachments, so a meeting sent from Google Calendar, Outlook or any client that follows the same standard is recognised in the message, and answering it mails the organiser a standard reply so their own calendar updates. An invitation with no organiser recorded, or one on a domain not yet cleared for sending, is still saved to your calendar — it just cannot notify anybody.
Side by side
Feature by feature
| Feature | Omucloud | Cloudflare · ImprovMX |
|---|---|---|
| Receive mail on your domain | Yes — stored in an inbox you sign into, searchable and paginated | Yes — forwarded to a mailbox you already own, or handed to a Worker you write |
| Send from your domain | Yes, DKIM-signed, from the composer | Yes, since April 2026 — from a Worker, the REST API or SMTP. ImprovMX still does not send |
| An inbox a person can open | Yes, on the web and on your phone | No. Cloudflare's own Agentic Inbox is open-source example code you deploy yourself |
| What you have to build | Nothing. Publish three DNS records and sign in | A Worker or an API integration, plus somewhere to store and render the mail |
| API keys and plans | None. There is no API and no paid tier | Email Sending is on the Workers paid plan |
| Reply and reply-all from the right address | Built in | Whatever your code sends. From an ordinary mail client, replies still leave from your personal address |
| Attachments and inline images | Yes, up to 25 MB per message | Supported by the sending API; inbound is passed to the forwarding target |
| Calendar invites with RSVP | Yes — .ics invitations are detected, and your answer is mailed back to the organiser | Handled by the downstream mailbox, not by the router |
| Cost | Permanently free, no card | Routing is free; sending requires the Workers paid plan |
| Where they are genuinely better | Omucloud does one thing — real mailboxes on your own domain — and nothing else | Transactional and agent mail from code, unlimited aliases, catch-all routing, and no new inbox to check |
Cloudflare details as at August 2026, from Cloudflare Email Service documentation and the Email Sending public beta changelog.
When they are the right call
Three cases, and in all three the other product is the better tool. Omucloud is not trying to replace either — plenty of domains want a mailbox for the humans and a sending API for the software, and there is no reason not to have both.
You are building software, not reading mail
Transactional mail, notifications, an agent that writes to customers: Cloudflare Email Service is built exactly for that, and Omucloud has no API at all to do it with.
You never want a second inbox
A router puts your domain's mail into the one you already read all day. Omucloud is a mailbox of its own, and that is a real cost if you did not want one.
You want a catch-all or aliases
Anything at all @yourdomain, swept to one place, with no address to create first. Omucloud has unlimited addresses, but each is a mailbox you make deliberately.
Common questions
- Can Cloudflare Email Routing send email?
- Email Routing itself is receive-only. Since April 2026, though, Cloudflare Email Service adds Email Sending in public beta, so you can send from your domain using a Workers binding, the REST API or SMTP — on the Workers paid plan. What it does not give you is a mailbox: there is no inbox to sign into, so the sending is done by code you write rather than by a person answering their mail.
- So what is left between Omucloud and Cloudflare?
- Cloudflare Email Service is infrastructure for applications. Omucloud is a mailbox for people: a web app you sign into from anywhere, mobile-first with an iOS app arriving 1 September 2026, no API keys or paid plan to set up, and calendar invitations you can answer straight from the message. If you want your domain's mail to be read and replied to by a human, that is the difference.
- Is Omucloud a good ImprovMX alternative?
- Yes, if you want real mailboxes rather than aliases. ImprovMX forwards mail to an address you already have and does not send from your domain at all; Omucloud stores your mail, lets you search it, and sends replies from your own domain — with unlimited addresses, all on a permanently free plan.
- Do I need to keep Cloudflare if I use Omucloud?
- You can keep Cloudflare as your DNS provider — many Omucloud users do. You simply publish Omucloud's MX, SPF and DKIM records there instead of enabling Email Routing, since both cannot own the domain's MX at once.
- Which should I pick?
- Pick Cloudflare if the mail is being sent and received by your code. Pick a forwarding router if you only want your domain's mail to appear in an inbox you already read. Pick Omucloud if you want mailboxes on your domain that a person opens, reads, replies from and RSVPs in — as many addresses as you need, at no cost.
Keep the domain. Keep Cloudflare. Get the inbox.
Your DNS can stay exactly where it is — publish Omucloud’s MX, SPF and DKIM records instead of switching on Email Routing, and your domain gets mailboxes a person can actually open. Unlimited addresses, nothing to deploy, no card.
Keep reading
- Omucloud vs Zoho Mail Forever Free
The suite alternative rather than the developer one, and where its five-user cap and missing IMAP bite.
- How to set up a custom domain for email
The same DNS records you already know from Cloudflare, pointed at real mailboxes instead of a forwarding rule.
- What free covers, and its limits
Why unlimited mailboxes can be free at all, and every limit that comes with it, written down.
- Business email, set up from your phone
No Worker, no dashboard, no laptop — the whole setup in a mobile browser, and an inbox to open at the end of it.