A
lowdb
84.6
22,578 stars · MIT
Databases
neon leads by 2.7 · narrow
A
84.6
22,578 stars · MIT
B · leads
87.3
23,335 stars · Apache-2.0
lowdb versus neon 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; neon is written mainly in Rust. The composite score is 84.6 for lowdb and 87.3 for neon.
neon has 23,335 GitHub stars to lowdb's 22,578, a gap of 757 (1.03×). Forks are 962 for lowdb and 1,139 for neon. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 98 versus 100.
Push history: lowdb was last pushed on 27 March 2026 (234 days ago), and neon was last pushed on 31 August 2026 (78 days ago). Open issues stand at 18 for lowdb (0.001 per star) and 589 for neon (0.025 per star). Issue-health scores are 96 and 70; activity scores are 36 and 58.
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. neon 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. License scores in this pair are 96 for lowdb and 96 for neon. This is a procurement signal, not legal advice.
In Databases, both lowdb (22,578 stars) and neon (23,335 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, neon is open source.
The lead is split. lowdb is furthest ahead on issue health (96 to 70), while neon is furthest ahead on recent activity (58 to 36). Choose the dimension a rollout cannot compromise on.
neon finishes ahead at 87.3 against lowdb at 84.6, a 2.7 point narrow 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 | neon |
|---|---|---|
| GitHub stars | 22,578 | 23,335 |
| Forks | 962 | 1,139 |
| Open issues | 18 | 589 |
| Adoption | 100 | 100 |
| Activity | 36 | 58 |
| Community | 98 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.6 | 87.3 |
Simple and fast JSON database
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
neon has more GitHub stars: 23,335 versus 22,578 for lowdb. The gap is 757 stars.
neon was pushed more recently: 31 August 2026 versus 27 March 2026 for lowdb. That is 156 days apart.
Yes. This catalog marks both lowdb and neon 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. neon 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.
neon scores 87.3 and lowdb scores 84.6. This page calls that a narrow lead for neon.