LSLaunch SentinelReports
⚡ Early access — every report is free right now.
Home / Reports / Supabase (Alpha)
S
VC Intelligence Report

Supabase (Alpha)

Developer Tools — Supabase is an open-source backend platform designed as an alternative to Firebase
Developer Toolsopen-source
● Stable
Category standing real
98th pctl · Developer Tools
37.1
Signal score
0–100 composite · real
#122
Category rank
of 7,723 · real
99th
Universe percentile
vs 79,105 modeled · real
1%
Mortality P(dead)
verified label · real

Signal trajectory

real

Signal 16.820.4 across 169 readings (+3.6). Composite of press, GitHub velocity, community heat, liveness and funding.

Cross-sectional profile

percentile rank vs 79,105 modeled products
Signal (universe) real
99
Signal (category) real
98
Profile maturity real
99
Tag breadth real
95
Network position sparse
94
Press footprint sparse
0

Percentiles computed over the modeled cohort (embedding + signal + tags). Sparse dimensions — network and press — reflect that most products have zero, so a single edge or mention lifts the rank; read those with the coverage flag.

Mortality outlook

verified label
1%
P(inactive)
Low risk
Higher risk than 2% of the universe.

This product carries a verified outcome label (“surviving”) — it is one of 600 hand-labeled cases the model is trained and tested on.

  • LightGBM · binary mortality (dead vs surviving)
  • Held-out AUC 0.71 · CV AUC 0.79 ± 0.05 · Brier 0.21
  • Trained on 600 verified labels (150 dead / 450 surviving)
  • Leakage-guarded: excludes status, discontinued_year, profile_maturity
  • Top drivers: tag breadth, signal, vintage, liveness, business model

n=600 is thin → 95% CI on AUC ≈ ±0.10. Treat as a directional signal, not a calibrated probability.

Analyst read

generated from the metrics above · no external narrative

Supabase (Alpha) sits in the 99th percentile of Launch Sentinel's 79,105-product universe by signal, ranked #122 of 7,723 in Developer Tools. The mortality model puts its probability of going inactive at 1% — a verified outcome label. It sits on the competitive-alternatives graph with 1 linked rival, so the comparable set below leans on curated edges. Signal momentum is roughly flat.

Comparable set

curated alternatives → functional tag-similarity
CompanyBasisSignalP(dead)
Parse Serverdev-toolscurated18.60%
VeloDBanalyticstag-overlap32.92%
Appwrite GraphQLdev-toolssimilar32.92%
Alephanalyticstag-overlap18.60%
KSQL for Kafkadev-toolssimilar21.41%
MongooseIM 2.0.1communicationtag-overlap18.628%
Autobahndev-toolssimilar15.763%
Rqueue aka Redis Queue For Spring/Bootdev-toolssimilar32.91%

Confidence reflects source and category coherence: curated = an editorially linked alternative; similar = strong functional tag-overlap in the same category; tag-overlap = shared tags only and may be noisy. Signal & P(dead) are real / model.

Structure

observed attributes
Business modelopen-source
Liveness tierquiet
Open sourceNo
Public APINo
Free tierNo
Enterprise tierNo

Funding & team

not in source

No disclosed funding in our sources. Funding data covers only ~1% of the corpus (462 rounds across 79K products), so absence here is unknown, not zero— we don't estimate a number we can't source.