A
FerretDB
77.3
11,117 stars · Apache-2.0
Databases
Valkey leads by 19.2 · decisive
A
77.3
11,117 stars · Apache-2.0
B · leads
96.5
27,730 stars · BSD-3-Clause
FerretDB versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. FerretDB is written mainly in Go; Valkey is written mainly in C. The composite score is 77.3 for FerretDB and 96.5 for Valkey.
Valkey has 27,730 GitHub stars to FerretDB's 11,117, a gap of 16,613 (2.49×). Forks are 496 for FerretDB and 1,540 for Valkey. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 85 versus 100.
Push history: FerretDB was last pushed on 05 June 2026 (165 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 452 for FerretDB (0.041 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 70 and 70; activity scores are 36 and 100.
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. Valkey is listed as BSD-3-Clause, 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 FerretDB and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both FerretDB (11,117 stars) and Valkey (27,730 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: FerretDB is open source, Valkey is open source.
Valkey is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 64 points (36 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Valkey finishes ahead at 96.5 against FerretDB at 77.3, a 19.2 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 | FerretDB | Valkey |
|---|---|---|
| GitHub stars | 11,117 | 27,730 |
| Forks | 496 | 1,540 |
| Open issues | 452 | 1,045 |
| Adoption | 91 | 100 |
| Activity | 36 | 100 |
| Community | 85 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 77.3 | 96.5 |
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.
Valkey is a Linux Foundation key-value store forked from Redis. It is used as a cache, queue, and ephemeral data store under a permissive license.
Valkey has more GitHub stars: 27,730 versus 11,117 for FerretDB. The gap is 16,613 stars.
Valkey was pushed more recently: 17 November 2026 versus 05 June 2026 for FerretDB. That is 165 days apart.
Yes. This catalog marks both FerretDB and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Valkey is listed as BSD-3-Clause, 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.
Valkey scores 96.5 and FerretDB scores 77.3. This page calls that a decisive lead for Valkey.