A · leads
etcd
97.9
52,615 stars · Apache-2.0
Databases
etcd leads by 8.4 · clear
A · leads
97.9
52,615 stars · Apache-2.0
B
89.5
25,279 stars · MIT
etcd versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. etcd is written mainly in Go; turso is written mainly in Rust. The composite score is 97.9 for etcd and 89.5 for turso.
etcd has 52,615 GitHub stars to turso's 25,279, a gap of 27,336 (2.08×). Forks are 10,608 for etcd and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 79.
Push history: etcd 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 478 for etcd (0.009 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
etcd 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 etcd and 96 for turso. This is a procurement signal, not legal advice.
In Databases, both etcd (52,615 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: etcd is open source, turso is open source.
etcd 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 32 points (84 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
etcd finishes ahead at 97.9 against turso at 89.5, a 8.4 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 | etcd | turso |
|---|---|---|
| GitHub stars | 52,615 | 25,279 |
| Forks | 10,608 | 1,553 |
| Open issues | 478 | 1,714 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 79 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 89.5 |
Distributed reliable key-value store for the most critical data of a distributed system
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
etcd has more GitHub stars: 52,615 versus 25,279 for turso. The gap is 27,336 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both etcd and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
etcd 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.
etcd scores 97.9 and turso scores 89.5. This page calls that a clear lead for etcd.