A · leads
influxdb
94.7
31,816 stars · Apache-2.0
Databases
influxdb leads by 2.3 · narrow
A · leads
94.7
31,816 stars · Apache-2.0
B
92.4
25,279 stars · MIT
influxdb versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Rust. The composite score is 94.7 for influxdb and 92.4 for turso.
influxdb has 31,816 GitHub stars to turso's 25,279, a gap of 6,537 (1.26×). Forks are 3,826 for influxdb and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 89.
Push history: influxdb 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 2,175 for influxdb (0.068 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
influxdb is listed as Apache-2.0, 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. License scores in this pair are 96 for influxdb and 96 for turso. This is a procurement signal, not legal advice.
In Databases, both influxdb (31,816 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: influxdb is open source, turso is open source.
influxdb is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 11 points (100 vs 89), and the tightest is self-hosting at 0 points (100 vs 100).
influxdb finishes ahead at 94.7 against turso at 92.4, a 2.3 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 | influxdb | turso |
|---|---|---|
| GitHub stars | 31,816 | 25,279 |
| Forks | 3,826 | 1,553 |
| Open issues | 2,175 | 1,714 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 52 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 92.4 |
Scalable datastore for metrics, events, and real-time analytics
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
influxdb has more GitHub stars: 31,816 versus 25,279 for turso. The gap is 6,537 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both influxdb and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
influxdb is listed as Apache-2.0, 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.
influxdb scores 94.7 and turso scores 92.4. This page calls that a narrow lead for influxdb.