Section
Listicles
Quick, scannable roundups — tools, tips, and checklists for building and running your own email stack. 25 articles
6 Myths About Sending Email From Cloudflare Workers
Cloudflare Workers grew up. The platform now has the pieces for a real email stack, but the lore around it has not caught up, and stale tutorials keep recycling claims that fall apart on contact. Here are the six myths that come up most, what is actually true, and where to read the full mechanics.
5 Smart Ways to Use Cloudflare R2 in an Email Stack
D1 gets the attention because it holds your messages and contacts, but a real email stack generates a lot of bytes that have no business living in a SQL row. Attachments, inline images, full MIME bodies, backups: all of it wants object storage. R2 is that storage, and its zero egress pricing fits email's habit of fetching the same blob over and over. Five concrete uses, each one keeping your D1 leaner and your stack more yours.
6 Cloudflare Queues Patterns for Reliable Email Sending
Email sending fails in boring, predictable ways: the provider has a slow minute, a recipient's domain rejects a batch, your Worker hits a rate limit, a retry fires twice. Cloudflare Queues turns those failure modes into handled cases instead of lost mail. Here are six patterns worth wiring in before you scale past a trickle, each one specific to running email on Workers.
5 Cloudflare Primitives Every Email Stack Is Built On
People assume "build your own email" means a mail server, a cron box, a Postgres instance, and a weekend you will not get back. On Cloudflare it decomposes into five primitives that map cleanly onto the five jobs an email stack actually has: run code, store data, hold blobs, queue work, and receive mail. Here is each one, what it does, and where it ends.
7 Things You Can Do With Cloudflare Email Routing
The marketing screenshot for Cloudflare Email Routing is "forward an address to your real inbox." That works. But the same feature hands you an email() Worker handler that fires on every inbound message, so you can parse, store, classify, and act on mail without running a mail server. Seven things worth doing, ordered from five-minute win to inbound platform.
9 Cloudflare Email Mistakes That Land Your Mail in Spam
Most "Cloudflare email" problems are not Cloudflare problems at all. They are the ordinary deliverability mistakes that a SaaS sender used to hide from you, now exposed because you are holding the wires directly. The nine below are the ones that quietly route good mail to spam or get it rejected outright. Each has a fast fix.
7 Reasons Cloudflare Email Costs a Fraction of SaaS
If you came from Mailchimp, Resend, and a webmail host, you were paying three vendors to do what Cloudflare's primitives already do: send, store, and serve. The savings are not a coupon. They come from a different pricing model: metered infrastructure instead of retail SaaS markup. Here are the seven places the difference actually lives, with the honest caveats kept in.
Your AI Email Agent Safety Checklist (11 Items)
Giving an agent your inbox is not the risky part. The risk is giving it your inbox with no brakes: no review step, no allowlist, no record of what it did. Most agent-email incidents are not exotic jailbreaks, they are an auto-send flow firing in a loop, or a model taking instructions from an email body. This checklist is the boring, load-bearing stuff that turns a clever demo into something you can run against real customers.
Buy vs Build vs Self-Host Email: 6 Questions That Decide It
Every team eventually hits the email question: pay a SaaS, write your own infrastructure, or run a stack you own. The loud version of this debate ignores that the answer depends entirely on your constraints, not on principle. The six questions below are the ones that actually move the decision. Work through them honestly and you will know which column you belong in. For the long-form version of this argument, see the full buy vs build vs self-host breakdown.
9 Bounce and Suppression Best Practices That Protect Your Reputation
Bounces are not the problem. Ignoring them is. One dead address costs nothing; a thousand uncaught bounces with automatic retries on top tells Gmail and Yahoo you are mailing a list you do not maintain, and that is how reputations slide into the spam folder. These nine practices keep bounce data working for you, and they matter more on a self-hosted Cloudflare stack where nobody manages the suppression list but you.
Top 8 Tools to Own Your Newsletter on Your Own Domain
Most "own your audience" advice stops at exporting a CSV, which is the weakest form of ownership there is. Real control means the form, the database, the sending domain, and the logs all live where you can reach them. The list below walks from signup to send, and each item names the specific Cloudflare primitive or pattern that does the work, so you can build piece by piece or adopt a stack that bundles them.
8 Best SendGrid Alternatives for Teams That Outgrew It
SendGrid got most teams to their first hundred thousand sends without trouble. The friction shows up later, usually when a pricing tier jumps, a deliverability dip lands transactional mail in spam, or someone asks where the recipient data actually lives. Below are eight real alternatives, ordered roughly from "drop-in replacement" to "stop renting the infrastructure entirely." Each one says where it genuinely wins before noting where it stops.
Top 10 Self-Hosted Email Tools, From Mailcow to Serverless
Owning your email means owning the work that comes with it. The classic stacks give you total control of a Linux box, your SMTP daemon, and your IP reputation, which is exactly as powerful and as fiddly as it sounds. The newer serverless approach removes the box but introduces a different constraint. This list runs from heavyweight to featherweight, says what each tool is genuinely good at, and names the operational cost you sign up for. For a structured head-to-head, see how the self-hosted email platforms compare.
11 Best Mailchimp Alternatives That Don't Tax You Per Contact
Mailchimp is a fine product. The friction is the pricing model: you pay for contacts stored, not value delivered, so a large list you mail once a month costs the same as one you hammer daily. This list ranks alternatives from "cheaper but still per-contact" up to "no contact tax at all," because that axis is the one that actually decides your bill in two years. For the full argument on why this model bites, see how per-contact pricing quietly inflates your email bill.
9 Best Flat-Rate Escapes From Mailchimp-Style Pricing
Mailchimp is a capable tool. The problem is the meter: you pay for contacts stored, so a 40,000-person list you email monthly costs the same as one you blast daily. "Flat-rate" is the honest goal here, but few tools are literally flat, so this list ranks real escapes by effort to switch, lowest first. The cheapest moves only soften the curve; the harder ones cut the link entirely. For why this pricing model bites in the first place, see how per-contact pricing quietly inflates your email bill.
8 Best Amazon SES Alternatives (and When to Skip the Console)
Below are eight alternatives, ranked on the two things that decide the switch: how much setup pain you trade away, and how much deliverability tooling you get for free. They run from "polished managed API" to "stop renting the pipe entirely."
7 Best AI Email Tools You Can Run on Your Own Stack
The pitch for AI on email is real: triage that actually triages, answers grounded in your own history, summaries that save you from a 40-message thread. The catch with the SaaS versions is that your entire mailbox, the most sensitive corpus most companies own, becomes training-adjacent data on someone else's servers. The good news for a privacy-minded team is that the building blocks are all self-hostable. Here are the seven worth running yourself, what each is for, and the one thing to get right.
8 Answer Engine Optimization Tactics for Developer Tools
The shift is simple to state: people increasingly ask an assistant instead of a search box, and the assistant returns one synthesized answer with a handful of citations. For a developer tool, getting named in that answer is the new top of funnel. The good news is that the tactics are mostly things good docs should do anyway: be clear, be specific, be structured, and be honest. Here are eight that move the needle, each one a concrete thing you can ship this week.
7 AI Inbox Features Gmail Won't Give You
Gmail will summarize a thread, suggest a reply, and sort your promotions. That is real value, and for a personal account it may be all you need. The ceiling shows up the moment you want an agent to take an action Google did not anticipate, an answer grounded in your whole archive, or a guarantee about where your mail goes. None of those are features a vendor can hand you, because they are properties of owning the stack. Here are seven, with the honest tradeoff on each.
10 AI Inbox Features Every Developer Should Know About
The interesting thing about AI on email, from a builder's seat, is how little of it is exotic. A chat agent is a few typed tools over your message store. Triage is an LLM call plus a label column. RAG is search plus a prompt. Once you see the inbox as a programmable surface, the features stop being magic and start being a checklist. Here are ten worth knowing, each one a thing you can wire up yourself on infrastructure you control.
10 AI Triage Rules That Tame a Busy Inbox
A busy shared inbox, an agency juggling ten clients, a founder drowning in receipts and "quick questions": the problem is never that email is hard to read, it is that the important three messages are buried under forty that a machine could have sorted. Good triage pairs an intent with an action and runs on every message as it lands. The rules below go from the safest, fully-automatable wins to the ones you keep on a leash. Each one says what to detect and what to do about it.
8 Mistakes People Make Letting an AI Agent Touch Their Email
Wiring a model to your mailbox is the easy part. A few tool definitions and an API key and suddenly Claude can read, draft, label, and send. The hard part is the boring safety scaffolding nobody screenshots for the demo video. Here are the eight mistakes that show up over and over, and the specific guardrail that fixes each one.
9 Agent Tools to Build for Your Inbox First
An agent over your mailbox is a model plus a set of typed functions it can call. The model is the easy part. The art is choosing which capabilities to expose, in what order, and with what guardrails. Build them in this sequence and you get a useful assistant fast, without handing it a loaded gun on day one. The ordering matters: each tool here unlocks the ones below it.
8 Tools to Add Email to Your App in an Afternoon
Adding email used to mean picking a vendor, wiring an SDK, and praying about deliverability. The work splits into a few concrete jobs: scaffold the stack, make the send call, shape the HTML, prove it lands, and react when it bounces. Below are eight tools ordered from "set it up" to "make it reliable," so you can stop at whatever depth your app needs today and come back for the rest.
8 Email A/B Tests Worth Running on Your Own Stack
Most "A/B testing" advice is a list of subject-line tricks. The useful version is a short menu of variables ranked by leverage, run one at a time, on a sample big enough to clear noise. The other half of the job is the data: if your analytics are sampled, rounded, or locked inside a vendor dashboard, your "winner" is a guess with a confidence badge on it. Run these on a stack you own and every open and click is a row you can query. For the deepest dive on the first test below, see how to A/B test email subject lines properly.