A
chartdb
79.8
23,133 stars · AGPL-3.0
Databases
supabase leads by 18.1 · decisive
A
79.8
23,133 stars · AGPL-3.0
B · leads
97.9
115,156 stars · Apache-2.0
chartdb 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 79.8 for chartdb and 97.9 for supabase.
supabase has 115,156 GitHub stars to chartdb's 23,133, a gap of 92,023 (4.98×). Forks are 1,527 for chartdb and 15,166 for supabase. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 76 versus 100.
Push history: chartdb was last pushed on 01 November 2026 (16 days ago), and supabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 155 for chartdb (0.007 per star) and 1,233 for supabase (0.011 per star). Issue-health scores are 84 and 84; activity scores are 78 and 100.
chartdb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for chartdb and 96 for supabase. This is a procurement signal, not legal advice.
In Databases, both chartdb (23,133 stars) and supabase (115,156 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: chartdb is open source, supabase is open source.
supabase is ahead on every scored dimension that is not level. Level dimensions: issue health, self-hosting. The widest gap is license flexibility at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
supabase finishes ahead at 97.9 against chartdb at 79.8, a 18.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 | chartdb | supabase |
|---|---|---|
| GitHub stars | 23,133 | 115,156 |
| Forks | 1,527 | 15,166 |
| Open issues | 155 | 1,233 |
| Adoption | 86 | 100 |
| Activity | 78 | 100 |
| Community | 76 | 100 |
| Issue health | 84 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 79.8 | 97.9 |
Database diagrams editor that allows you to visualize and design your DB with a single query.
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 23,133 for chartdb. The gap is 92,023 stars.
supabase was pushed more recently: 17 November 2026 versus 01 November 2026 for chartdb. That is 16 days apart.
Yes. This catalog marks both chartdb and supabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
chartdb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 chartdb scores 79.8. This page calls that a decisive lead for supabase.