A · leads
etcd
97.9
52,615 stars · Apache-2.0
Databases
etcd leads by 24.9 · decisive
A · leads
97.9
52,615 stars · Apache-2.0
B
73.0
11,117 stars · Apache-2.0
etcd versus FerretDB 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 Go. The composite score is 97.9 for etcd and 73.0 for FerretDB.
etcd has 52,615 GitHub stars to FerretDB's 11,117, a gap of 41,498 (4.73×). Forks are 10,608 for etcd and 496 for FerretDB. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 67.
Push history: etcd was last pushed on 17 November 2026 (0 days ago), and FerretDB was last pushed on 05 June 2026 (165 days ago). Open issues stand at 478 for etcd (0.009 per star) and 452 for FerretDB (0.041 per star). Issue-health scores are 84 and 70; activity scores are 100 and 36.
Both etcd and FerretDB are listed as Apache-2.0. 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 etcd (52,615 stars) and FerretDB (11,117 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, FerretDB is open source.
etcd is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 64 points (100 vs 36), and the tightest is self-hosting at 0 points (100 vs 100).
etcd finishes ahead at 97.9 against FerretDB at 73.0, a 24.9 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 | FerretDB |
|---|---|---|
| GitHub stars | 52,615 | 11,117 |
| Forks | 10,608 | 496 |
| Open issues | 478 | 452 |
| Adoption | 100 | 86 |
| Activity | 100 | 36 |
| Community | 100 | 67 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 73.0 |
Distributed reliable key-value store for the most critical data of a distributed system
FerretDB is a MongoDB-compatible document database that stores data in PostgreSQL. It is built for teams that want that wire protocol without the SSPL server.
etcd has more GitHub stars: 52,615 versus 11,117 for FerretDB. The gap is 41,498 stars.
etcd was pushed more recently: 17 November 2026 versus 05 June 2026 for FerretDB. That is 165 days apart.
Yes. This catalog marks both etcd and FerretDB 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. FerretDB 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
etcd scores 97.9 and FerretDB scores 73.0. This page calls that a decisive lead for etcd.