A · leads
quivr
99.1
39,655 stars · MIT
Databases
quivr leads by 7.3 · clear
A · leads
99.1
39,655 stars · MIT
B
91.8
25,279 stars · MIT
quivr versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. quivr is written mainly in Go; turso is written mainly in Rust. The composite score is 99.1 for quivr and 91.8 for turso.
quivr has 39,655 GitHub stars to turso's 25,279, a gap of 14,376 (1.57×). Forks are 3,730 for quivr 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 89.
Push history: quivr was last pushed on 16 November 2026 (1 day ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 16 for quivr (0.000 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 96 and 52; activity scores are 100 and 100.
Both quivr 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 quivr (39,655 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: quivr is open source, turso is open source.
quivr 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 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
quivr finishes ahead at 99.1 against turso at 91.8, a 7.3 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 | quivr | turso |
|---|---|---|
| GitHub stars | 39,655 | 25,279 |
| Forks | 3,730 | 1,553 |
| Open issues | 16 | 1,714 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 96 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 91.8 |
An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search, alerts, and plugins for formats, models and business rules.
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
quivr has more GitHub stars: 39,655 versus 25,279 for turso. The gap is 14,376 stars.
turso was pushed more recently: 17 November 2026 versus 16 November 2026 for quivr. That is 1 days apart.
Yes. This catalog marks both quivr and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
quivr 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.
quivr scores 99.1 and turso scores 91.8. This page calls that a clear lead for quivr.