A
lowdb
83.5
22,578 stars · MIT
Databases
Valkey leads by 13.0 · clear
A
83.5
22,578 stars · MIT
B · leads
96.5
27,730 stars · BSD-3-Clause
lowdb versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. lowdb is written mainly in JavaScript; Valkey is written mainly in C. The composite score is 83.5 for lowdb and 96.5 for Valkey.
Valkey has 27,730 GitHub stars to lowdb's 22,578, a gap of 5,152 (1.23×). Forks are 962 for lowdb and 1,540 for Valkey. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 94 versus 100.
Push history: lowdb was last pushed on 27 March 2026 (234 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 18 for lowdb (0.001 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 96 and 70; activity scores are 36 and 100.
lowdb 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. 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 lowdb and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both lowdb (22,578 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: lowdb is open source, Valkey is open source.
The lead is split. lowdb is furthest ahead on issue health (96 to 70), while Valkey is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
Valkey finishes ahead at 96.5 against lowdb at 83.5, a 13.0 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 | lowdb | Valkey |
|---|---|---|
| GitHub stars | 22,578 | 27,730 |
| Forks | 962 | 1,540 |
| Open issues | 18 | 1,045 |
| Adoption | 98 | 100 |
| Activity | 36 | 100 |
| Community | 94 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 83.5 | 96.5 |
Simple and fast JSON database
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 22,578 for lowdb. The gap is 5,152 stars.
Valkey was pushed more recently: 17 November 2026 versus 27 March 2026 for lowdb. That is 234 days apart.
Yes. This catalog marks both lowdb and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
lowdb 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. 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 lowdb scores 83.5. This page calls that a clear lead for Valkey.