A · leads
DuckDB
96.5
43,126 stars · MIT
Databases
DuckDB leads by 5.2 · narrow
A · leads
96.5
43,126 stars · MIT
B
91.3
25,279 stars · MIT
DuckDB versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. DuckDB is written mainly in C++; turso is written mainly in Rust. The composite score is 96.5 for DuckDB and 91.3 for turso.
DuckDB has 43,126 GitHub stars to turso's 25,279, a gap of 17,847 (1.71×). Forks are 4,214 for DuckDB and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 88.
Push history: DuckDB 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 1,261 for DuckDB (0.029 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
Both DuckDB and turso are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both DuckDB (43,126 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: DuckDB is open source, turso is open source.
DuckDB is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 18 points (70 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
DuckDB finishes ahead at 96.5 against turso at 91.3, a 5.2 point narrow 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 | DuckDB | turso |
|---|---|---|
| GitHub stars | 43,126 | 25,279 |
| Forks | 4,214 | 1,553 |
| Open issues | 1,261 | 1,714 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 91.3 |
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.
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
DuckDB has more GitHub stars: 43,126 versus 25,279 for turso. The gap is 17,847 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both DuckDB and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
DuckDB scores 96.5 and turso scores 91.3. This page calls that a narrow lead for DuckDB.