A
lowdb
80.7
22,578 stars · MIT
Databases
rocksdb leads by 10.2 · clear
A
80.7
22,578 stars · MIT
B · leads
90.9
32,285 stars · GPL-2.0
lowdb versus rocksdb 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; rocksdb is written mainly in C++. The composite score is 80.7 for lowdb and 90.9 for rocksdb.
rocksdb has 32,285 GitHub stars to lowdb's 22,578, a gap of 9,707 (1.43×). Forks are 962 for lowdb and 7,033 for rocksdb. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 78 versus 100.
Push history: lowdb was last pushed on 27 March 2026 (234 days ago), and rocksdb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 18 for lowdb (0.001 per star) and 1,855 for rocksdb (0.057 per star). Issue-health scores are 96 and 52; 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. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for lowdb and 64 for rocksdb. This is a procurement signal, not legal advice.
In Databases, both lowdb (22,578 stars) and rocksdb (32,285 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, rocksdb is open source.
The lead is split. lowdb is furthest ahead on issue health (96 to 52), while rocksdb is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
rocksdb finishes ahead at 90.9 against lowdb at 80.7, a 10.2 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 | rocksdb |
|---|---|---|
| GitHub stars | 22,578 | 32,285 |
| Forks | 962 | 7,033 |
| Open issues | 18 | 1,855 |
| Adoption | 97 | 100 |
| Activity | 36 | 100 |
| Community | 78 | 100 |
| Issue health | 96 | 52 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 80.7 | 90.9 |
Simple and fast JSON database
A library that provides an embeddable, persistent key-value store for fast storage.
rocksdb has more GitHub stars: 32,285 versus 22,578 for lowdb. The gap is 9,707 stars.
rocksdb 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 rocksdb 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. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
rocksdb scores 90.9 and lowdb scores 80.7. This page calls that a clear lead for rocksdb.