I publish every article through two email systems. Substack sends one version. My self-hosted setup sends another. Same content, two endpoints.
This isn’t a backup plan. It’s not indecision. It’s a deliberate setup – because the two systems do fundamentally different things, and I want both of those things.
The “Substack vs. self-hosted” debate usually gets framed as a choice. Own your platform or go where the audience is. Control or convenience. Independence or reach.
I think that framing is wrong. Here’s what I’ve learned from running both side by side.
Where Substack wins
Substack is fun to use. That sounds like a small thing, but it’s not. If your publishing system feels like a chore, you’ll publish less. Substack removes enough friction that the gap between “I have an idea” and “it’s live” is remarkably short.
But fun isn’t the real advantage. Discovery is.
Substack has a built-in recommendation engine. When another writer recommends your newsletter, their subscribers see it. When someone reads your post, they get suggestions for similar writers. Notes – Substack’s short-form layer – gives you a social channel that lives right next to your long-form work. You’re not shouting into a void. You’re joining an existing conversation.
For a solo founder with no audience, this matters more than most people admit. You can have the best self-hosted WordPress site in the world, a beautifully designed email template, and a segmentation strategy that would make a marketing team jealous. None of it helps if nobody knows you exist.
Substack solves the cold start problem. Not completely – you still have to write things worth reading – but it gives you infrastructure for being found that would take years to build on your own.
The community aspect is real too. I’ve had more genuine interactions through Substack Notes and comment threads than through any other platform. There’s something about the culture – more long-form, more thoughtful, less performative – that attracts the kind of readers I actually want to connect with.
Where self-hosted wins
Self-hosted email wins on everything that happens after someone subscribes.
On Substack, every subscriber gets the same experience. Same emails, same format, same sequence. That’s fine when you’re starting out. It becomes a limitation as your audience grows and their needs diverge.
With a self-hosted system, I can build automation sequences. A new subscriber gets a welcome series. Someone who downloaded a specific lead magnet gets follow-up content tailored to that topic. I can segment by interest, by engagement level, by how someone found me. None of this is possible on Substack – at least not without workarounds that fight the platform.
Design control matters too. My self-hosted emails match my website. They feel like they come from the same place, because they do. On Substack, you’re working within their template. It’s clean and functional, but it’s not yours.
Then there’s the independence question. Substack is a company. Companies change direction. They adjust algorithms, alter recommendation logic, update terms. I don’t think Substack is going to disappear tomorrow, but I’ve been online long enough to know that any platform you don’t control can change the rules on you without warning.
With self-hosted, my subscriber list lives on my server. My emails go out through my infrastructure. If I decide to switch tools next year, I take everything with me. No export, no migration anxiety, no hoping the CSV file is complete.
GDPR compliance is simpler too. When I control the data pipeline end to end, I know exactly where subscriber data lives and how it’s handled. On third-party platforms, you’re trusting their compliance – which is usually fine, but “usually fine” isn’t the same as “fully in my control.”
Why “both” isn’t indecision
Running two systems sounds like overhead. In practice, it’s about ten minutes per week.
I write the piece once. It publishes on Substack for discovery and connection – the community, the Notes, the recommendations. Then I send a version through my self-hosted system for subscribers who came through my website or lead magnets.
Some readers are on both lists. That’s fine. The overlap is intentional. Each system serves a different function in the same workflow.
Substack is where I connect. It’s where new readers find me, where conversations happen, where the social layer lives. My self-hosted setup is where I build. Automation sequences, segmentation, long-term relationship architecture – the stuff that compounds over time but doesn’t need an audience to witness it.
The ten minutes of extra work per week buys me something valuable: optionality. If Substack changes its algorithm tomorrow – which platforms always do eventually – I have a fully functional system with my entire subscriber list. If my self-hosted setup has a deliverability issue, Substack keeps the connection alive.
It’s not redundancy for the sake of it. It’s insurance with a low premium.
The real question behind the debate
Most of the Substack vs. self-hosted arguments I see online are about philosophy. Own your platform. Don’t rent your audience. Build on land you control.
I agree with all of that – in principle. But principles alone are bad decision-making tools.
The better question is functional: what does each system actually do for you right now? And what do you need it to do in twelve months?
If you have no audience and no content engine yet, the “own everything” approach gives you a beautiful ghost town. Substack’s network effects do real work that a fresh WordPress install with zero traffic simply can’t match.
If you have a growing list and increasingly specific needs – segmentation, automation, integration with your own products – self-hosted earns its complexity.
And if you’re somewhere in between, running both is less work than most people assume.
The platform debate is a distraction from the question that actually matters: can you leave any single platform tomorrow with your subscriber list intact? If yes, you’re in a good position regardless of which tools you use. If no, that’s the problem worth solving – not which logo sits in your email footer.
Where to start
If you’re building a solo business and haven’t started an email list yet, start on Substack. The discovery alone is worth it, and the friction is close to zero.
If you already have a list and feel the walls closing in – wanting automations, segmentation, or just more control – add a self-hosted layer. You don’t have to migrate. You can run both.
The goal isn’t to pick the right platform. It’s to build a system where no single platform has the power to cut you off from the people who chose to hear from you.
That’s ownership. Everything else is just tooling.
I’m writing a series comparing the tools and systems I actually use as a solo founder. If you want to follow along, subscribe – I’ll keep sharing what works, what doesn’t, and what I’d do differently.
