A · leads
etcd
97.9
52,615 stars · Apache-2.0
Databases
etcd leads by 26.1 · decisive
A · leads
97.9
52,615 stars · Apache-2.0
B
71.8
10,666 stars · license n/a
etcd versus yugabyte-db 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; yugabyte-db is written mainly in C. The composite score is 97.9 for etcd and 71.8 for yugabyte-db.
etcd has 52,615 GitHub stars to yugabyte-db's 10,666, a gap of 41,949 (4.93×). Forks are 10,608 for etcd and 1,477 for yugabyte-db. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 79.
Push history: etcd was last pushed on 17 November 2026 (0 days ago), and yugabyte-db was last pushed on 17 November 2026 (0 days ago). Open issues stand at 478 for etcd (0.009 per star) and 9,707 for yugabyte-db (0.910 per star). Issue-health scores are 84 and 34; 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. yugabyte-db 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. License scores in this pair are 96 for etcd and 30 for yugabyte-db. This is a procurement signal, not legal advice.
Only etcd is marked self-hostable here (52,615 stars, deploy score 100). yugabyte-db is not (10,666 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: etcd is open source, yugabyte-db is unpriced in this catalog.
etcd is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is recent activity at 0 points (100 vs 100).
etcd finishes ahead at 97.9 against yugabyte-db at 71.8, a 26.1 point decisive 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 | yugabyte-db |
|---|---|---|
| GitHub stars | 52,615 | 10,666 |
| Forks | 10,608 | 1,477 |
| Open issues | 478 | 9,707 |
| Adoption | 100 | 85 |
| Activity | 100 | 100 |
| Community | 100 | 79 |
| Issue health | 84 | 34 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 97.9 | 71.8 |
Distributed reliable key-value store for the most critical data of a distributed system
YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
etcd has more GitHub stars: 52,615 versus 10,666 for yugabyte-db. The gap is 41,949 stars.
Both were last pushed on 17 November 2026.
Only etcd is marked self-hostable. yugabyte-db is not.
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. yugabyte-db 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
etcd scores 97.9 and yugabyte-db scores 71.8. This page calls that a decisive lead for etcd.