Who actually sends your newsletter?

A field guide to rented pipes: how to find out, from public pages alone, which company actually delivers your email.

Published 2026-07-17

The question nobody asks during the free trial

You compared editors. You compared pricing, analytics, referral programs, maybe the fonts. The question that decides whether your writing reaches anyone — whose servers actually deliver it — probably never came up, because no platform volunteers it.

For most of the creator-platform market, the answer is somebody else's: every newsletter platform we surveyed rents its delivery: beehiiv's status page lists SendGrid components; Buttondown's subprocessor list names Mailgun and Postmark; Substack sends through Mailgun (verified on their own public pages, July 2026).

That is not an accusation of wrongdoing. Operating delivery infrastructure is hard: reputation management, warmup, feedback loops, blocklist politics. Reselling an established provider is a rational choice for a company that would rather point its engineers at the editor. But it is a choice, it lives below the fold of every landing page that mentions deliverability, and you are the one who carries its consequences.

What renting means when something breaks

Delivery problems are quiet. Open counts sag. A few readers mention the spam folder. You write in, and you hear back from "our deliverability team."

At a reseller, that phrase deserves scrutiny. The team you are talking to does not operate the servers that spoke to your readers' mailbox providers. Its real capability is to diagnose what it can see and escalate a ticket into its vendor's queue. You are two hops from the machine. Nobody you can reach can show you the receiving server's side of the conversation, because the company that owns that conversation has a contract with your platform, not with you. Accountability follows the pipes, and the pipes are rented.

What renting means when you want to leave

Platforms compete on the layers above delivery: the editor, the network, the analytics. If two platforms hand their sending to the same underlying provider, then "better deliverability" — often the anchor of the pitch — may amount to the same pipes behind a different dashboard. And resold sending often means shared sending infrastructure, which makes your reputation partly a neighborhood effect: you inherit some of the behavior of strangers on the same pools.

None of this makes switching pointless. It means the delivery layer is usually not where the differences live, and you should weigh the differences that are real — ownership of your list, export paths, fees — instead of a delivery story two vendors may be buying from the same place.

Check for yourself

You do not have to take our word, or theirs. Three public sources will tell you who sends any platform's mail:

1. The status page. Companies monitor what they depend on. When a platform's status page lists another company's email service as a component, that is the dependency stating itself: they have to tell you when it breaks because they cannot fix it themselves.
2. The subprocessor list. Data-protection law obliges companies to enumerate the subprocessors that handle personal data, usually on a privacy or DPA page. A company that transmits your subscribers' addresses through a third party has to name that third party. Read the list and look for delivery vendors.
3. The email itself. Open a newsletter you receive from the platform and view the raw source. Read the Received: header chain, the d= domain in the DKIM signature, and the Return-Path:. Infrastructure has a hard time hiding from the headers it is required to write.

If those sources name a company other than the one charging your card, you now know who actually sends your newsletter — and who your platform calls when it stops arriving.

Where we stand

We are not a neutral observer here, so we will not pretend this conclusion is neutral: Email Fast runs its own mail transfer agent, warmup engine, reputation breaker, and per-tenant fair queue — the pipes are ours, not resold. That was the founding decision, and it cuts both ways: when delivery breaks for our senders, there is no vendor to escalate to, and none to hide behind. The person who answers the ticket operates the machine, and the machine can show its work, down to the receiving server's own response.

Renting pipes is a defensible way to build a newsletter product. We just think you should get to see that the choice was made — and we chose the other thing. How our delivery path works end to end is documented at /features/deliverability.