Case study · GitHub signal → priced round
PostHog, OSS analytics to a $15M YC Series B
PostHog's open-source product analytics engine and YC backing priced the $15M Series B in late 2021.
At a glance
- Company
- PostHog
- Sector
- Product analytics
- Primary repo
- github.com/PostHog/posthog
- Trigger window
- second half 2021
- Stars at trigger
- ~9K stars at trigger window; YC backing
- Announced raise
- $15M Series B (Y Combinator) (2021-10-12)
- Lead investor
- Y Combinator (Series B)
- Time-to-money read
- OSS analytics positioning + customer growth led the Series B
PostHog's positioning is 'OSS Amplitude', same product surface, open-source license, self-hostable. By late 2021 the repo had crossed 9K stars and customer logos were public.
The signal was multi-modal: stars, customer references, plugin ecosystem, and YC backing. Each one weak alone; together strong.
The $15M Series B in October 2021 led by YC was the priced confirmation of a clear category-positioning play.
Signals that would have flagged this pre-raise
- OSS positioning:Default 'OSS Amplitude' recommendation
- Customer logo growth:Public references on landing page
- YC backing:Strong network signal
How the timeline read
The engineering acceleration was observable during second half 2021, while any fundraising paperwork was still private. The announced event, $15M Series B (Y Combinator) on 2021-10-12, landed after the signal window: OSS analytics positioning + customer growth led the Series B. That ordering is the entire thesis of this series: by the time a round appears in a funding digest, the repositories were already telling the story at ~9k stars at trigger window; yc backing.
In practice, that is what a weekly monitoring cadence buys you. VC Deal Flow Signal re-scores this sector (Product analytics) every week across its tracked repository, so a window like this one surfaces as a rising trend rather than a single spike you had to be lucky to catch. The pre-raise signals listed above are the rows that moved while the press stayed quiet.
Repositories
Frequently asked questions
How does YC backing change the signal?
It amplifies it. Network effects on YC-backed OSS tools tend to compound, both via internal-batch adoption and via Y Combinator's broader brand reach.
Find the next one
VC Deal Flow Signal tracks engineering acceleration weekly across twenty sectors, the same signal shapes that preceded the raise above.
Get the weekly signal report →Related case studies
- Sentry, OSS error monitoring to a $90M Series E at $3B
- Grafana: OSS dashboards to a $240M Series D
- Appsmith, OSS internal tools builder to a $41M Insight Series B
Read them side by side: these related cases span Dev tools / observability, Observability / dashboards, Low-code / internal tools, each with its own trigger window and raise event, and the same pre-raise signal shape held in every one. A pattern that repeats across different sectors and different windows is what separates a repeatable signal from an after-the-fact story.
Related proof stories
More in From Stars To Seed