In the summer of 2025, Postiz — an open-source social media scheduler built and run by a single developer, Nevo David — was stuck at a plateau most bootstrapped founders would be thrilled to hit and unable to see past: somewhere between $17,000 and $21,000 in monthly recurring revenue, new signups flattening, churn creeping up. Then Nevo shipped a command-line tool and a small connector protocol most of his human users would never directly touch, aimed not at people but at the AI agents starting to act on their behalf. Within about two months, an Indie Hackers writeup documents revenue climbing from roughly $21,000 to $70,000 a month. By April 2, 2026, the company had crossed $1 million in annualized recurring revenue. It kept climbing from there. As of this piece’s research, Postiz’s Stripe-verified monthly recurring revenue sits above $160,000, across nearly 5,000 paying subscriptions.

Nothing about the product changed for the humans still scheduling their own Instagram posts with it. What changed is who else could use it.

Here’s how an open-source scheduler with no sales team, no ad budget, and one full-time founder actually got there — and which parts of it you can use even if you’re not building the next AI-agent tool.

The wedge: an old category, and a license used as a weapon

Before Postiz, Nevo David had already failed at one startup and helped grow someone else’s.

The failure was Linvo, a LinkedIn automation tool — bots handling connection requests, messages, and posting — that he built and ran alone starting around 2021. Linvo made real revenue. It also had a burn problem that had less to do with market demand than with infrastructure: a single developer keeping a stack of cloud servers and job queues alive, patching the same category of failure on repeat, with no second engineer to share the load. Nevo has written about the experience under a blunt headline — he sold the company, worn down less by the market than by his own system’s persistent instability. The lesson wasn’t “automation tools don’t work.” It was narrower and more useful: a good idea, built alone on fragile infrastructure with no plan for distribution, isn’t yet a business.

The correction came at Novu, an open-source notification-infrastructure startup, where Nevo spent roughly a year — 2022 into 2023 — as a growth hire. He wasn’t writing the core product; he was running community programs (a hackathon called HackSquad, an ambassador program called Community Heroes) and treating the open-source repository itself as the top of the marketing funnel rather than a footnote to it. Novu passed 30,000 GitHub stars during that stretch. What Nevo has since said he took from the experience is close to a single idea: building a good product and distributing it are two different jobs, and open source only compounds when someone works the second job as hard as the first.

That’s the playbook he ran back on his own, launching Postiz as an open-source project on September 1, 2024.

The category he picked was old and, on paper, unpromising. Social media scheduling has existed for roughly two decades, dominated by Buffer, Hootsuite, and a long tail of near-identical tools, most gating ordinary features behind $99–$199/month plans. What none of them had done was open-source the product. Postiz’s wedge wasn’t a new feature — it was structural: publish the whole thing, let anyone self-host it free with full feature parity, and sell a hosted cloud version to people who’d rather pay than run a server themselves.

The detail worth sitting with, if you’re a developer weighing the same kind of bet, is the license — because it isn’t the one Postiz launched with. Postiz shipped in 2024 under Apache 2.0, a permissive license that lets anyone, including a well-funded competitor, fork the code, modify it, close the modifications, and sell a hosted rival with zero obligation to give anything back. At some point in the following year — the exact date isn’t independently documented, though the project’s current license file carries a 2025 copyright notice — Postiz relicensed to AGPL-3.0, which is what it ships under today. That’s not a cosmetic swap. Ordinary copyleft licenses like the GPL only trigger their share-your-changes obligation when you distribute the software, and running modified code as a hosted web service has never legally counted as “distribution” — which is why plenty of companies have built closed, proprietary SaaS businesses on top of GPL’d code without open-sourcing a line of their own changes. The AGPL closes exactly that gap: run a modified version of an AGPL project as a network service, and you’re obligated to offer your modified source to the people using it. A competitor can still fork Postiz today. They can even sell a hosted version of it. What they can’t do is fork it, improve it, and keep those improvements proprietary while competing with the original for the same hosted-customer dollar. It’s the same logic Mastodon runs on, for the same reason, and it’s a decision that tends to only matter once an open-source project’s hosted version has become a revenue line worth protecting — which, by 2025, Postiz’s clearly was.

How the first customers actually showed up

Postiz didn’t find its early users through a sales team or paid acquisition — there wasn’t either. It found them through a coordinated open-source launch, and then the compounding weight of the repository itself.

Nevo timed the release to land across several developer-facing channels in the same window: GitHub’s trending page, Hacker News, Reddit’s r/selfhosted — where developers gather specifically to evaluate tools like this one — Lemmy, and a set of technical-writing platforms (Dev.to, Medium, Hackernoon) where he published the build-in-public story himself rather than waiting for someone else to cover it. Roughly six weeks later, on November 20, 2024, he launched on Product Hunt and took #1 Product of the Day, Week, and Month, with upvotes reported between roughly 1,200 and 2,000 depending on the source.

None of that is revenue by itself — stars and upvotes aren’t dollars. But for a self-hostable product, they compound into something that matters more: by January 2025, Postiz had around 15,000 GitHub stars and had reportedly been pulled from Docker Hub more than 584,000 times, alongside its first meaningful cloud revenue — a modest $2,000 in monthly recurring revenue, up from roughly $700 a few months earlier. The GitHub repository has stayed Postiz’s single largest source of referral traffic since, ahead of every paid channel, every social platform, and every search term other than the product’s own name. For a product built this way, the repo isn’t a technical artifact sitting next to the marketing. It is the marketing.

The growth machine

Two different mechanics did the work here, roughly a year apart. The first is the slower, durable one that’s still running today. The second is the one that changed the company’s trajectory in a matter of weeks.

The self-hosted-to-cloud funnel

The open-source release was never a lead-gen gimmick sitting in front of a crippled free tier — and that detail is what makes the rest of the funnel work. Postiz’s self-hosted version runs the same codebase as the paid cloud product, with no feature held back for paying customers. That’s a deliberate, slightly counterintuitive choice: it means Postiz can’t monetize by withholding functionality, so it has to monetize by removing friction instead.

Self-hosting a tool like this carries real friction, even for developers comfortable with Docker. Postiz connects to more than 20 social networks — Instagram, TikTok, LinkedIn, X, Reddit, Bluesky, Mastodon, and others — and each one requires its own developer-portal application, its own API keys, its own OAuth approval, sometimes its own review queue. Running the free version means becoming the person responsible for provisioning a server, registering and maintaining a stack of third-party credentials, and keeping all of it patched and online. That’s a reasonable trade for someone who wants full control or has a compliance reason to keep everything in-house. It’s a bad trade for almost everyone else — including a lot of the same developers, on a different day, with less patience. The $29–$99/month cloud tiers aren’t selling extra capability; they’re selling the removal of that maintenance job. That’s the opposite of how most SaaS free tiers are built, and it’s a meaningful part of why the free tier here doesn’t cannibalize the paid one as hard as you’d expect.

The other half of the funnel runs in the opposite direction. Larger organizations that need to keep everything on their own infrastructure, for security or compliance reasons, self-host by default — and pay Postiz directly for support and custom implementation instead of a subscription. That segment only exists because the open-source option is real and fully featured; you can’t sell “help me run my own instance” if there’s no instance worth running.

Underneath both halves sits a content engine built the same way the GitHub repo compounds: Nevo turns his own video walkthroughs into written posts (transcribed, clipped, republished across Dev.to, Medium, and Hackernoon), posts build-in-public revenue updates on X and Reddit on a near-daily cadence, and reinvests cloud revenue into backlinks and directory listings instead of paid search. None of this is exotic on its own. What’s notable is doing it continuously for two years rather than treating launch week as the whole marketing plan.

The agent-ready pivot

By the middle of 2025, the funnel above had done its job and stalled. Postiz was sitting around $17,000 to $21,000 in monthly recurring revenue — a real, profitable business, and also a plateau.

What changed it was a positioning bet, not a new product. Postiz already had a working public API, built earlier for people wiring it into Zapier, Make, and n8n automations — which meant the plumbing an AI agent would eventually need already existed by the time the moment arrived. As autonomous agent frameworks moved from novelty to a real developer audience through 2025 — OpenClaw, an open-source personal-agent framework with its own skills marketplace, prominent among them — Nevo repositioned Postiz’s entire framing: not a scheduler a person uses, but infrastructure an agent can act through on a person’s behalf. He shipped a command-line interface specifically so an agent didn’t have to construct verbose JSON requests to schedule a post — a short CLI command costs an agent far fewer context tokens than hand-building a REST call, which matters when every token an agent spends is latency and money. He built a Model Context Protocol server so Claude- and ChatGPT-style assistants could call Postiz as a tool directly. And he got Postiz listed in the places agents and their builders actually go looking for capabilities, OpenClaw’s skills hub among them.

The catalyzing moment, by Nevo’s own account, was a piece of content he didn’t write: someone else’s writeup demonstrating an autonomous agent scheduling social posts through Postiz spread widely inside the agent-developer community. “My revenue just exploded once I started sending to agents,” he told Mixergy’s Andrew Warner — a podcast worth citing specifically because Warner is known for pushing guests past the polished version of a story toward the actual numbers. The climb from there is dated, if not perfectly granular: from roughly $21,000 in mid-2025, an Indie Hackers writeup documents Postiz passing $70,000 in monthly recurring revenue within about two months of shipping the CLI and MCP server. By April 2, 2026, the company had crossed $1 million in annualized recurring revenue. It kept compounding afterward — past $110,000 by June 2026, past $145,000 not long after, and, as of this piece’s research, verified directly against Postiz’s Stripe account, above $160,000 today.

Why did agents move the number that much? The mechanical explanation is a usage-pattern shift, not magic. A human scheduling their own posts logs in, schedules a batch, and leaves. An agent running a client’s content calendar, or a solo creator’s cross-posting pipeline, calls Postiz continuously and in volume — usage that drives up paid-tier consumption and, per independent growth analysis of the account, coincided with a drop in churn, because ripping out an integration an agent depends on is a bigger switching cost than canceling a tool a human occasionally remembers to open. Timing mattered as much as the engineering: Buffer, Postiz’s largest incumbent competitor, had no agent-facing integration when this wave hit. Having a working public API, a CLI, and an MCP server already built meant Nevo could ship the positioning change fast enough to own the moment rather than react to it once it was obvious to everyone. Asked how much new engineering the pivot actually took, his answer undersold it on purpose — mostly, he said, it was a matter of writing the documentation an agent needs to understand a tool: “just need to create one MD file.”

The numbers, stated plainly

  • Monthly recurring revenue: $167,620 as of July 12, 2026, per TrustMRR, which verifies revenue by syncing directly against a founder’s live Stripe account rather than accepting a self-reported figure. Trailing 30-day revenue on the same dashboard: $158,947 — the two numbers differ slightly because one is a snapshot of active subscriptions and the other includes one-time fluctuations, which is itself a small piece of evidence the tracker is pulling real transaction data rather than a single hand-typed number.
  • Active subscriptions: 4,971, same source, same date.
  • All-time cloud revenue: $724,011 since the hosted product started billing.
  • The inflection: roughly $21,000 to $70,000 in monthly recurring revenue within about two months of shipping the CLI and MCP server, per Nevo’s own build-in-public account and an Indie Hackers writeup — the steepest sustained growth stretch in the company’s history. Treat “about two months” as approximate; none of the sourcing here publishes a single day-by-day ledger.
  • Annual recurring revenue: crossed $1,000,000 around April 2, 2026, roughly nineteen months after the September 2024 launch. At the current $167,620 monthly run rate, the business is now tracking closer to $2 million annualized — worth stating plainly, because it’s easy to freeze a fast-growing company’s story at its most recent milestone and undersell what happened after.
  • GitHub stars: 33,100, with 6,200 forks, as of this piece’s research — up from around 14,000 four months after launch and 15,000 by January 2025.
  • Team size: effectively one. Nevo is the founder; public hiring signals show a single open role, in customer success, rather than an engineering team. This is a roughly $2-million-run-rate business operated by one person.
  • Pricing: four cloud tiers — $29 (Standard), $39 (Team), $49 (Pro), $99/month (Ultimate) — plus the permanently free, fully-featured self-hosted option.

What’s transferable, and what isn’t

The AI-agent wave itself isn’t repeatable. That specific, narrow window — when autonomous agents were suddenly plausible enough to be a real usage pattern, but almost no developer tool had bothered to build for them yet — has mostly closed. Ship an MCP server as your entire growth strategy today and you’re not catching a wave anyone else has missed; every serious API-first product either already has one or is building one. Copying the tactic alone, in 2026, buys you table stakes, not a five-x jump.

What is transferable is the sequence that put Nevo in a position to catch that wave at all, and it’s longer than “he got lucky with timing”:

Ship the open-source version first, and mean it. Feature parity between free and paid wasn’t a nice-to-have — it’s the reason developers trusted the project enough to star it, self-host it, and recommend it before a single dollar changed hands. A crippled free tier doesn’t earn that trust, and trust is what a solo founder is actually selling before there’s a sales team to do it instead.

Pick your license for the threat you actually have, and be willing to change it. Apache 2.0 was the right call when Postiz needed maximum adoption and had nothing yet worth protecting. AGPL-3.0 became the right call once the hosted product was a revenue line a well-funded competitor could credibly clone. That’s a sequence, not a rule — know which stage you’re in before you commit to a license, and don’t treat the first choice as permanent.

Build the boring infrastructure before you need it. The API, the CLI, and eventually the MCP server all trace back to plumbing Nevo built for Zapier and Make users well before AI agents were a growth channel. When the positioning wave arrived, he wasn’t starting from zero — he was relabeling something that already worked. That’s the part of “we shipped an MCP server in a weekend” stories that rarely gets said out loud: the weekend only works because of the eighteen months of unglamorous API work that came before it.

Treat distribution as its own job, learned somewhere real. Nevo didn’t figure out open-source distribution from first principles on Postiz — he ran it, at someone else’s company, for a year first. If you don’t have that experience somewhere already, budget the time to build it before assuming a good product will distribute itself.

Watch for the next wave honestly, not performatively. The transferable habit isn’t “predict AI agents” — nobody gets credit for calling the specific next hype cycle before it happens. It’s staying close enough to your own users and your own infrastructure that when a genuine shift shows up, you can tell the difference between a real inflection and a trend piece, and you’re technically ready to move in days instead of quarters.

What isn’t transferable: the specific timing, the fact that Nevo already had a public build-in-public following from two prior ventures before Postiz’s first GitHub star, and the plain reality that most products don’t have an AI-agent-shaped growth wave waiting for them at all. Ride the wave that’s actually there for your product. This one happened to be agents. For you, it might be something else entirely, or nothing you can name yet — and pretending otherwise is worse than admitting it.

Sources

postiz open-source developer-tools ai-agents saas
Share this article
LinkedIn (opens in new tab) X / Twitter (opens in new tab)
Atticus Li

Experimentation and growth leader. CXL-certified CRO practitioner, Mindworx-certified behavioral economist (1 of ~1,000 worldwide). 200+ A/B tests across energy, SaaS, fintech, e-commerce, and marketplace verticals.

About LinkedIn Newsletter