Cloudflare Email Routing only forwards inbound mail to a destination address. Email Inbox turns that routing into a full inbox: receive, send from your domain, thread conversations, and search every message — all on Cloudflare's infrastructure, provisioned automatically.
A real inbox on top of Cloudflare Email Routing — not just a forward
Send mail from your domain via Cloudflare's send_email binding
Full-text search across every message
Automatic MX, SPF, and catch-all route setup
Comparison
Cloudflare's native email routing — forwards inbound mail to a destination address.
| Feature | Email Inbox | Cloudflare Email Routing |
|---|---|---|
| What it does | Full inbox: receive, send, search, thread | Forwards inbound mail only |
| Sending mail | Yes, from your domain | No — forwarding only |
| Inbox UI | Built-in mail client | None — you bring a destination |
| Search across mail | Full-text search | Not applicable |
| Setup | OAuth + pick domains | Manual routing rules |
| Best for | People who want an inbox, not a forward | Forwarding to an existing mailbox |
Comparison reflects general product positioning as of 2025. Verify with each provider's current plans.
Authorize Kiap to manage Email Routing and deploy a Worker. One scoped OAuth consent screen — no API tokens to create or paste.
Pick one or more domains from your Cloudflare account. Kiap enables Email Routing, deploys a Worker, and wires a catch-all rule.
Kiap deploys a Worker per domain, turns on Email Routing with the right MX and SPF records, and creates the catch-all route. A few seconds per domain.
No. Cloudflare Email Routing forwards inbound mail to a destination address you already own. Email Inbox builds on top of Email Routing and a Worker to give you an actual inbox — you read, reply, search, and send mail from your domain, without forwarding it somewhere else first.
No. Email Inbox is the destination. Mail on your domain is parsed, stored with full-text search, and presented in a mail client — no external mailbox required.
No. Kiap deploys a Cloudflare Worker to your account and uses Cloudflare Email Routing for inbound mail. There is no Postfix, no Dovecot, and no server to keep patched. You approve one OAuth consent screen and Kiap provisions everything.
No. Authorization happens through Cloudflare OAuth. You approve a scoped consent screen in your browser. Kiap never sees your Cloudflare password and you never paste a token.
Yes — that is the whole point. Pick any domain on your Cloudflare account and Kiap provisions a catch-all inbox on it. Every address on that domain lands in your inbox by default.
Yes. Select one or many domains during setup. Each gets its own Worker and catch-all route, and all mail arrives in one inbox you can search and thread.
Yes. Outbound mail goes through the same Cloudflare Worker using Cloudflare's send_email binding, so you send from your own domain. Replies, reply-all, forwarding, HTML and plain text, and attachments are all supported.
Email Inbox runs on Cloudflare's free Email Routing tier and a free-tier Worker. You bring the domain. Check the Kiap pricing page for plan details.
Authorize Cloudflare, pick your domain, and you're sending from it in minutes.