A Cloudflare agentic-inbox alternative built for teams
Both run in your own Cloudflare account. agentic-inbox is a free single-trust-boundary inbox with a built-in AI assistant; MarkRelay adds per-mailbox access, scoped keys, webhooks, broadcasts and support.
Facts checked
The short answer
Choose Cloudflare's agentic-inbox if you want a free, open-source inbox with a built-in AI assistant and everyone who uses it may read every mailbox. Choose MarkRelay when several people or agents share one deployment and each should see only their own mailboxes: MarkRelay grants access per mailbox, limits every API key and webhook to its owner's access, works across many domains, and adds templates, broadcasts, one-click updates and email support.
Side by side
| Feature | MarkRelayLicense from $99/yr | agentic-inboxApache-2.0, free |
|---|---|---|
| Runs in your own Cloudflare account | Yes | Yes |
| Deploy to Cloudflare button | Yes | Yes |
| Webmail: compose, reply, folders, search | Yes | Yes |
| Access control | Per mailbox, per person | One Cloudflare Access policy for all mailboxes |
| Multiple domains in one app | Yes | Not stated |
| HTTP email API | Send, read, reply, forward | Not stated |
| MCP server | Yes | Yes |
| API keys limited to chosen mailboxes | Yes | No |
| Signed inbound webhooks | Yes | No |
| Built-in AI assistant | Bring your own agent (API + skill) | Workers AI side panel |
| Visual template editor | Yes | No |
| Broadcasts with unsubscribe and suppression | Yes | No |
| One-click updates | Yes | Not stated |
| Email support | 1 business day | Not stated |
| Price | $99/yr or $249 once | Free |
Runs in your own Cloudflare account
- MarkRelay
- Yes
- agentic-inbox
- Yes
Deploy to Cloudflare button
- MarkRelay
- Yes
- agentic-inbox
- Yes
Webmail: compose, reply, folders, search
- MarkRelay
- Yes
- agentic-inbox
- Yes
Access control
- MarkRelay
- Per mailbox, per person
- agentic-inbox
- One Cloudflare Access policy for all mailboxes
Multiple domains in one app
- MarkRelay
- Yes
- agentic-inbox
- Not stated
HTTP email API
- MarkRelay
- Send, read, reply, forward
- agentic-inbox
- Not stated
MCP server
- MarkRelay
- Yes
- agentic-inbox
- Yes
API keys limited to chosen mailboxes
- MarkRelay
- Yes
- agentic-inbox
- No
Signed inbound webhooks
- MarkRelay
- Yes
- agentic-inbox
- No
Built-in AI assistant
- MarkRelay
- Bring your own agent (API + skill)
- agentic-inbox
- Workers AI side panel
Visual template editor
- MarkRelay
- Yes
- agentic-inbox
- No
Broadcasts with unsubscribe and suppression
- MarkRelay
- Yes
- agentic-inbox
- No
One-click updates
- MarkRelay
- Yes
- agentic-inbox
- Not stated
Email support
- MarkRelay
- 1 business day
- agentic-inbox
- Not stated
Price
- MarkRelay
- $99/yr or $249 once
- agentic-inbox
- Free
agentic-inbox facts are from its README on GitHub; “Not stated” means the README does not say. It also says: “There is no per-mailbox authorization; the Cloudflare Access policy is the single trust boundary.”
Which one fits you
Choose agentic-inbox if
- You are one person, or everyone may read every mailbox.
- You want an AI assistant inside the inbox, running on Workers AI.
- You want free, open-source software you maintain yourself.
Choose MarkRelay if
- Teammates, clients or agents should see only their own mailboxes.
- You run several domains or brands from one deployment.
- Apps and agents need scoped API keys and signed webhooks.
- You also send newsletters or campaigns, and want updates and support.
Who can open which mailbox
Members see only the mailboxes granted to them. Everything else stays hidden, in the inbox and in the API.
| Person | support@acme.com | sales@acme.com | billing@acme.com | hello@brand.io |
|---|---|---|---|---|
| MayaAdministrator | Can open | Can open | Can open | Can open |
| LeoSupport | Can open | Hidden | Can open | Hidden |
| SaraSales | Hidden | Can open | Hidden | Can open |
| Triage agentAPI key | Can open | Hidden | Hidden | Hidden |
Common questions
Is MarkRelay a fork of agentic-inbox?
No. MarkRelay is a separate product with its own codebase. Both run on Cloudflare Workers and use Email Routing to receive and Email Sending to send.
Does agentic-inbox have per-mailbox permissions?
No. Its README states that the Cloudflare Access policy is the single trust boundary and that any user who passes it can access all mailboxes. MarkRelay grants each person and each API key specific mailboxes.
Can I use an AI agent with MarkRelay?
Yes. Give the agent its own mailbox and a key scoped to it. Every deployment serves an OpenAPI spec, an llms.txt and an installable agent skill, so Claude Code, Codex or your own agent can read and reply over HTTP.
Can I move from agentic-inbox to MarkRelay?
Yes. Deploy MarkRelay in the same Cloudflare account, create the same addresses as mailboxes, and point their Email Routing rules at the MarkRelay Worker. New mail then arrives in MarkRelay.
Keep reading
Own your email stack today
Buy MarkRelay once and run it in your Cloudflare account. MarkRelay adds no per-message or per-seat charge; Cloudflare usage and service limits remain separate.