Compare variants
Choose between Cloudflare Inbox and Resend Inbox.
Simple Inbox has two deployable implementations with the same product idea and different infrastructure tradeoffs.
| Need | Pick |
|---|---|
| You want the fastest Cloudflare-native deployment | Cloudflare Inbox |
| Your domain already uses Cloudflare DNS and Email Routing | Cloudflare Inbox |
| You want Queue events for downstream Workers/OpenClaw-style automation | Cloudflare Inbox |
| You want bearer API routes for machine sends/replies/thread reads | Either variant |
| You want a Dockerized Node app | Resend Inbox |
| You prefer Resend for sending and receiving | Resend Inbox |
| You want S3-compatible storage rather than Worker bindings | Resend Inbox |
| You need to run on any container host | Resend Inbox |
Shared capabilities
- Single-tenant custom-domain inbox
- Catch-all mailbox partitioning
- Magic-link operator login
- Raw EML and attachment storage
- Owner-inbox forwarding with reply aliases
- Web replies with per-inbox sender alias settings
- Bearer-token machine APIs
- Local mock mode when storage is not configured
Cloudflare-specific capabilities
Cloudflare Inbox adds native Cloudflare primitives:
- Cloudflare Email Routing inbound handling
- Cloudflare Email Service outbound sending
- R2 object storage binding
- Cloudflare Queue producer events for handled inbound mail
- Workers Deploy Button path
Resend-specific capabilities
Resend Inbox adds provider-portable deployment:
- Resend
email.receivedwebhook ingestion - Resend Email API sending
- S3-compatible storage through AWS SDK
- Docker image build and GHCR publishing workflow
- Runtime portability across container platforms