Skip to content
DevUtils Online

Databases

chartdb vs turso

turso leads by 7.2 · clear

A

chartdb

87.5

23,133 stars · AGPL-3.0

B · leads

turso

94.7

25,279 stars · MIT

chartdb versus turso 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; turso is written mainly in Rust. The composite score is 87.5 for chartdb and 94.7 for turso.

turso has 25,279 GitHub stars to chartdb's 23,133, a gap of 2,146 (1.09×). Forks are 1,527 for chartdb and 1,553 for turso. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 100.

Push history: chartdb was last pushed on 01 November 2026 (16 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 155 for chartdb (0.007 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 84 and 52; 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. turso 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 turso. This is a procurement signal, not legal advice.

In Databases, both chartdb (23,133 stars) and turso (25,279 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, turso is open source.

The lead is split. chartdb is furthest ahead on issue health (84 to 52), while turso is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.

turso finishes ahead at 94.7 against chartdb at 87.5, a 7.2 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

chartdb versus turso metrics
Signal chartdb turso
GitHub stars 23,133 25,279
Forks 1,527 1,553
Open issues 155 1,714
Adoption 99 100
Activity 78 100
Community 100 100
Issue health 84 52
License 52 96
Self-hosting 100 100
Composite 87.5 94.7

turso

A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, chartdb or turso?

turso has more GitHub stars: 25,279 versus 23,133 for chartdb. The gap is 2,146 stars.

Which was updated more recently, chartdb or turso?

turso was pushed more recently: 17 November 2026 versus 01 November 2026 for chartdb. That is 16 days apart.

Can I self-host both chartdb and turso?

Yes. This catalog marks both chartdb and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, chartdb or turso?

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. turso 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.

Who wins the chartdb vs turso score?

turso scores 94.7 and chartdb scores 87.5. This page calls that a clear lead for turso.

Related comparisons