A
convex-backend
72.8
12,804 stars · license n/a
Databases
supabase leads by 25.1 · decisive
A
72.8
12,804 stars · license n/a
B · leads
97.9
115,156 stars · Apache-2.0
convex-backend versus supabase is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 72.8 for convex-backend and 97.9 for supabase.
supabase has 115,156 GitHub stars to convex-backend's 12,804, a gap of 102,352 (8.99×). Forks are 854 for convex-backend and 15,166 for supabase. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 70 versus 100.
Push history: convex-backend 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 277 for convex-backend (0.022 per star) and 1,233 for supabase (0.011 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
convex-backend 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 convex-backend 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). convex-backend is not (12,804 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: convex-backend is unpriced in this catalog, supabase is open source.
supabase is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is recent activity at 0 points (100 vs 100).
supabase finishes ahead at 97.9 against convex-backend at 72.8, a 25.1 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 | convex-backend | supabase |
|---|---|---|
| GitHub stars | 12,804 | 115,156 |
| Forks | 854 | 15,166 |
| Open issues | 277 | 1,233 |
| Adoption | 81 | 100 |
| Activity | 100 | 100 |
| Community | 70 | 100 |
| Issue health | 70 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 72.8 | 97.9 |
The open-source reactive database for app developers
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 12,804 for convex-backend. The gap is 102,352 stars.
Both were last pushed on 17 November 2026.
Only supabase is marked self-hostable. convex-backend is not.
convex-backend 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 convex-backend scores 72.8. This page calls that a decisive lead for supabase.