A
chartdb
83.7
23,133 stars · AGPL-3.0
Databases
tidb leads by 9.2 · clear
A
83.7
23,133 stars · AGPL-3.0
B · leads
92.9
40,739 stars · Apache-2.0
chartdb versus tidb 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; tidb is written mainly in Go. The composite score is 83.7 for chartdb and 92.9 for tidb.
tidb has 40,739 GitHub stars to chartdb's 23,133, a gap of 17,606 (1.76×). Forks are 1,527 for chartdb and 6,297 for tidb. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 84 versus 100.
Push history: chartdb was last pushed on 01 November 2026 (16 days ago), and tidb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 155 for chartdb (0.007 per star) and 7,730 for tidb (0.190 per star). Issue-health scores are 84 and 34; 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. tidb 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 tidb. This is a procurement signal, not legal advice.
In Databases, both chartdb (23,133 stars) and tidb (40,739 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, tidb is open source.
The lead is split. chartdb is furthest ahead on issue health (84 to 34), while tidb is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
tidb finishes ahead at 92.9 against chartdb at 83.7, a 9.2 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 | tidb |
|---|---|---|
| GitHub stars | 23,133 | 40,739 |
| Forks | 1,527 | 6,297 |
| Open issues | 155 | 7,730 |
| Adoption | 95 | 100 |
| Activity | 78 | 100 |
| Community | 84 | 100 |
| Issue health | 84 | 34 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 83.7 | 92.9 |
Database diagrams editor that allows you to visualize and design your DB with a single query.
TiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, analytics, and vector search. No data silos. No noisy neighbors. No infrastructure ceiling.
tidb has more GitHub stars: 40,739 versus 23,133 for chartdb. The gap is 17,606 stars.
tidb 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 tidb 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. tidb 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.
tidb scores 92.9 and chartdb scores 83.7. This page calls that a clear lead for tidb.