Why Substack Writers Need a Self-Hosted Website

Relying solely on a platform for your audience is a gamble where the house always wins. Eventually, investor interests shift, and the platform shifts with them. It doesn't matter if you love the current UI or the growth tools. When the goals of the people funding the site diverge from your goals as a writer, you're the one who loses.

I've seen this cycle enough times to know that "platform lock-in" is just a polite way of saying you're renting your career. You might think having a website on Substack solves this, but that's a misunderstanding of what the tool actually is. Substack isn't your home. It's a distribution engine meant to amplify a home you already own.

Rachel from Conscious Living gets this right. She uses the platform as a CMS, not a destination. It's a subtle distinction, but it's the difference between owning your assets and hoping a company in San Francisco keeps your account active.

The real question is whether your current setup would survive if the platform decided to change its pricing or visibility algorithms tomorrow.

The Platform Dependency Trap

Building on a platform is building on rented land. When you rely entirely on a service like Substack or Twitter for your archive, you don't own your history; you're just borrowing a database. This is a precarious position because platform pivots are inevitable. When a company changes its discovery algorithm or shifts its monetization strategy to satisfy investors, your reach can drop overnight. User experience is rarely the priority when a board of directors demands a new growth metric.

The loss of "institutional memory" is the real danger here. If a platform shuts down or wipes your data, your intellectual record vanishes. This is why owning a self-hosted site is a practical necessity, not just a hobby for enthusiasts. It's the difference between having a permanent record and having a temporary profile.

Setting up a basic static site generator like Hugo or Jekyll is the fastest way to move your content into a format you actually control.

brew install hugo
hugo new site my-archive
cd my-archive
hugo new site-theme # Add a theme to get started

The technical overhead of managing your own site is higher than clicking "Publish" on a platform, but it's the only way to ensure your work exists in five years. If you're just using a platform as a distribution channel while keeping your primary records in Markdown files on your own server, you've solved the problem. If the platform is your only archive, you're one API change away from losing everything.

The Strategic Hybrid Model

The goal is to use Substack for distribution and a personal site for ownership. Substack is great for growth because it has built-in discovery and a mailing list, but you don't own the platform. If the company changes its pricing or disappears, your archive goes with it. A personal site is your institutional memory. It's the official record where a post exists because you put it there, not because a platform allows it.

This setup is a bit tedious because it requires a double-posting workflow. You're essentially managing two different CMSs. It's an annoying friction point, but it's the only way to ensure your work isn't lost to the same void as old Twitter threads.

To make this sustainable, you should automate the archive process. Instead of manual copy-pasting, use a script to pull your Substack RSS feed and save the content as Markdown files in a Git repository. This turns your blog into a version-controlled asset.

import feedparser # Used to parse the Substack RSS feed
import os

FEED_URL = "https://yourusername.substack.com.rss"

def archive_posts():
    feed = feedparser.parse(FEED_URL)
    for entry in feed.entries:
        # Save each post as a markdown file for a static site generator
        filename = f"{entry.id}.md"
        with open(filename, "w") as f:
            f.write(f"# {entry.title}\n\n{entry.description}")

archive_posts()

Your permanent site should be a static site generator like Hugo or Jekyll. These are better for archives because they're just files on a disk. You can host them on Cloudflare Pages or GitHub Pages for free.

• Full control over CSS and layout
• Permanent URLs that don't change
• Local backups of every word you've written
• Zero monthly subscription fees

Ownership vs. Distribution

The POSSE strategy sounds great in a manifesto, but I think it underestimates the sheer friction of the modern attention economy. Moving your audience from a centralized platform to your own domain is an uphill battle against the "push" mechanisms that actually make content get read. If you're using Ghost or a self-hosted setup, you've solved the ownership problem, but you've inherited the distribution problem. Most people don't check RSS feeds anymore; they check notifications.

I disagree with the idea that "owning your audience" is a binary state. If your readers only find you through a Substack recommendation engine, you don't actually own that relationship,you're just renting it at a lower rate. However, the alternative,building a completely independent infrastructure,often results in shouting into a void. The real tension isn't between ownership and distribution; it's between the convenience of a platform's growth hacks and the inevitable moment those platforms pivot to satisfy a VC's exit strategy.

The question I'm left with is whether the effort of maintaining a private site actually yields a meaningful hedge against platform risk, or if we're just spending our time polishing a digital fortress that no one knows how to find.

Conclusion

Substack is a great distribution tool, but it isn't a home. We've seen this movie before with Facebook and Twitter; the "digital paradise" phase always ends when the platform starts answering to investors instead of users. Relying on a single company for your entire digital presence isn't a strategy, it's a gamble.

If you're like Rachel from Conscious Living, you can make the hybrid model work. Use Substack to amplify your reach, but keep your actual archives and identity on a site you own.

The real question is whether you'd rather spend a few hours setting up a self-hosted site now, or spend a week of panic migrating your entire audience five years from now when the terms of service change overnight.