Owning Your Email List Instead of Renting It: What It Costs and the Smallest Version Worth Doing

TL;DR: Your list is the one asset a platform can’t repossess, but only if you hold a copy you can mail from. You don’t have to own the whole stack. You do have to own the export and the sending address.

A post on Engineered.at summarizes Sam Patterson’s switch from Substack to Listmonk, and the title carries the whole reason: Substack has no API. Everything else follows from that one missing door.

I’ve stood at that door. Got pissed off enough at it once to build my own Substack integration, because I wasn’t about to run some stranger’s black-box code against my account and hope for the best.

Patterson’s setup fits in one breath. Listmonk, a self-hosted newsletter manager, handles subscribers, lists and campaigns. Amazon SES does the delivery over SMTP. A GitHub Actions workflow calls the Listmonk API when new content lands on the blog, and a frontmatter flag on each post decides whether it goes out as a newsletter. Publish the post and the email happens. No dashboard. No copy-paste.

That’s what an API buys you.

The newsletter stops being a place you go and becomes a step in your own pipeline.

Why does a missing API matter to a creator who just wants to write?

Because the first time you want something the platform didn’t plan for, you find out whose tool it is. Send a post to the list when it goes live. Pull subscriber counts into your own page. Move the list somewhere else. Each of those is a small ask, and each one turns into a feature request to a company with its own priorities and no reason on God’s green earth to put yours first.

The Engineered.at page is an aggregator summary, and it says nothing about costs, hosting specs or how Patterson moved his subscribers over. So read it as a sketch of the architecture, and don’t read it as a price quote. The one failure it does mention is the best part: a send broke because Listmonk’s default SMTP “from” address had to be changed before delivery worked. That’s what owning it feels like. Small, dull, a pain in the ass, and yours to fix.

The IndieWeb borrowed punk’s best idea

Jim Mitchell keeps The IndieWeb Is Punk Manifesto. It grew out of Jamie Thingelstad’s original post, whose framing is that punk rejected the music industry of its day and the IndieWeb rejects the dominant platforms. Mitchell boils the ownership argument down to “Own your domain. Own your data. Own your identity.”

I like the punk comparison for a reason that has nothing to do with safety pins. Punk was a way around gatekeepers. You didn’t wait for a label to say yes. You booked the room, made the flyer and played to whoever the hell showed up. A newsletter on your own domain works the same way. Nobody approves you, and nobody can demote you in a feed you never controlled.

Thingelstad’s version has a line that fits the email world exactly: “We opt out of algorithmic surveillance systems and choose to be independent.” Anyone who’s watched a platform change what gets surfaced, overnight and without a word, knows what that opt-out is worth.

Owning the list costs time and attention

Time and attention, mostly, and nobody hands you a receipt for either.

• Deliverability is now your job. Landing in the inbox depends on your sending domain, its authentication records and your list hygiene. A platform eats that cost for you. You don’t get that anymore.
• Bounces and unsubscribes are your job. You need working unsubscribe links and a way to stop mailing dead addresses.
• Something has to stay up. A server, a database, a backup. If it falls over the morning of a send, there’s no support ticket to file, just you and a log file.
• You lose the built-in audience engine. Platform recommendation networks and discovery are real. Leave, and the growth comes from you or it doesn’t come.

What you get back is the right to leave

A subscriber list that’s a file you hold. The ability to automate sending from wherever you publish. A sending address under your own domain. And the one thing a renter never gets: the option to move again without asking anybody’s permission.

What is the smallest version worth doing?

Most independent creators don’t need to babysit a server on day one. The smallest version that grabs most of the value looks like this:

1. Export your list on a schedule. Monthly, to a plain CSV that sits in your own storage. If the platform vanishes tomorrow, you lose a tool and keep the audience.
2. Collect signups on your own domain. A form on your site that writes to a file or a database you control, even if it also feeds the platform.
3. Send from a domain you own. Authenticated, with a reply address that reaches you. A mail host like Fastmail or Proton will run that inbox on your own domain for a few bucks a month, and the address stays yours when you switch hosts.
4. Keep one test send you trust. Before you need it.

Only after that does self-hosting a full newsletter manager earn its place. Patterson’s route is the far end of the same road, and it starts making sense the week clicking “send” by hand feels like a toll booth you pay every time you publish. If you already push posts from a repo, you’ve got the habits. If you don’t, step one is a calendar reminder and a CSV with your readers’ names in it, sitting on a drive nobody can lock you out of. Check the date on that file. If it’s older than the last time a platform changed its terms on you, it’s already stale.