Skip to content
DevUtils Online

Databases

dragonfly vs turso

turso leads by 9.5 · clear

A

dragonfly

84.5

31,878 stars · license n/a

B · leads

turso

94.0

25,279 stars · MIT

dragonfly versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dragonfly is written mainly in C++; turso is written mainly in Rust. The composite score is 84.5 for dragonfly and 94.0 for turso.

dragonfly has 31,878 GitHub stars to turso's 25,279, a gap of 6,599 (1.26×). Forks are 1,294 for dragonfly and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 98 versus 100.

Push history: dragonfly was last pushed on 17 November 2026 (0 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 209 for dragonfly (0.007 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.

dragonfly 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. 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 30 for dragonfly and 96 for turso. This is a procurement signal, not legal advice.

Only turso is marked self-hostable here (25,279 stars, deploy score 100). dragonfly is not (31,878 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: dragonfly is unpriced in this catalog, turso is open source.

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

turso finishes ahead at 94.0 against dragonfly at 84.5, a 9.5 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.

dragonfly versus turso metrics
Signal dragonfly turso
GitHub stars 31,878 25,279
Forks 1,294 1,553
Open issues 209 1,714
Adoption 100 98
Activity 100 100
Community 98 100
Issue health 84 52
License 30 96
Self-hosting 35 100
Composite 84.5 94.0

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, dragonfly or turso?

dragonfly has more GitHub stars: 31,878 versus 25,279 for turso. The gap is 6,599 stars.

Which was updated more recently, dragonfly or turso?

Both were last pushed on 17 November 2026.

Can I self-host both dragonfly and turso?

Only turso is marked self-hostable. dragonfly is not.

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

dragonfly 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. 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 dragonfly vs turso score?

turso scores 94.0 and dragonfly scores 84.5. This page calls that a clear lead for turso.

Related comparisons