Sub.club is no longer operating. Launched on August 29, 2024, by the team behind the Mammoth Mastodon app, it attempted to create a subscription and payment layer for the fediverse. On December 13, 2024, the company announced that it was winding down the service and expected its feeds to stop working by the end of January 2025.
Its short-lived model is still worth examining because it addressed a real financial problem: how creators, bot operators, publishers, and community-run servers might earn recurring income without moving their audiences entirely to a separate platform.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
RSS Feed Reader | Buy on Amazon | |
| 2 |
|
Feed RSS Reader | Buy on Amazon | |
| 3 |
|
UOKIK RSS Feed Reader | Buy on Amazon | |
| 4 |
|
Norfolk RSS Feed Reader | Buy on Amazon | |
| 5 |
|
Freader - RSS Feed Reader | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What Sub.club was trying to do
Mastodon and other ActivityPub services are distributed across independently operated servers. Those servers and the people who create content on them have traditionally relied on donations, grants, merchandise, sponsorships, Patreon, and other external funding tools.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThat does not mean the fediverse had no monetization. The gap was more specific: there was no widely adopted, built-in way to connect a paid subscription with exclusive posts delivered through a user’s existing fediverse account.
#1 Best Overall
- Internet connectivity
- Displaying RSS feed
Sub.club aimed to fill that gap. Its stated thesis was that a creator could charge for premium content, while the subscriber could read that content in a Mastodon-compatible client instead of visiting a separate membership website for every post.
The service came from The Blvd. Inc., the company associated with Mammoth. Mammoth co-founder Bart Decrem argued that the ActivityPub ecosystem needed additional resources. The project was not a Mastodon Foundation product, an ActivityPub standard feature, or a decentralized payment protocol. It was a commercial service built around fediverse identities and delivery infrastructure.
How the premium-feed model worked
At launch, the historical subscription process generally followed this path:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches- A creator created a Sub.club account and connected Stripe.
- The creator selected a subscription price. A reported example was $3 per month, but prices were set by individual creators rather than by Sub.club.
- The creator linked the paid service to a fediverse identity or feed.
- A prospective subscriber clicked the creator’s subscription link and entered the domain of their Mastodon instance.
- Sub.club requested authorization through Mastodon. Contemporary coverage described the access as read-only account access and write-only access related to follows.
- The subscriber completed payment on the web through Stripe.
- Sub.club sent a welcome message, followed by premium posts through private mentions or a private ActivityPub feed.
- Cancellation could be initiated by sending a private message containing “unsubscribe.”
That workflow was historical. It should not be treated as a live setup guide: Sub.club announced its wind-down only a few months after launch.
TechCrunch described the broader product as an ActivityPub-compatible feed that could be consumed from Mastodon clients, with an API intended to let apps integrate subscription feeds. In practice, compatibility at the protocol level did not guarantee identical support or a dedicated subscription interface in every client.
What Sub.club charged
Launch coverage reported a 6% Sub.club transaction fee. TechCrunch compared that with Patreon platform cuts of 8% and 12% for plans available at the time. Those Patreon figures were historical August 2024 comparisons, not current pricing.
Rank #2
- Read your RSS feeds and discover other by keywords
- Fast and simple interface
- Resizable Widget
- Dark and white layout
- Share content easily
The 6% figure also should not be interpreted as a complete cost-of-doing-business calculation. Payment processing, taxes, refunds, chargebacks, and any other applicable costs could affect a creator’s actual economics. The available launch reporting established Sub.club’s stated platform fee, not a universal net payout after every expense.
TechCrunch also reported planned tools for server owners that would initially waive Sub.club’s and Stripe’s fees for the first 90 days. Because the service shut down, that was a launch-era promise rather than an enduring offer.
Why it was different from Patreon
The important distinction was not simply that Sub.club advertised a lower platform fee. The products occupied different positions in the creator economy.
| Sub.club’s intended model | Patreon-style model |
|---|---|
| Payment and access layer connected to fediverse accounts | Centralized creator-membership platform |
| Premium posts delivered through compatible social feeds | Content generally consumed on the membership platform |
| Potential integration into Mastodon clients | Established creator pages, tiers, analytics, and membership tools |
| ActivityPub-oriented delivery | Centralized account and publishing infrastructure |
| Young service with limited operating history | Larger installed base and more mature operations |
Sub.club was therefore closer to a back-end service than to a full replacement for Patreon. It did not appear designed to provide Patreon’s entire combination of discovery, creator pages, audience management, analytics, and community tools.
Its appeal was convenience and context: subscribers could use an existing fediverse account, while creators could potentially keep paid posts close to their ordinary social publishing workflow.
Who might have used it?
The model was aimed at more than individual social-media creators. Potential use cases included:
Rank #3
- free app
- help to read news
- Creators: exclusive updates or commentary delivered to paying followers.
- Bots: premium alerts, data feeds, or specialized automated services.
- Publishers and writers: paid articles or posts distributed through fediverse accounts.
- Server operators: recurring support for community infrastructure.
- App developers: native subscription experiences built into Mastodon clients.
The distinction between these use cases matters financially. Funding a server’s operating costs is not the same product as selling premium content. Likewise, a private creator subscription has different tax, refund, governance, and trust implications from a community membership.
Integrations showed the broader ambition
Mammoth planned to add a subscription button, and Ice Cubes was identified as the first third-party Mastodon app to implement subscription feeds. Sub.club also offered an API for app developers.
The service later reached beyond short social posts. Write.as integrated Sub.club for premium blogs, allowing publishers to mark part of a post as paid content with a <!--paid--> marker. That was a concrete example of the service being used as a publishing and access layer rather than merely a theoretical monetization concept.
Write.as subsequently removed its Sub.club support after the service shut down. See the Write.as integration announcement and follow-up for that history.
The limits of the model
Federated identity did not mean federated payments
ActivityPub could help distribute social activity, but it did not itself provide billing, refunds, fraud handling, tax reporting, entitlement checks, or customer support. Stripe handled payments at launch, while Sub.club handled the subscription relationship and content access.
In other words, Sub.club used a federated social environment while retaining centralized commercial infrastructure. Calling it decentralized payments would have been misleading.
Rank #4
Private delivery was not perfect access control
A private mention or private feed could make premium content convenient to deliver, but it was not digital-rights-management technology. Subscribers could copy, forward, screenshot, or redistribute posts. Creators considering any social-feed subscription would need to treat the system as access control, not a guarantee against sharing.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Client support depended on adoption
An ActivityPub-compatible feed could theoretically be consumed across compatible services, but a polished experience depended on individual app developers implementing the relevant API or subscription metadata. A user’s preferred Mastodon client might not offer the same controls as Mammoth, Ice Cubes, or another integrated app.
Instance policies could affect access
Every Mastodon server has its own moderation and federation policies. Domain blocking, server rules, or other local decisions could affect whether a subscription account was visible or usable. This is a structural complication for any third-party service that depends on federated identity.
Commercial trust was part of the product
The fediverse includes strong support for open-source software, community ownership, and resistance to centralized platform incentives. Sub.club’s association with a commercial, venture-backed company could therefore prompt skepticism independently of its technical design.
That concern was not proof that the product failed, but it highlighted an important financial reality: a paid intermediary must earn trust from both creators and communities. Continuity, portability, transparent fees, and a credible shutdown plan matter as much as checkout convenience.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Why Sub.club shut down
Sub.club announced the wind-down on December 13, 2024. The announcement said creators would be fully paid, connected Stripe accounts would remain in good standing, and feeds were expected to stop working by the end of January 2025.
Best Value
- Add and manage RSS/Atom feeds by catagory
- Save favorites and custom feeds
- Share articles with friends
- Lightweight and easy to use
- Full screen video support for embedded videos in feed description and in external links
The service’s shutdown should not be reduced to the claim that “the fediverse rejected monetization.” The available evidence does not establish a single definitive cause. Possible explanations include a small addressable market, difficulty converting fediverse audiences into paying subscribers, uneven client support, operational complexity around federated access, limited time to build creator inventory, and the economics of operating a venture-backed startup with slow adoption.
A later secondary report discussed an estimate of approximately 150 people onboarded. That figure should be treated as attributed reporting rather than an independently verified official user metric.
The more defensible conclusion is narrower: one commercial premium-feed experiment launched, struggled to establish a durable service, and shut down within months. That does not prove that paid content cannot work on ActivityPub or that fediverse users categorically oppose subscriptions.
Free tools Windows power users keep installed
One-click scans. No signup required.
What the experiment teaches about online creator income
- Lower fees are not enough. Audience reach, conversion, analytics, refunds, moderation, tax support, and reliability can matter more than the headline platform percentage.
- Federated distribution and business operations are different layers. Social posts may travel across servers, while billing and entitlement decisions remain centralized.
- Portability should be a financial requirement. Creators using an intermediary should understand how to export subscriber information where legally permitted, preserve paid access, issue refunds, replace the payment processor, and update old links.
- Client compatibility is part of the customer experience. A protocol-compatible service may still be inconvenient if the user’s preferred app does not support the relevant features.
- Paid access is not the same as server funding. A premium feed benefits a creator or publisher; a donation or membership program may be more appropriate for paying a server’s operating costs.
What to use instead of Sub.club
No alternative listed below has been established here as an identical replacement for Sub.club’s ActivityPub-oriented premium-feed delivery. The right choice depends on what is being funded.
- Patreon: best suited to recurring memberships, tiers, premium creator content, and an established centralized workflow. Check Patreon’s current pricing rather than relying on the historical figures cited in 2024 launch coverage.
- Ko-fi: useful for tips, memberships, commissions, and lightweight creator support. It is not documented here as a replacement for federated premium-feed delivery.
- Open Collective: better suited to transparent funding for open-source projects, communities, nonprofits, and infrastructure than to private subscriber-only posts.
- Direct Stripe billing: potentially appropriate for organizations with technical resources. Stripe supplies payment infrastructure, not account linking, entitlement delivery, moderation, customer support, or an ActivityPub membership layer.
- Direct instance support: Mastodon server operators may use donations, memberships, grants, merchandise, sponsorships, Patreon, Ko-fi, or Open Collective to fund operating costs without creating a premium feed.
Anyone replacing a discontinued subscription service should communicate with subscribers, preserve access for already-paid periods, handle refunds appropriately, migrate recurring billing carefully, and remove obsolete links from profiles and websites.
The historical launch details are documented in TechCrunch’s launch report and a contemporaneous hands-on account and shutdown report.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
