MailySend: Drop-in Resend Replacement, one click deploy on Cloudflare

Hey Product Hunt 👋 I built MailySend because I liked Resend's API and disliked where the data sat. Your sending history, your contact list and your bounce data live in someone else's account, on their retention policy, at a per-email markup over what the bytes actually cost. So this is that API, reimplemented on Cloudflare's own primitives, running in your account: - const resend = new Resend(process.env.RESEND_API_KEY) + const resend = new Resend(process.env.MAILYSEND_API_KEY) + // RESEND_BASE_URL=https://your-deployment/v1 The `resend` npm package honours `RESEND_BASE_URL`, so that is the whole migration. No rewrite, and no lock-in in either direction. What's in it: transactional sending (batches, scheduling, idempotency keys), marketing broadcasts with A/B testing and holdouts, live segments that compile to parameterised SQL, automations on Cloudflare Workflows, real inbound mailboxes with MIME parsing and reply threading, delivery events with bounce classification, parsed DMARC aggregate reports, opens and clicks split by bot vs. human, and a nine-tool MCP server so an assistant can read and draft mail -- behind an approval screen you click before anything sends. Four transports, one API: Cloudflare Email Service, Amazon SES, Resend, or plain SMTP, with deterministic routing and failover. Switching is one config line. Cost: about $16/month for 100k emails on SES, or $40 on Cloudflare's own sender -- against $90 on Resend Pro and $60 on SendGrid. The dashboard shows your real month-to-date Cloudflare spend next to your send volume, so the estimate is answerable to a number. Honest about the trade: you are on call. Postmark measures inbox placement better than we do, and our comparison table says so. SES on its own is ~$10 at this volume -- MailySend runs *on top of* SES for the same per-thousand rate, it doesn't compete with it. MIT licensed, one-click deploy to Cloudflare, and it also runs as a plain Node process with no Cloudflare account at all. Live demo and docs at mailysend.com -- the screenshots are real traffic, not empty states. I'd love to hear what breaks, and what's missing before you'd move a production sender onto it.