Cloudflare AppsSearch apps/

All apps / Email & Communication

boxox

A self-hosted mail client and transactional email API that deploys into the visitor's own Cloudflare account, using Workers, D1, R2, Email Service, and Access for mail storage, sending, receiving, sign-in, and optional AI features.

Stars
0
Forks
0
License
NOASSERTION
Category
Email & Communication
Latest push
Published
Refreshed
Published

Review

The bill it replaces

Email on your own domain is old technology that still bills like a service. Migadu’s Mini plan is $9 a month for unlimited addresses and domains, or $19 a year on the Micro plan. A transactional send API is a second subscription: Postmark starts at $15 a month for 10,000 emails, then $1.80 per thousand more. Box Ox claims both jobs for one Cloudflare install: the inbox client and the send API, on Workers Paid at a $5 monthly minimum plus Email Service usage, which includes 3,000 sends a month and charges $0.35 per thousand after that. The usual self-hosted route is Postfix and Dovecot on a rented server, where the real cost is deliverability: an IP reputation you maintain by hand, one ISP at a time.

What Cloudflare already gives you, and what’s missing

Email Routing receives mail for your domain on any plan and forwards it, with no per-message charge. Email Sending gives your domain an API with SPF and DKIM once the account is on Workers Paid. What neither does is keep anything. Cloudflare’s service-specific terms say the Email Service is “for routing and transmission” and provides “no durable storage or ‘Inbox’ services.” A forwarded message disappears at the redirect; a send is your problem once the API accepts it. The platform hands you a faucet and a drain. A mailbox is everything around those. Something has to thread messages, keep bodies and attachments, search them, and draw the result on a screen.

What Box Ox packages up

Box Ox is that mailbox, installed into your account. One Worker serves a React client as static assets and handles the API, MCP endpoint, and inbound mail hooks. The paid profile’s wrangler.jsonc reads like a tour of the platform: a send_email binding for outbound mail, D1 for message metadata, an R2 bucket for message storage, KV for OAuth state and a downloaded OpenPhish feed. Three Queues pipelines (email events, webhook delivery, ingest) each carry a dead-letter queue. Four Workflows run ingest, enrichment, sending, and snoozing. Two SQLite-backed Durable Objects do the parts that need state: MailboxHub for live mailbox updates, FreeRuntime to hold heavier processing on the free plan. Three rate-limit namespaces cap inbound mail, per-sender volume, and agent endpoints, an Analytics Engine dataset takes usage records, and four cron triggers purge trash, refresh the phishing feed every six hours, and run recovery sweeps. Optional features add Workers AI, Vectorize for semantic search, and Browser Rendering for link previews and PDF export, and they stay unbound until the owner turns them on.

The Free profile drops those paid bindings before installing into a Workers Free account. What it keeps is governed by the platform’s ceiling, because a free account allows 100,000 requests a day, 10 ms of CPU per request, five cron triggers per account, and a Durable Objects free tier of 100,000 requests and 13,000 GB-seconds daily. Box Ox needs four of those five cron slots. The project’s own verification notes say Free-profile mail delivery and throughput remain untested.

Who’s behind it

The public record starts on the day of this review. The repository, under Paul DeMarco’s GitHub account, holds a single commit dated October 20, 2026, whose message credits Claude Opus 5.5 as co-author, and it lists one contributor with no releases or tags. The README says earlier private development history is not included. DeMarco has shipped durable open source before: flutter_blue, his Bluetooth plugin for Flutter, has drawn about 2,400 stars. The project’s download site, boxox.dev, currently serves a “Coming soon” page.

Release 2.4.4, dated October 19, describes a self-published distribution in which source, CLI, and SDK ship as direct downloads from boxox.dev. Nothing goes through the npm registry, no release carries a signature, and the README’s checksums “establish download consistency, not independent maintainer identity.” The release notes also contradict their own README on whether a Deploy to Cloudflare button exists. The documentation is the most candid part of the project. It names what stays unverified down to the sentence: “a successful /health response alone does not prove mail delivery.” The license is FSL-1.1-MIT, which permits internal use, restricts competing mail products, and converts each version to MIT two years after release. That restriction is also why this review carries no screenshot: the license does not grant the right to republish the project’s images.

Where it falls short

  • A one-day-old public project. One commit, one contributor, no issues or releases, and boxox.dev still serves a coming-soon page, so the documented install path has nothing to download today. The README says earlier private development history is not included, and there is no public record of it.
  • Transactional sending only. Cloudflare’s Email Service terms restrict sending to messages tied to a specific customer interaction, put new accounts in a reputation-gated Sandbox, and reserve the right to scan message content. Outgoing mail from Box Ox inherits those terms.
  • The free plan is a preview, and the author says so. Ten milliseconds of CPU per request is little room for a mail client, and the project’s own notes leave Free-profile delivery and throughput unverified.
  • Source-available, not open source. FSL-1.1-MIT lets you run and read the code; competing products cannot reuse it, and MIT only arrives per version after two years.

Verdict

Box Ox fits the developer who wants one Cloudflare install to hold a domain’s inbox and its transactional API, and who will accept a project one day into its public life for the sake of OAuth and MCP agent access with grants and a kill switch. If boxox.dev’s downloads are live, that developer has a real option. Until then nobody should install it, because mail you cannot download is not a thing to point your domain at.

Based on reading the source at commit 83338bc and public research, .

How these reviews are made

Research and source context

This profile is compiled from public repository data. Repository details were captured and the profile was last researched .

More in Email & Communication