Case No. 0152·Investigation·2,300 words

How a Free, Open-Source Tool Became a $2.7M-a-Year Business

Inside Postiz's climb from a stalled side project to one of 2026's fastest-growing bootstrapped SaaS companies

By the WebTribunal Team
10 min read
$2.7MAnnualized
run rate
$223K+Tracked MRR,
Sep 16, 2026
36KGitHub
stars
$0Price of the
self-hosted software

Sourced from TrustMRR, IdeaWave, GitHub & founder disclosures

Most social media schedulers ask you to pay before you can even try them. Postiz did the opposite: it gave the product away to anyone willing to run it themselves and built a business on top of that decision.

Founder Nevo David made the core software fully open-source, so anyone could self-host it at no cost. Customers only pay for the convenience of a hosted cloud version. That single choice turned Postiz's GitHub repository into its biggest marketing channel. The project has accumulated roughly 36,000 stars and 6,900 forks to date.

More importantly, the open-source popularity has translated into a substantial commercial business. Postiz crossed $1 million in annual recurring revenue (ARR) around April 2026, and by mid-September, independently tracked billing data put it at approximately $223,000–$225,000 in monthly recurring revenue (MRR), or roughly $2.7 million annualized.

The business is still run largely by its founder, with outside contributors helping maintain the code.

Postiz Started as a Traditional SaaS and Stalled

2022–2024

The social media scheduling market has existed for over 20 years, dominated by players like Buffer, Hootsuite, and Hypefury. Nevo David saw an opportunity to differentiate Postiz in three areas:

  • Developer flexibility – More control over APIs, integrations, and external workflows.
  • Self-hosting and data control – An option for users who didn't want a third party hosting the application and its data.
  • AI-agent workflows – APIs, CLI tools, and MCP support that let automated systems interact with the platform programmatically.

Before launching Postiz, Nevo spent ten years as a full-stack developer and team leader. In 2022, he moved into growth marketing and joined Novu, an open-source notification startup, where he helped grow its repository through developer-focused marketing and influencer strategies.

In early 2024, Nevo left Novu and spent the first half of the year building Gitroom, an open-source platform and growth consultancy for developer-focused startups to track analytics and schedule content. While running Gitroom, he noticed strong demand for a developer-friendly, open-source social media scheduler. Since Gitroom's focus was broader, he used its core engineering ideas to spin out a dedicated, rebuilt product: Postiz.

Postiz initially launched as a closed-source, proprietary SaaS. Nevo partnered with digital experience agency Peppermint to handle naming, branding, and UI design, giving it a professional look from day one.

But the standard SaaS playbook didn't work.

Without a large personal following to drive traffic, Nevo hired freelancers on Upwork to buy backlinks and write SEO content. He soon realized a solo founder couldn't compete on Google against multi-million-dollar companies that had owned social media keywords for decades. Traffic stayed near zero, and the business stalled. The few users he acquired churned at a punishing 17% per month, a rate that would have sunk the business.

On September 1, 2024, Nevo made the entire Postiz codebase public. It was first released under the Apache-2 license, then later relicensed to AGPL-3.0. This wasn't new territory for him. He had already helped scale Novu's open-source community, so he knew developers and self-hosters made an engaged, passionate audience. Going free and self-hosted also let him sidestep the SEO competition entirely. It put the product directly into the hands of technical users running it via Docker.

The open-source release gave Postiz a new distribution channel. A few months later, its November 2024 Product Hunt launch ranked #1 Product of the Day, Week, and Month. The GitHub repository subsequently passed 14,000 stars, while Docker downloads climbed into the hundreds of thousands.

But registrations weren't the same as retention. To fix the churn problem, Nevo repositioned the product as "Postiz-as-a-Service," building out API access and webhooks so other companies could embed Postiz directly into their platforms as a white-labeled solution.

From Open-Source Project to SaaS Business

The open-core model

Postiz runs on an open-core model: a free, self-hosted layer paired with a paid, fully-managed cloud platform.

The free, self-hosted version is available on GitHub under the AGPL-3.0 license. Users deploy it themselves via Docker, absorbing the infrastructure work, including running a Node app, PostgreSQL database, and Redis instance, plus registering their own API keys and handling OAuth renewals for each social platform.

The Cloud version provides a managed SaaS layer built on the same core, with plans ranging from $29 to $99 per month. Instead of maintaining the deployment themselves, customers pay Postiz to handle the infrastructure, updates, integrations, and uptime. It also requires a credit card to initiate a trial.

What customers pay for, in short, is convenience. Self-hosted users manage their own servers, API keys, OAuth renewals, updates, and technical failures. Cloud customers pay Postiz to handle that work for them.

The Software Is Free. Convenience Is What Postiz Sells.

Both options run on the same open-source core. The difference is who does the operational work.

Self-Hosted Postiz
Free software
  • User provides infrastructure
  • User manages servers
  • User handles API keys
  • User handles OAuth renewals
  • User manages updates and technical failures
Postiz Same open-source core+Two ways to run it
Postiz Cloud
$29–$99/month
  • Managed infrastructure
  • Updates handled by Postiz
  • Hosted integrations
  • Managed uptime
  • Support and plan-based allowances

Based on Postiz's public repository, documentation and pricing page. This compares who does the work, not plan features.

Monetization began at launch in September 2024, since the payment infrastructure had already been built during Postiz's earlier closed-source phase. Nevo simply opened the codebase while launching the paid cloud tier alongside it.

Pricing and positioning changed in stages. Postiz's revenue initially grew slowly. David has described a long stretch around $3,000–$6,000 MRR while the product competed as a conventional social media scheduler. By early 2026, revenue had moved into the low five figures, but the sharper acceleration came as Postiz repositioned itself around automation and AI-agent workflows.

By mid-2026, Postiz had accumulated over 27,000 GitHub stars and hundreds of thousands of Docker downloads. By late August, verified Stripe data showed around 5,640 paying subscriptions against roughly $191,600 MRR, still a small fraction of the free user base. David has said automated workflows churned less often than Postiz's traditional human users because API-connected customers tended to leave the service running once it became part of their workflow. Postiz has not published cohort-level retention data that would independently quantify that difference.

Open Source as Postiz's Distribution Engine

GitHub and Docker

Postiz's GitHub repository shows how widely the project has spread, but popularity and revenue are different measures.

As of September 2026, more than 80 contributors had worked on the project, while its star and fork counts continued to climb. Regular releases also show that the repository remains actively maintained.

The free Docker image also gave developers a way to build on Postiz before becoming cloud customers. One prominent example came from developer Oliver Henry, whose autonomous AI agent used Postiz to publish TikTok content that accumulated millions of views. Stories like that exposed Postiz to AI builders beyond its original social-media scheduling audience.

Separately, the Docker Compose Repository has around 7.8 million container downloads. This measures how often people deploy the software, not how many unique users there are. One person can download it many times, so downloads do not equal self-hosters, and self-hosters do not equal paying customers.

GitHub growth and paying customers increased over the same period, but no public source shows how many stars or Docker downloads converted into paying accounts. What the stars and downloads did provide was free exposure to developers, sysadmins, and AI builders, an audience that would be expensive to reach through Google ads.

The Postiz Growth Flywheel

How free code leads to paid subscriptions. Community exposure feeds back into GitHub and developer discovery.

Step 1
Open-source code
Step 2
GitHub / Docker discovery
Step 3
Developer & AI-builder adoption
Step 4
Integrations and automated workflows
Step 5
Some users choose managed Postiz Cloud
Step 6
Subscription revenue

No conversion rates are shown between stages because none exist publicly: no source shows how many GitHub stars or Docker downloads became paying accounts.

Postiz's MRR Jumped 10x in 2026

Tracked billing data, Jan–Sep 2026

According to daily billing data independently tracked by TrustMRR and IdeaWave, Postiz's MRR grew from roughly $21,000 in January 2026 to more than $83,000 by April, when it crossed the equivalent of $1 million ARR. Growth continued to more than $158,000 by July 2, $168,700 by July 13, and $181,000 by August 1.

By September 9, tracked MRR stood at approximately $207,500–$209,500. On September 16, both trackers were close to $223,000–$225,000 MRR, equivalent to roughly $2.7 million annualized. The two services generally tracked within about 1% of each other.

Unaudited

Postiz MRR Grew More Than 10x in 2026

Monthly recurring revenue at the seven readings cited from TrustMRR and IdeaWave, placed on a to-scale 2026 timeline.

$0 $50K $100K $150K $200K $250K January 2026: about $21,000 April 2026: more than $83,000 July 2, 2026: more than $158,000 July 13, 2026: $168,700 August 1, 2026: $181,000 September 9, 2026: approximately $207,500 to $209,500 September 16, 2026: approximately $223,000 to $225,000 ~$21K >$83K >$158K $168.7K $181K ~$207.5K–$209.5K ~$223K–$225K JAN MAR MAY JUL SEP 2026 Tracked MRR at seven cited readings, January to September 16, 2026
Cited MRR reading Straight lines between readings, not daily data

January and April are cited by month only and are plotted mid-month. The two September readings are ranges and are plotted at their midpoints; the labels show the full range. Figures come from TrustMRR and IdeaWave, which read Postiz's billing data. They are not audited accounts and have not been independently verified by WebTribunal. The founder's own updates run roughly 8–10% lower on comparable dates.

Nevo David's own public updates on X and the official Postiz blog describe a somewhat lower trajectory over the same period. He reported $145,000 MRR on July 2, $154,000 on July 13, $159,000 on July 20, and $190,000 by September 9, each roughly 8–10% below what the independent trackers show for the same dates. These founder-reported figures are unaudited and consistently run below the tracked figures on comparable dates. The public sources do not explain whether the gap comes from reporting lag, rounding, different MRR definitions, or another accounting difference.

AI demand alone doesn't explain the acceleration. The available record points to a more specific trigger.

According to Nevo, Postiz plateaued at $3,000–$6,000 MRR for a long stretch in 2025 while competing head-on with Buffer and Hootsuite on generic scheduling features. The shift began when he pivoted toward automation, taking MRR from $6,000 to $12,000 in a single month. The bigger jump came when OpenClaw, an AI agent framework, launched: he adjusted his marketing around it and grew from $21,000 to $70,000 MRR in roughly two months. This is the clearest single trigger point in the available record, a specific product launch he moved quickly to build around, rather than a gradual drift toward AI positioning.

David also built around emerging automation tools early. Postiz added an n8n integration while the platform was gaining traction, followed by an MCP server that let compatible AI systems connect directly to Postiz. When interest in AI agents accelerated, the infrastructure was already in place.

Nevo stated that growth came from a deliberate mix of unpaid channels: four separate Product Hunt launches, regular posts to r/selfhosted that reportedly drew around 100,000 views each time, N8N workflow templates, official skills listed on marketplaces like Claude's and GitHub's "awesome" lists, and collaborations with other creators on X, plus standard SEO and backlink work. None of it relied on paid advertising.

Meanwhile, the product itself kept improving in the background. Recent GitHub release notes show steady updates: faster video uploads, fewer duplicate posts, ongoing bug fixes, and new platforms added, including Tumblr and MeWe.

David has attributed much of the acceleration to organic distribution rather than paid advertising, including Postiz's open-source community, Product Hunt launches, Reddit posts, workflow templates, integrations, creator collaborations, and developer word of mouth.

Competing in a Mature SaaS Market

Postiz vs. Buffer and Hootsuite

Postiz's core bet, giving away the product that Buffer and Hootsuite charge for, only works if it can still compete against incumbents with 16–18 years of brand recognition, established customer relationships, and mature product ecosystems. Hootsuite advertises more than 100 integrations and support for more than 20 social networks, alongside connections to CRM, project-management, and marketing tools. Buffer offers a free plan, paid tiers, collaboration features, and agency-oriented pricing for teams managing multiple client accounts.

The two sides aren't really selling the same thing. Buffer and Hootsuite primarily monetize access to their hosted software. Postiz makes its core software available for self-hosting and monetizes the convenience of its managed Cloud version. The table below makes that split concrete.

Postiz vs. Buffer / Hootsuite

Core software · PostizOpen-source and self-hostable under AGPL-3.0.
Core software · Buffer / HootsuiteProprietary, primarily vendor-hosted SaaS products.
Free offering · PostizFree self-hosted software; users supply infrastructure and operate the deployment.
Free offering · Buffer / HootsuiteBuffer offers a free plan; Hootsuite's current offering is primarily subscription-based.
Network support · PostizBroad support for social and publishing channels.
Network support · Buffer / HootsuiteHootsuite advertises 20-plus social networks and more than 100 integrations.
Primary acquisition channel · PostizGitHub, developers, automation communities, and integrations.
Primary acquisition channel · Buffer / HootsuiteBrand recognition, search, content, partnerships, paid acquisition, and established customer relationships.
Revenue source · PostizManaged Cloud subscriptions, currently listed at $29–$99 per month, plus related services.
Revenue source · Buffer / HootsuiteSubscription revenue from hosted software and plan-based features.
Target workflow · PostizHuman dashboard use plus programmatic automation through API, CLI, and MCP.
Target workflow · Buffer / HootsuitePrimarily human-operated social-media management dashboards, with growing developer and automation capabilities.

Postiz Cloud currently lists Standard, Team, Pro, and Ultimate plans at $29, $39, $49, and $99 per month. The plans differ by channel limits, webhooks, team features, AI-generation credits, and other allowances. The documentation also states that there is no free Cloud plan, although new organizations may receive a trial.

That split helps explain how Postiz can open-source its core product while still generating subscription revenue. Self-hosted users can adopt and operate the software themselves, while customers who value convenience pay for managed infrastructure, updates, hosted integrations, support, and plan-based allowances.

Because the source code is publicly available, GitHub and developer communities also function as a discovery and adoption channel, though, as noted earlier, stars and forks shouldn't be treated as equivalent to active users or paying customers.

Postiz's positioning differs from the traditional dashboard-centered model in one more way: it provides a public API, CLI, and MCP server for programmatic workflows, with its MCP documentation describing AI agents listing integrations, scheduling posts, and generating media through a standardized tool-calling interface. That gives Postiz a sharper emphasis on developers, automation builders, agencies, and AI-agent workflows. It isn't proof that Buffer or Hootsuite can't compete here; it's a focused positioning opportunity while they haven't.

The model still carries real risks. Self-hosted users may never convert into Cloud customers. Cloud margins may be pressured by infrastructure, AI-generation, and social-platform API costs. And because the code is open, established competitors could copy the AI-agent features and distribute them to much larger existing customer bases. Postiz's edge has to come from more than the code itself: reliability, documentation, integrations, developer adoption, support, and a strong ecosystem.

The Real Product Was Convenience

Analysis

Postiz didn't make money by putting its software behind a paywall. It used free, open-source software to expand its reach, then monetized the users who wanted the convenience of the hosted product.

The contradiction is simple: giving away the core product while building a multimillion-dollar business. Open source became Postiz's distribution engine, turning GitHub stars, Docker downloads, and developer word-of-mouth into a funnel that traditional SaaS companies would have to buy with ads and SEO. Revenue came not from locking features away, but from selling relief from operational friction: no servers to maintain, no API keys to juggle, no breaking OAuth flows to debug.

The bigger question is whether AI agents represent another distribution layer for the business rather than simply another feature. David argues that AI-driven workflows are stickier once Postiz becomes embedded through its API, CLI, or MCP integrations. If that pattern holds as the customer base grows, Postiz could become less of a tool customers periodically evaluate and more like infrastructure their automated workflows depend on.

Resources

Every figure traces back to one of these
Have documents on Postiz?
Board decks, billing exports, contracts, internal dashboards. We read everything, we protect sources, and we tell you first what we intend to do with it.
Reach the tip line