A
chartdb
84.1
23,133 stars · AGPL-3.0
Databases
DuckDB leads by 12.4 · clear
A
84.1
23,133 stars · AGPL-3.0
B · leads
96.5
43,126 stars · MIT
chartdb versus DuckDB is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. chartdb is written mainly in TypeScript; DuckDB is written mainly in C++. The composite score is 84.1 for chartdb and 96.5 for DuckDB.
DuckDB has 43,126 GitHub stars to chartdb's 23,133, a gap of 19,993 (1.86×). Forks are 1,527 for chartdb and 4,214 for DuckDB. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 88 versus 100.
Push history: chartdb was last pushed on 01 November 2026 (16 days ago), and DuckDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 155 for chartdb (0.007 per star) and 1,261 for DuckDB (0.029 per star). Issue-health scores are 84 and 70; 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. DuckDB is listed as MIT, 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 DuckDB. This is a procurement signal, not legal advice.
In Databases, both chartdb (23,133 stars) and DuckDB (43,126 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, DuckDB is open source.
The lead is split. chartdb is furthest ahead on issue health (84 to 70), while DuckDB is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
DuckDB finishes ahead at 96.5 against chartdb at 84.1, a 12.4 point clear 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 | DuckDB |
|---|---|---|
| GitHub stars | 23,133 | 43,126 |
| Forks | 1,527 | 4,214 |
| Open issues | 155 | 1,261 |
| Adoption | 94 | 100 |
| Activity | 78 | 100 |
| Community | 88 | 100 |
| Issue health | 84 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.1 | 96.5 |
Database diagrams editor that allows you to visualize and design your DB with a single query.
DuckDB is an in-process analytical database, often described as SQLite for OLAP. It runs inside the application process and queries local files such as Parquet.
DuckDB has more GitHub stars: 43,126 versus 23,133 for chartdb. The gap is 19,993 stars.
DuckDB 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 DuckDB 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. DuckDB is listed as MIT, 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.
DuckDB scores 96.5 and chartdb scores 84.1. This page calls that a clear lead for DuckDB.