head to head · open source
etcd vs Turso
etcd has 52,441 GitHub stars, 10,552 forks, 351 open issues and last shipped yesterday. Turso has 17,309 stars, 554 forks, 453 open issues and last shipped 17 days ago. etcd leads on adoption by 203% (52,441 vs 17,309 stars). etcd is written in Go under Apache-2.0; Turso is written in C under MIT. etcd has attracted 20% as many forks as stars, Turso 3%. etcd was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (database), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| etcd | Turso | |
|---|---|---|
| GitHub stars | ★ 52K | ★ 17K |
| License | Apache-2.0 | MIT |
| Written in | Go | C |
| Last push | 2026-11-02 | 2026-10-17 |
| Forks | ⑂ 11K | ⑂ 554 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick etcd if
- You weight community size — 52K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick Turso if
- You want the Turso feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches C
- You evaluated both and Turso fits your workflow better
About etcd
etcd Note : The main branch may be in an unstable or even broken state during development. For stable versions, see [releases][github release]. etcd is a distributed reliable key value store for the most critical data of a distributed system, with a focus on being: Simple : well defined, user facing API (gRPC) Secure : automatic TLS with optional client cert authentication Fast : benchmarked 10,000 writes/sec Reliable : properly distributed using Raft etcd is written in Go and uses the [Raft][] consensus algorithm to manage a highly available replicated log. etcd is used in production by many companies, and the…
About Turso
libSQL libSQL is an open source, open contribution fork of SQLite, created and maintained by Turso . libSQL Docs · libSQL Manifesto · Turso · Turso Docs · Discord · Blog & Tutorials [!IMPORTANT] Turso database and libSQL are two different projects from the same team. libSQL (this repository) is an open source fork of SQLite. It extends SQLite with features like embedded replicas and remote access, but inherits SQLite's fundamental limitations such as the single writer model. Turso database is a SQLite compatible database rewritten from scratch in Rust. It is not a fork of SQLite — it is a completely new…
read the full Turso overview →
More in Infrastructure & Operations
Related comparisons
More Databases projects
Compare either of these against the rest of the Databases field.
Frequently asked questions
Is etcd or Turso more popular?
etcd has 52,441 GitHub stars and Turso has 17,309. etcd has the larger community by that measure.
Are etcd and Turso free?
Both are open source. etcd is licensed under Apache-2.0 and Turso under MIT. Neither carries a licence fee.
What is the difference between etcd and Turso?
etcd is written in Go and Turso in C. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, etcd or Turso?
Choose etcd if you want the larger community (52,441 stars) or its Apache-2.0 licence terms. Choose Turso if its feature set, stack or MIT licence fits better. Both are self-hostable.