A
sqlitebrowser
83.3
24,802 stars · license n/a
Databases
turso leads by 10.7 · clear
A
83.3
24,802 stars · license n/a
B · leads
94.0
25,279 stars · MIT
sqlitebrowser versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. sqlitebrowser is written mainly in C++; turso is written mainly in Rust. The composite score is 83.3 for sqlitebrowser and 94.0 for turso.
turso has 25,279 GitHub stars to sqlitebrowser's 24,802, a gap of 477 (1.02×). Forks are 2,381 for sqlitebrowser and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 94.
Push history: sqlitebrowser was last pushed on 15 November 2026 (2 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 816 for sqlitebrowser (0.033 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
sqlitebrowser 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 sqlitebrowser 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). sqlitebrowser is not (24,802 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: sqlitebrowser is unpriced in this catalog, turso is open source.
The lead is split. sqlitebrowser is furthest ahead on issue health (70 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 sqlitebrowser at 83.3, a 10.7 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 | sqlitebrowser | turso |
|---|---|---|
| GitHub stars | 24,802 | 25,279 |
| Forks | 2,381 | 1,553 |
| Open issues | 816 | 1,714 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 94 |
| Issue health | 70 | 52 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 83.3 | 94.0 |
Official home of the DB Browser for SQLite (DB4S) project. Previously known as "SQLite Database Browser" and "Database Browser for SQLite". Website at:
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
turso has more GitHub stars: 25,279 versus 24,802 for sqlitebrowser. The gap is 477 stars.
turso was pushed more recently: 17 November 2026 versus 15 November 2026 for sqlitebrowser. That is 2 days apart.
Only turso is marked self-hostable. sqlitebrowser is not.
sqlitebrowser 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.
turso scores 94.0 and sqlitebrowser scores 83.3. This page calls that a clear lead for turso.