GitDealFlowsignals

Case study · GitHub signal → priced round

PlanetScale, serverless MySQL to a $50M Series C at $1B

PlanetScale's CLI repo was modest; the partnership-density signal preceded the Series C unicorn round.

At a glance

Company
PlanetScale
Sector
Database / serverless MySQL
Primary repo
github.com/planetscale/cli
Trigger window
late 2021 / early 2022
Stars at trigger
CLI star count modest; signal in customer growth
Announced raise
$50M Series C ($1B valuation) (2022-02-15)
Lead investor
Series C at $1B
Time-to-money read
CLI usage growth + Next.js partnership coverage led the Series C

PlanetScale's GitHub footprint is intentionally small, the product is a hosted MySQL service. The CLI repo carried the technical brand, but the *real* signal was partnership-announcement density.

By late 2021 PlanetScale was the recommended database in Next.js + Prisma tutorials, with co-marketing across the dev-tool ecosystem. That kind of partnership density is a strong leading indicator for SaaS rounds.

The $50M Series C at $1B closed in February 2022, a unicorn-tier outcome on top of a signal that had been visible in the partnership graph for a year.

Signals that would have flagged this pre-raise

  • Partnership density:Co-marketing with Next.js, Prisma, Vercel
  • CLI release cadence:Steady tagged releases through 2021-2022
  • Tutorial inclusion:Default Next.js database pick in many tutorials

How the timeline read

The engineering acceleration was observable during late 2021 / early 2022, while any fundraising paperwork was still private. The announced event, $50M Series C ($1B valuation) on 2022-02-15, landed after the signal window: CLI usage growth + Next.js partnership coverage led the Series C. 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 cli star count modest; signal in customer growth.

In practice, that is what a weekly monitoring cadence buys you. VC Deal Flow Signal re-scores this sector (Database / serverless MySQL) 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 'partnership density' translate to a signal?

Count co-marketed launches per quarter. A rising count over 12 months is one of the strongest predictors of priced rounds for SaaS-tier companies.

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

Read them side by side: these related cases span Backend-as-a-service, Dev tools / ORM, 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

🚀 Explore Our Network

21-47 days
Signal Lead Time (median 31d)
$80M+
Rounds Tracked
90 sec
Per Scan
5,000+
Founders Tracked

One missed signal is a missed round. Get the Velocity Verdict in your inbox every Sunday free.

Get Free Signals

Free weekly digest. Cancel anytime. No spam, no VC pitches just data.