A · level
drawdb
92.6
40,334 stars · AGPL-3.0
Databases
Too close to call · 92.6 to 91.9
A · level
92.6
40,334 stars · AGPL-3.0
B · level
91.9
25,279 stars · MIT
drawdb versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. drawdb is written mainly in JavaScript; turso is written mainly in Rust. The composite score is 92.6 for drawdb and 91.9 for turso.
drawdb has 40,334 GitHub stars to turso's 25,279, a gap of 15,055 (1.60×). Forks are 3,368 for drawdb and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 90.
Push history: drawdb was last pushed on 13 November 2026 (3 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 253 for drawdb (0.006 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
drawdb 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 drawdb and 96 for turso. This is a procurement signal, not legal advice.
In Databases, both drawdb (40,334 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: drawdb is open source, turso is open source.
The lead is split. drawdb 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.
Composite score: drawdb 92.6, turso 91.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | drawdb | turso |
|---|---|---|
| GitHub stars | 40,334 | 25,279 |
| Forks | 3,368 | 1,553 |
| Open issues | 253 | 1,714 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 90 |
| Issue health | 84 | 52 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 91.9 |
Free, simple, and intuitive online database diagram editor and SQL generator.
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
drawdb has more GitHub stars: 40,334 versus 25,279 for turso. The gap is 15,055 stars.
turso was pushed more recently: 17 November 2026 versus 13 November 2026 for drawdb. That is 3 days apart.
Yes. This catalog marks both drawdb and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
drawdb 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.
Neither tool clears a one-point margin. drawdb scores 92.6 and turso scores 91.9.