Owning your email infrastructure
The platform isn't your friend — it's your landlord. What it actually takes to own the pipes your letter travels through, and when it's worth it.
Every newsletter platform makes the same quiet promise: we'll handle the pipes. And they do — until the price changes, the feature sunsets, the account flags, or the company sells. Then you learn the difference between renting an audience and owning one.
What you actually rent
When your letter lives on someone else's rails, you're leasing four things: the sending reputation, the subscriber relationship, the checkout, and the export button. Most platforms let you carry out the CSV. Almost none let you carry out the reputation — the years of deliverability your domain earned, or worse, didn't.
The ownership checklist
- Your own domain, sending. mail.yoursite.com with SPF, DKIM, DMARC aligned. Reputation attaches to the domain — make sure it's yours.
- Your own SMTP or provider account. SES, Postmark, or a reputable relay under your credentials. If the platform disappears, the pipe doesn't.
- A database you can dump. Not an export wizard — an actual database, on a server you can SSH into, backed up nightly.
- Checkout under your merchant account. Paystack or Flutterwave paying into your account, not a platform wallet that settles when it feels like it.
The honest trade-offs
Ownership costs you a weekend of setup and the responsibility of your own backups. What it buys: no rev-share on your revenue, no algorithm between you and your list, no rug-pull risk, and the ability to leave any vendor without leaving your business.
Rent tools. Own relationships. The list, the domain, the revenue — those are the business.
When it's worth it
If your letter is a hobby, rent happily. The moment it makes money — or you intend it to — owning the rails stops being ideology and becomes risk management. This site runs exactly this way, and it's why this issue can tell you to do the same without flinching.