MailySend

MailySend speaks the Resend API, so an app that sends through Resend can switch by changing its base URL and API key. Behind that API it adds marketing broadcasts, automations, mailboxes for inbound mail and deliverability reports, all stored in your own Cloudflare account. Mail goes out through Cloudflare Email Service, Amazon SES, Resend or any SMTP server, with automatic failover between them.

Transactional sending covers batches of 100, scheduled sends up to 30 days ahead, idempotency keys, attachments and tags. For marketing there are audiences with custom properties, CSV import, live segments, broadcasts with A/B tests and a preference centre for unsubscribes. Automations are built from steps (send, wait, branch, tag, call a webhook) and run on Cloudflare Workflows. Inbound mail arrives through Email Routing into mailboxes with threading, full-text search and attachments in R2. Analytics cover delivery, bounces and complaints, opens and clicks with bot and Apple Mail Privacy Protection traffic counted separately, and parsed DMARC reports. Webhooks are signed and retried, templates can be Handlebars, MJML or JSX with version history, and an MCP server lets an AI assistant read and draft mail that you approve before it is sent. The Deploy to Cloudflare button asks for nothing; the build creates the queues, D1 database, KV namespaces and R2 bucket. On first open, /setup lets you claim the instance with a passkey, and there is no password store. The same code also runs as a single Node process without Cloudflare.

Built for: Developers and small teams who send transactional and marketing email and want the sending history and contacts in their own account

An alternative to: Brevo, Mailgun, Postmark, Resend, SendGrid

What you can use it for

• Move an app off Resend without changing its code
• Send newsletters and product announcements to segmented audiences
• Receive and answer mail on your domain in shared mailboxes
• Watch bounces, complaints and DMARC reports for your sending domain

Deploy

• One-click

  Branch main

  Deploy to Cloudflare

The Deploy button has no fields. Afterwards you claim the instance with a passkey at /setup, verify a sending domain and choose a transport.

What it needs to run

• Analytics Enginems_api_usage, ms_email_events
• D1 databasesmailysend
• Durable ObjectsAutomationCohortDO, AutomationRunDO, BroadcastDO, BroadcastCounterDO, MailboxDO, ScheduleShardDO, SegmentDO, SendingDomainDO, WebhookEndpointDO, WorkspaceHubDO
• KV namespacesCACHE, SUPPRESSIONS
• Queues (consumer)ms-send
• Queues (producer)ms-automation-triggers, ms-broadcast-pages, ms-dmarc, ms-events-norm, ms-export, ms-inbound, ms-segments, ms-send-bulk, ms-send, ms-webhooks
• R2 bucketsmailysend
• Email sendingSEND_EMAIL

Good to know

Cloudflare Email Service, the default transport, is in beta and needs Workers Paid; with Amazon SES, Resend or SMTP you pay that provider instead. Receiving mail over SMTP cannot run on Workers and needs a separate container. There is no alerting yet. Whoever opens /setup first claims the instance, so claim it right after the deploy. The repository dates from September 2026.

Cost on Cloudflare

Where this comes from

• Repositoryhttps://github.com/GagnDeep/mailysend
• App websitehttps://mailysend.com
• Documentationhttps://mailysend.com/docs