How to Run an Owned Newsletter Instead of Renting One

I built my whole network off a box that costs less than lunch. The press, the storefront, the radio, the brain. All of it mine, all of it cheap, all of it living on land I own instead of land I rent.

The newsletter was the last piece I pulled home. It's also the one most people get wrong, because the rented version feels free until the day it isn't.

Here's how I run an owned email list. Not the polished agency version. The one-person, off-platform, sleep-at-night version.

What "rented" actually means

You sign up for the big newsletter platform. You write. People subscribe. It looks like you own a list.

You don't. You own a login.

The list lives in their database. The sending reputation is theirs. The archive of everything you ever wrote sits on their server, behind their dashboard, under their terms. They can change the pricing. They can change the rules. They can decide your topic violates a policy nobody read, and on that morning your audience is gone and you have no copy of the road home.

I've watched it happen to people. One email from support and a decade of work goes dark. They didn't do anything wrong. They just built their house on someone else's dirt and the landlord changed the locks.

Owning the newsletter means four things are yours and can't be taken: the domain, the subscriber list, the way mail leaves, and the archive. Get those four under your roof and the platform becomes a tool you swap out, not a landlord you answer to.

The four pieces you actually own

The domain. This is the foundation. A domain you registered and control is the one address nobody can revoke. Email goes out from it. The archive lives on it. If every service I use vanished tomorrow, the domain is the thread I pull to rebuild everything. Register it somewhere boring and reliable, point the DNS where you need it, and never let it lapse. That renewal is the cheapest insurance you'll ever buy.

The list. Your subscribers are a file. Emails, signup dates, a tag or two. That's the asset. Everything else is plumbing around it. The rule is simple: you keep a copy. A CSV in a folder, exported on a schedule, sitting on your own machine. If you can't open your full subscriber list as a plain file right now, today, you don't own your list. You're renting it back from whoever stores it.

The sender. Mail has to physically leave the building. You don't run your own mail server for this. That's a war you don't want, fighting spam filters at 2am for the rest of your life. You rent the trucks, not the warehouse. A transactional email service ships your mail for pennies per thousand. You point your owned domain at it, prove the domain is yours with a few DNS records, and your mail goes out signed as you. The truck company can be swapped. The domain doing the signing stays yours.

The archive. Every issue you send is also a page on your own site. This is the part almost everyone skips, and it's the one that compounds. The platforms bury your back catalog inside their walls where search engines barely reach it. On your own domain, every issue is a real page that ranks, gets found, and pulls new subscribers in for years. The letter does double duty: it lands in inboxes today and it works the search results forever.

My actual setup

I run static. A folder of markdown and a build step, same as the rest of my network. I wrote about why I tore the CMS out a while back and never looked back.

The flow is plain. I write an issue as a markdown file. The build turns it into a page on my site, formatted the way I drew it, no database, nothing to patch. That same content gets pushed to the email service that hauls it to inboxes. The signup form on my pages writes new subscribers to my list. I export that list on a schedule so a fresh copy always sits on my own drive.

No login stands between me and my own work. No dashboard owns my readers. The whole stack costs me almost nothing because static files are cheap to host and transactional email is cheap to send. I'm running the press, the store, and the radio off the same lean box, and the newsletter just joined them.

The point isn't that my exact tools are the only ones. The point is the shape. Owned domain, exported list, swappable sender, archive on your turf.

How to move without burning the house down

If you're on a rented platform now, don't panic-delete anything. Migrate slow and keep the old place running until the new one proves itself.

1. Register and control your domain if you haven't. Everything hangs off it.
2. Export your full list today. Get the CSV. Put it in a folder you back up. Do this even if you change nothing else. It's the difference between owning an asset and hoping a company stays nice.
3. Stand up the archive. Pick a static site setup, point your domain at it, and start publishing issues as real pages. This alone is worth the move.
4. Wire up a sender with a transactional email service. Add the DNS records that prove the domain is yours so your mail authenticates and lands in inboxes instead of spam.
5. Move the signup form to your own pages so new subscribers flow into a list you store.
6. Run both in parallel for a few sends. Watch your delivery. When the owned path works clean, retire the rental.

Nobody's coming to do this for you, and nobody needs to. It's a weekend of fiddling and then it's just yours.

The paranoid part, which is the useful part

Every convenient platform is a bet that the company stays aligned with you forever. That bet loses eventually. Pricing shifts, policies tighten, the thing gets bought, the founder cashes out, the rules you agreed to get rewritten by someone who's never read a word you wrote.

You don't have to predict which one. You just refuse to be standing on the trapdoor when it opens.

An owned newsletter is the whole game in one move. The relationship between you and the people who chose to hear from you, with nobody standing in the middle taking a cut and holding the keys. Free to read, yours to keep, sent from an address no landlord can revoke.

I keep the signal at home. The list comes home with it. That's the whole idea. Want to see the rest of the network it runs on? It's all right here.