The Indie Publisher's Case for Owning Your Infrastructure
Every few years, a platform that indie publishers relied on changes the rules. Algorithm changes cut organic reach. Monetization programs introduce new requirements or reduce payouts. Accounts get suspended without clear appeal paths. The terms shift in ways that favor the platform over the publisher.
This is not a new dynamic. It predates the internet. But the specific form it takes now — where a significant portion of an independent publisher’s audience, revenue, and distribution lives on infrastructure controlled by companies whose interests regularly diverge from the publishers they host — is worth examining directly.
The alternative is not to abandon platforms. It is to use them differently, from a foundation of owned infrastructure.
What “Owning Your Infrastructure” Actually Means
Owning your publishing infrastructure means the core of your operation — your content, your archive, your subscriber list, your publication’s identity — lives on systems you control, not on systems you access by permission.
In practical terms:
- Your primary publication lives on a domain you own, hosted on a server or service where you have full data access and portability
- Your subscriber and reader data lives in systems you control or can export cleanly
- Your content archive is yours — in files you can move, republish, and build from independently
- Platforms (social media, newsletters, syndication) are distribution channels you use, not the foundation you build on
The distinction matters when platforms change. If your primary audience lives on someone else’s platform, a policy change or account action can cut you off from readers you spent years building relationships with. If your primary publication is yours, platforms become amplification tools rather than existential dependencies.
The Static Site Approach
Static site generators — Hugo, Eleventy, Jekyll, Astro — represent the most radical version of owned publishing infrastructure. Your content is files. Your site is files. Hosting is cheap or free and trivially portable.
A publication built on Hugo lives in a Git repository. The full content archive is Markdown files. The site can be rebuilt from those files on any hosting provider in minutes. There is no database to migrate, no proprietary format to escape, no hosting lock-in.
The tradeoffs are real — no browser-based editing, no dynamic features without third-party services, a technical barrier to entry — but for publishers willing to work within those constraints, the operational independence is genuine.
Self-Hosted WordPress
WordPress is not a platform in the sense that social media companies are. WordPress.org is open-source software you run on your own hosting. Your data is in a database you control and can export. Your content is yours.
The distinction between WordPress.com (a hosted platform with its own terms and restrictions) and a self-hosted WordPress.org installation is important and often elided. A self-hosted WordPress site, properly backed up and on hosting you control, is owned infrastructure in the meaningful sense.
The calculus changes if your publication lives on WordPress.com’s higher tiers, Ghost Pro, or other managed platforms. These are quality services, but they are platforms — the distinction is that portability and control, while present, require deliberate exit planning.
Your Subscriber List
If you are building a reader relationship, your subscriber list is the most valuable asset you have. It is also the most commonly platform-dependent one.
A list built through a newsletter service you own the export for is an asset. A following on social platforms where you cannot export your followers is not — it is an audience you are renting access to.
Prioritize building a directly owned email list. Whatever newsletter service you use — Mailchimp, ConvertKit, Beehiiv, Ghost, self-hosted Listmonk — confirm that you can export your subscriber list completely at any time. This should be a precondition of committing your audience development to any platform.
A Practical Stack for Owned Publishing
An indie publisher who wants genuine infrastructure ownership might operate with:
- A Hugo or self-hosted WordPress site on their own domain — the primary publication
- A self-controlled email list (export confirmed, ideally running through a provider with strong portability)
- Social media used for distribution and discovery, not as primary publication venues
- Content in formats they own — Markdown, HTML, standard export formats rather than proprietary systems
This is not a rejection of platforms. It is a structural choice to use them from a position of independence rather than dependency.
The Longer View
Publications that survive algorithmic shifts, platform closures, and industry disruption tend to share a characteristic: the core of their operation was theirs. They adapted distribution strategy when platforms changed, because their content, their readers, and their publishing infrastructure were not hostage to any single platform’s decisions.
Independent publishing has always required some combination of stubborn commitment and strategic flexibility. Getting the infrastructure foundation right is what makes flexibility possible when you need it.