Setting up email on a custom domain usually means configuring MX records, SPF, DKIM, and a mail server you have to keep alive. Email Inbox does all of it for you — authorize Cloudflare, pick your domain, and get a catch-all inbox that receives, sends, threads, and is fully searchable.
MX, SPF, and catch-all configured automatically
No Postfix, Dovecot, or server to maintain
Catch-all: every address on your domain works
Send from your domain in the same inbox
Comparison
Google's free consumer email. Hosted on gmail.com or a custom domain via Google Workspace.
| Feature | Email Inbox | Gmail |
|---|---|---|
| Runs on your own domain | Yes, catch-all by default | Only on Google Workspace (paid) |
| Mail server to run | None — Cloudflare Worker | None — Google hosts it |
| API tokens to paste | No — OAuth consent | No |
| Where your mail lives | Your Cloudflare account + Kiap | Google's servers |
| Pricing model | Cloudflare free tier + Kiap plan | Free, or per-seat Workspace |
| Best for | Owners who want mail on their domain without Google | Consumers and Workspace shops |
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.
Kiap enables Cloudflare Email Routing, sets the MX records, configures SPF, and creates a catch-all route so every address on your domain lands in your inbox. You do not edit DNS manually — it happens during provisioning.
Yes, as long as the domain is on your Cloudflare account with Cloudflare managing its DNS. Pick it during setup and Kiap provisions the inbox on it.
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.