A
dragonfly
77.5
31,878 stars · license n/a
Databases
supabase leads by 20.4 · decisive
A
77.5
31,878 stars · license n/a
B · leads
97.9
115,156 stars · Apache-2.0
dragonfly versus supabase is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dragonfly is written mainly in C++; supabase is written mainly in TypeScript. The composite score is 77.5 for dragonfly and 97.9 for supabase.
supabase has 115,156 GitHub stars to dragonfly's 31,878, a gap of 83,278 (3.61×). Forks are 1,294 for dragonfly and 15,166 for supabase. On the log scale used inside this pair, adoption is 89 versus 100, and the fork community is 74 versus 100.
Push history: dragonfly was last pushed on 17 November 2026 (0 days ago), and supabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 209 for dragonfly (0.007 per star) and 1,233 for supabase (0.011 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
dragonfly is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. supabase is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 30 for dragonfly and 96 for supabase. This is a procurement signal, not legal advice.
Only supabase is marked self-hostable here (115,156 stars, deploy score 100). dragonfly is not (31,878 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: dragonfly is unpriced in this catalog, supabase is open source.
supabase is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is issue health at 0 points (84 vs 84).
supabase finishes ahead at 97.9 against dragonfly at 77.5, a 20.4 point decisive margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | dragonfly | supabase |
|---|---|---|
| GitHub stars | 31,878 | 115,156 |
| Forks | 1,294 | 15,166 |
| Open issues | 209 | 1,233 |
| Adoption | 89 | 100 |
| Activity | 100 | 100 |
| Community | 74 | 100 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 77.5 | 97.9 |
A modern replacement for Redis and Memcached
The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
supabase has more GitHub stars: 115,156 versus 31,878 for dragonfly. The gap is 83,278 stars.
Both were last pushed on 17 November 2026.
Only supabase is marked self-hostable. dragonfly is not.
dragonfly is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. supabase is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
supabase scores 97.9 and dragonfly scores 77.5. This page calls that a decisive lead for supabase.