Substack vs Self-Hosted: The Real Tradeoffs
Substack’s pitch is friction removal: sign up, start writing, collect subscribers, charge for access. No hosting to configure, no plugin to install, no deliverability to manage. For a writer who wants to go from idea to published newsletter without touching anything technical, Substack is hard to beat for speed of start.
The tradeoffs are real and worth understanding before you build a significant audience on the platform.
What Substack Controls
When your publication lives on Substack, Substack controls:
The relationship between your publication and your readers. Readers subscribe through Substack’s infrastructure. They discover you through Substack’s network features. The Substack app is an increasingly important reading surface. The closer a reader’s relationship is to Substack rather than to your publication directly, the more platform-dependent that relationship is.
Your revenue processing. Substack handles payment through Stripe and takes 10% of subscription revenue — not once, but permanently, on every renewal. At low subscriber counts this is trivial. At meaningful subscription volumes it is a significant and perpetual operating cost.
Your publication’s URL. By default, your publication lives at yourname.substack.com. Substack allows custom domains (pointing yourpublication.com to Substack hosting), which helps, but the content and infrastructure still live on Substack’s servers.
Your distribution features. Substack’s Notes feed, recommendation network, and app presence are features Substack controls. They can change how these work, who they surface, and what they prioritize at any time.
What You Get in Return
Substack’s network effects are genuinely valuable, especially at the start.
Discovery. Substack’s recommendation system — where publications can recommend other publications — drives real subscriber growth for many writers. The Substack app and Notes feed expose your writing to readers already in the ecosystem. For a writer starting from zero, this is not nothing.
Email deliverability. Managing email deliverability at scale is genuinely hard. SPF, DKIM, DMARC records, sender reputation management, bounce handling — Substack handles all of this. Writers who self-host newsletters have to manage deliverability themselves or pay for a transactional email service that does it for them.
Zero setup. This is worth stating plainly: the absence of technical friction is a real benefit, not just a marketing claim. Writers who publish more because they do not have to manage a server are better off than writers who set up optimal infrastructure and then delay launching because the tech is still not perfect.
The Self-Hosted Alternative
Self-hosted publishing means owning the infrastructure: a domain you control, hosting you pay for and manage, and software (typically Ghost, WordPress, or a static site generator) that runs on it.
The core tools for a self-hosted newsletter + publication stack:
Ghost (self-hosted) — the closest functional equivalent to Substack. Built-in membership, newsletter delivery, free and paid tiers, clean editor. Requires a VPS (typically $6–10/month), a Node.js environment, and a transactional email provider (Mailgun at modest subscriber counts, Postmark or Sendgrid at scale). Ghost handles deliverability through the email provider’s infrastructure.
WordPress + Mailpoet or FluentCRM — more complex to configure but more extensible. WordPress handles the publication; Mailpoet or FluentCRM handle subscriber management and email delivery.
Static site + Listmonk — Listmonk is a self-hosted newsletter and mailing list manager that runs as a Go binary with a Postgres database. Highly capable, zero per-email cost beyond the transactional email provider, open source. Requires more technical comfort.
The Migration Problem
The practical argument for at least considering Substack is the switching cost trajectory. Moving from Substack to a self-hosted setup is possible — Substack allows CSV export of subscriber email addresses — but:
- Reader habits built around the Substack app do not transfer
- Subscribers who found you through Substack’s recommendation network may not follow through a migration
- Paid subscribers need to be migrated to a new payment processor, with associated churn
- Notes posts and Substack-native content do not port
The switching cost grows with audience size. A writer with 200 subscribers can migrate with minimal friction. A writer with 20,000 subscribers faces a genuinely difficult migration with meaningful churn risk.
This is the structural case for starting self-hosted: it is hardest to leave Substack when you most want to — when you have built something significant enough to matter.
The Practical Middle Ground
For writers who want the benefits of self-hosted infrastructure without fully giving up Substack’s discovery features, a common pattern is:
- Run the primary publication on Ghost or WordPress, on a domain you own
- Maintain a Substack presence as a distribution channel (cross-posting or publishing shorter pieces there) to capture discovery
- Direct Substack readers to subscribe on your owned platform for the full publication
This is more operational overhead than either pure approach, but it captures network effects while maintaining infrastructure independence.
The Decision
The honest answer depends on where you are and what you value.
Start on Substack if: you want to validate whether you will actually publish consistently before investing in infrastructure, you are starting from zero audience and want Substack’s discovery, or you have no interest in managing technical systems.
Start self-hosted if: you are serious about long-term audience ownership, you are already technical enough that setup is not a barrier, or you are building something that will generate meaningful subscription revenue (where the 10% cut matters).
Either way, own your domain. Whether on Substack with a custom domain configured or self-hosted, having yourpublication.com as your primary address gives you portability options that yourname.substack.com does not.