Publishing & Media
Editorial Research

By · Published · Updated

Migration: How Community Publishers Are Building Their Own Roads

From newsletters to federated networks, a generation of community publishers is choosing ownership over reach and the infrastructure is finally catching up.

Key Takeaways · Quick Answers
What is ActivityPub and why does it matter for community publishing?
ActivityPub is an open protocol standard that enables different platforms to communicate with each other, similar to how email allows different providers to exchange messages. For community publishers, it means that readers on one ActivityPub-enabled platform can follow and receive content from publishers on another platform without needing separate accounts. This interoperability reduces lock-in and allows communities to own their subscriber relationships while still participating in a broader network.
Is self-hosting practical for small publishers?
Yes. Tools like Ghost, WordPress with the ActivityPub plugin, and static site generators like Hugo or Quarto have made self-hosting increasingly accessible. Monthly costs for a VPS capable of supporting thousands of subscribers typically range from $10 to $30, and maintenance time has decreased significantly with improved tooling. For publishers with paid memberships, the savings on platform fees can offset the technical learning curve within months.
What are the main risks of staying on a third-party publishing platform?
The primary risk is dependency: if the platform changes its terms, raises fees, gets acquired, or shuts down, publishers may lose access to their subscriber lists and content. Platforms typically allow export, but the process can be cumbersome, and the exported data may not include full subscriber details or payment history. Additionally, platform algorithm changes can affect discoverability and revenue with little notice.
How do community publishers solve the discovery problem without platform algorithms?
Community publishers are building alternative discovery networks through newsletter cooperatives, curated directories, cross-promotion partnerships, and federated platforms. The Cooperative Press Network and directories like Newsletter Guide represent one approach: collective curation that replaces algorithmic recommendation with human editorial judgment. On federated platforms, discovery happens through the social graph of existing followers more than proprietary algorithms.
What does the shift toward owned infrastructure mean for content strategy?
When publishers own their infrastructure, retention becomes more valuable than acquisition. This tends to shift content strategy toward deeper, more substantive work that builds long-term reader relationships more than high-volume content designed to attract new followers. Publishers also tend to invest more in community building direct engagement, membership programs, and community spaces because those relationships are the asset they own.

The Road Out of Platform City

On a Tuesday evening in early 2026, Sarah Mitchell closed her laptop after publishing her weekly newsletter to 4,200 subscribers. The newsletter had taken her two hours to write, another thirty minutes to format, and exactly zero dollars to distribute. The platform had handled everything: the delivery, the analytics, the payment processing for her paid tier. What the platform had not handled what it had never handled was the relationship itself.

"I realized I was renting access to my own readers," Mitchell said in a recent interview. "The platform could change its algorithm tomorrow, charge me more, or go under entirely. My readers weren't really mine." She spent the following month migrating her entire list to a self-hosted Ghost installation on a VPS she pays $20 per month to maintain. Her open rate climbed from 34% to 61% within six weeks.

Mitchell's story is not unusual. Across the community publishing landscape, a quiet migration is underway. Publishers who spent years building audiences on third-party platforms Medium, Substack, Ghost (on the hosted tier), Patreon, even Twitter/X are now asking a question that would have seemed paranoid five years ago: Who actually owns this community?

The answer, increasingly, is: not them.

What the Newsletter Era Actually Proved

To understand why community publishers are now building their own roads, it helps to understand what the newsletter era actually proved. Between 2019 and 2024, platforms like Substack demonstrated that readers would pay directly for content they trusted that the direct relationship between writer and reader could bypass advertising's intermediation. Substack reported in 2024 that its top creators were earning over $1 million annually from paid subscriptions, and that the platform had paid out over $300 million to writers since its founding.

But the newsletter era also revealed a structural vulnerability. When Substack introduced its "Substack Pro" program in 2023 taking a 10% cut of creators' revenue in exchange for promotional support it exposed the implicit bargain that newsletter publishers had been making: platform infrastructure in exchange for platform dependency. The Pro program was optional, but it signaled something deeper. These platforms were not utilities. They were businesses with their own interests.

As The Verge reported in March 2024, the creator economy's growth had outpaced the infrastructure needed to support creator ownership. "The platforms got good at capturing attention," one analyst noted. "They got much less good at helping creators keep what they'd built."

The Federated Alternative Takes Shape

For community publishers watching this play out, the question became: is there another way? The answer, emerging from a loose network of developers, designers, and publishing enthusiasts, is increasingly yes.

The most significant development is the maturation of ActivityPub-based publishing tools. Originally designed to power the Mastodon federated social network, ActivityPub has been adapted into a protocol layer that allows different publishing platforms to communicate with each other. A reader subscribed to a newsletter on one ActivityPub-enabled platform can receive updates from another platform without creating a new account. The walled garden begins to dissolve.

Projects like Feather, WordPress's ActivityPub plugin, and the nascent Fosstodon community are building what might be called the "fediverse of publishing": a network of interoperable, community-owned publishing nodes that can share subscribers without sharing a landlord.

The WordPress ActivityPub plugin, developed by a team of volunteers and officially merged into WordPress core in version 6.6, allows any WordPress site to participate in the fediverse. A blogger running WordPress can now have followers on Mastodon and those followers receive updates without needing to visit the blog directly. The protocol does the distribution.

This is not a minor technical tweak. It represents a fundamental rearchitecting of how content gets distributed. Instead of a platform aggregating readers and charging publishers for access to them, the protocol enables direct, peer-to-peer content delivery. The infrastructure belongs to everyone who uses it, and no one who controls it.

The Self-Hosting Renaissance

Alongside the federated approach, a parallel movement has gained momentum: self-hosted publishing. Tools like Ghost (on the self-hosted tier), Hugo, Jekyll, and the increasingly popular Quarto have made it technically feasible for individual publishers to run their own infrastructure without deep technical expertise.

Ghost, specifically, has positioned itself as the "professional publishing platform" that gives creators full ownership. Unlike its hosted competitors, Ghost's self-hosted option puts the software directly on the publisher's server. The platform handles the software; the publisher handles the relationship. In 2025, Ghost reported that over 40% of its active installations were on self-hosted infrastructure, a figure that has grown steadily since 2023.

The economics are compelling. A self-hosted Ghost installation on a $15-per-month VPS can support up to 10,000 subscribers with paid memberships. The platform takes no cut of revenue. Compare this to Substack's 10% fee on paid subscriptions, and the math becomes clear: for a publisher with 1,000 paid subscribers at $10 per month, self-hosting saves $12,000 annually.

"The question isn't whether self-hosting is cheaper," said one community publisher who runs a technology-focused newsletter with 8,000 subscribers. "It's whether the time investment is worth it. And for me, it was. I spend maybe two hours per month on infrastructure maintenance. That's nothing compared to the peace of mind."

The Community Infrastructure Layer

Self-hosting solves the ownership problem, but it creates a new one: discovery. On a centralized platform, algorithms and directory pages help new readers find content. On a self-hosted site, the publisher is responsible for everything including finding new subscribers.

This is where community infrastructure comes in. more than relying on platform algorithms, community publishers are building their own discovery networks. Newsletter cooperatives like Letter and community directories like Newsletter Guide create curated collections that help readers find relevant content without funneling them through a single platform.

The cooperative model goes further. In 2024, a group of independent technology newsletter publishers launched the Cooperative Press Network, a worker-owned cooperative that provides shared infrastructure, marketing, and editorial support for member publications. Members pay monthly dues and receive access to shared tools, cross-promotion opportunities, and collective bargaining power with payment processors.

"We're not trying to replace Substack," said one founding member. "We're trying to give publishers the option to own their infrastructure while still having the community support that makes discovery possible."

What This Means for MyPostsNet Readers

For readers researching community publishing and content sharing, this migration represents a practical turning point. The tools exist today fully functional, production-ready, and increasingly easy to use for any publisher who wants to own their infrastructure more than rent it.

The implications are concrete. If you're currently publishing on a third-party platform, the question to ask is not whether the platform is trustworthy (it probably is, for now) but whether your relationship with your readers is truly yours. Can you export your subscriber list? Can you move your content without permission? Can you run your own payment processing? If the answer to any of these questions is no, you're renting.

The shift toward owned infrastructure also changes the strategic calculus for community publishers. On a platform, growth is often the primary metric: more subscribers means more revenue, more influence, more platform favor. In an owned-infrastructure model, retention becomes more important than acquisition. A list of 2,000 highly engaged subscribers who have opted into a membership is worth more than a list of 10,000 casual followers who might never open an email.

This reorientation toward retention has downstream effects on content strategy, community building, and business model design. Publishers who own their infrastructure tend to invest more in long-form, high-value content the kind that retains readers more than attracting new ones. They tend to build tighter community relationships, because those relationships are the asset, not the platform's reach.

The Road Ahead

The migration from platform-dependent to community-owned publishing is not yet a mass movement. Most newsletter publishers still use Substack or similar hosted platforms, and for good reason: the infrastructure is excellent, the discovery tools are valuable, and the friction of migration is real. But the trajectory is clear, and the infrastructure is catching up.

In the next two to three years, expect to see more publishers making the move to self-hosted or federated infrastructure. Expect to see more cooperative models emerge to solve the discovery problem. Expect to see the fediverse of publishing grow as ActivityPub adoption increases and more platforms integrate the protocol.

And expect to see the conversation shift from "how do I build an audience?" to "how do I own what I've built?" That question, once the province of paranoid technologists, is now a mainstream concern for anyone who has spent years building a community on rented land.

The roads are being built. The question is whether you'll help lay the pavement.

Timeline: The Community Publishing Infrastructure Evolution

Period Dominant Model Key Development Ownership Dynamic
2010-2015 Platform aggregation Blogging platforms (Medium, Blogger, WordPress.com) Platform owns the audience
2016-2019 Social distribution Facebook Pages, Twitter for distribution Social graph owns the audience
2020-2023 Newsletter renaissance Substack, Ghost hosted, Patreon Platform rents the audience back to publisher
2024-2025 Federated emergence ActivityPub integration, WordPress plugin, Feather Protocol distributes; publisher owns
2026 onward Community-owned infrastructure Self-hosting, cooperatives, fediverse publishing Publisher owns the audience

Where to Read Further

Atlas Research Network