How Plausible Analytics Hit $1M ARR with SEO, GitHub, and Hacker News
Plausible built to $1M ARR bootstrapped using three channels and zero paid ads. Here are the patterns behind each one.
Plausible Analytics crossed $1M ARR bootstrapped. No paid ads. Two founders. They ran three channels in parallel: SEO content targeting developers, GitHub open-source visibility, and Hacker News. Each channel fed the others. It is one of the cleaner distribution case studies in the DistributionMarket database, and the pattern it represents shows up across multiple apps that crossed $100K ARR using zero ad spend.
How Plausible Analytics hit $1M ARR: the channel combination
Most SaaS companies treat distribution as a single-channel problem. Plausible ran three channels from year one.
The sequence: a well-timed Hacker News post brought the initial audience. That audience validated the product and left GitHub stars. The GitHub stars became social proof that every SEO post could reference. The SEO content brought a steady organic baseline that compounded month over month.
None of those three channels is unusual on its own. What separates Plausible is the sequencing. HN gave speed. GitHub gave trust. SEO gave compounding volume. No single channel gave all three.
Across the 68 apps in the DistributionMarket database, two or more channels running simultaneously shows up in the majority of apps that crossed $100K ARR. Single-channel approaches that worked were almost always founder audience plays: a founder with an existing audience of 10,000 or more followers launched and converted that list. Without an existing audience, multi-channel was the dominant path.
What the Hacker News play actually required
The Show HN post that put Plausible on the map generated 48,000 visitors in one week. That was more traffic than the previous 15 months combined. It added 166 new trials and pushed monthly revenue up 40% in a single week.
Two things made that post land. First, Plausible had a working product before posting. The spike converted because there was something ready to receive it. Founders who post Show HN before the product is ready get traffic that evaporates without converting.
Second, the framing worked for the specific HN audience. Plausible did not lead with features. The post challenged Google Analytics directly, building a 2,500-word argument before mentioning Plausible as an alternative. By the time readers reached the product mention, they felt informed, not sold to. HN has a strong reaction to self-promotion. Plausible avoided it by leading with the problem.
The timing also mattered. GDPR enforcement was an active conversation in Europe at exactly the moment Plausible was growing. Austrian, French, Italian, and Swedish authorities all ruled that Google Analytics violated GDPR between 2022 and 2023. Each ruling gave Plausible a reason to reshare their content. One viral HN post became a repeating wave of inbound. Timing a launch around regulatory pressure is not luck. It is positioning.
The HN post worked because it challenged a specific giant on a specific problem the audience already had. That framing, problem-first, product second, is replicable. The regulatory tailwind was timing. The framing was craft.
What the SEO play actually looked like
Plausible's SEO approach is one of the clearest examples of intent-matched content in the DistributionMarket database. Every post was built around a search the audience was already making, not around what Plausible wanted to say about itself.
Posts like "why you do not need Google Analytics" and "GDPR-compliant analytics alternatives" are not thought leadership. They are pages built around searches with specific buyer intent. Someone searching for a Google Analytics alternative is already a qualified lead. The content does not need to sell. It needs to answer completely and make the product the obvious next step.
Here is the trap most founders fall into: publishing content about the product instead of content about the problem. A post titled "Introducing Plausible 2.0" attracts no organic search. A post titled "Is Google Analytics GDPR compliant?" attracts every European developer facing a compliance audit.
Across the 833 tactics in the DistributionMarket database, this approach shows up across most apps that crossed $100K ARR with content as their main channel. Write the complete answer, not a teaser. Give people the whole thing. It is not a Plausible-specific insight. It is a pattern.
What made Plausible's execution distinct was volume. They published consistently at one to two posts per week for multiple years, each post targeting a specific search with a specific buyer mindset. That cadence is what turns a few good posts into compounding search traffic. SEO is not a campaign. It is a publication schedule.
What the GitHub channel gave them that the others could not
SEO brings strangers. HN brings critics. GitHub brings contributors and validators.
When developers evaluate a tool, GitHub star count is a signal they actually use. A project with 10,000 stars is assumed to be real, maintained, and trusted. Plausible's open-source core meant every developer who evaluated the product could inspect the code, verify the privacy claims, and star the repo. That star count became a trust signal that every SEO post and every HN comment could reference.
The open-source channel is slow to build but nearly impossible to replicate. A competitor cannot buy GitHub stars. They have to earn them through the same process: shipping a real product, making the code public, and being in the right communities when developers are evaluating options.
There is also a second-order effect that gets less attention. Open-source communities create organic link building. Developers blog about tools they use, share repos in newsletters, and mention integrations in documentation. Every mention is a backlink. Plausible did not run a link-building campaign. The community built the links.
Why Plausible did not run paid ads
No paid advertising. No influencer partnerships. No affiliate program at launch. No Product Hunt launch campaign.
The decision to avoid paid ads was not ideological. It was economic. Developer audiences do not convert from display or social ads the way consumer audiences do. The CAC at their price point did not support paid acquisition when measured against LTV. SEO and community converted better and cost less per customer acquired.
This exposes one of the most common anti-patterns in B2B SaaS: spending on paid channels before SEO has compounded. Paid gives you a signal quickly, but the cost per acquisition never decreases. SEO takes 12 to 18 months to compound. After that, the cost per acquisition drops every month because the content keeps working after you stop paying for it.
Product Hunt generated 2,399 visitors and 33 trials when Plausible eventually ran a launch there. That is a reasonable outcome. But compared to what a single HN post produced (48,000 visitors, 166 trials), the Product Hunt result shows why community-native channels outperform campaign-style launches for developer audiences. The community you build slowly converts better than the spike you buy quickly.
Two channels running together beat one channel running twice as hard. The Plausible case is evidence. The DistributionMarket database, across 68 apps and 98 channels tracked, is the pattern.
What the data shows about bootstrapped apps like Plausible
Inside DistributionMarket, the combination of SEO plus at least one community channel shows up in the majority of bootstrapped apps that reached $100K ARR. Apps that relied on SEO alone showed slower initial conversion because there was no trust signal to accelerate the decision. Apps that relied on community alone showed traffic spikes that did not compound into sustained organic growth.
The durable businesses sit at the intersection of both. Plausible reached $3.1M revenue in 2024 with 12,000 paying subscribers. Their search traffic keeps compounding years after the content was published. The HN posts from 2021 still drive branded searches. The GitHub stars from 2020 are still visible on product listing pages.
That compounding effect is what separates distribution strategies from distribution campaigns. Early work keeps producing. Plausible built a strategy.
The full breakdown is inside the app
The channels, tactics, and anti-patterns described here are a pattern-level summary. The DistributionMarket database has the full breakdown for Plausible: all sources cited, revenue snapshots by month, every channel with the specific tactics used, the 1,130 lessons catalogued across all 68 apps, and the complete anti-pattern list. The above covers the mechanism. The database covers the execution.
Frequently Asked Questions
How did Plausible Analytics get their first customers?
Plausible's first customers came from a Hacker News Show HN post. They followed it with SEO content and open-source community building on GitHub.
What distribution channels does Plausible use?
SEO blog targeting developer search intent, GitHub open-source community, and Hacker News. No paid advertising.
Is Plausible Analytics bootstrapped?
Yes. Two founders, no outside funding, over $1M ARR.
Stop Building, Start Selling
Full channel breakdowns, tactics, and revenue data. Free to join.
68 Apps Pattern
DistributionMarket analyzed 68 bootstrapped SaaS apps. These are the distribution patterns that appear repeatedly across every app at $100K ARR.
ScreenshotOne
ScreenshotOne crossed the $100K MRR band bootstrapped, solo, and without a sales team. Here is the distribution stack behind a screenshot API that compounds.