Skip to content
DevUtils Online

Databases

dragonfly vs lowdb

dragonfly leads by 1.5 · narrow

A · leads

dragonfly

84.8

31,878 stars · license n/a

B

lowdb

83.3

22,578 stars · MIT

dragonfly versus lowdb is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dragonfly is written mainly in C++; lowdb is written mainly in JavaScript. The composite score is 84.8 for dragonfly and 83.3 for lowdb.

dragonfly has 31,878 GitHub stars to lowdb's 22,578, a gap of 9,300 (1.41×). Forks are 1,294 for dragonfly and 962 for lowdb. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 96.

Push history: dragonfly was last pushed on 17 November 2026 (0 days ago), and lowdb was last pushed on 27 March 2026 (234 days ago). Open issues stand at 209 for dragonfly (0.007 per star) and 18 for lowdb (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 36.

dragonfly is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. License scores in this pair are 30 for dragonfly and 96 for lowdb. This is a procurement signal, not legal advice.

Only lowdb is marked self-hostable here (22,578 stars, deploy score 100). dragonfly is not (31,878 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: dragonfly is unpriced in this catalog, lowdb is open source.

The lead is split. dragonfly is furthest ahead on recent activity (100 to 36), while lowdb is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

dragonfly finishes ahead at 84.8 against lowdb at 83.3, a 1.5 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

dragonfly versus lowdb metrics
Signal dragonfly lowdb
GitHub stars 31,878 22,578
Forks 1,294 962
Open issues 209 18
Adoption 100 97
Activity 100 36
Community 100 96
Issue health 84 96
License 30 96
Self-hosting 35 100
Composite 84.8 83.3

Questions this page answers

Which has more GitHub stars, dragonfly or lowdb?

dragonfly has more GitHub stars: 31,878 versus 22,578 for lowdb. The gap is 9,300 stars.

Which was updated more recently, dragonfly or lowdb?

dragonfly was pushed more recently: 17 November 2026 versus 27 March 2026 for lowdb. That is 234 days apart.

Can I self-host both dragonfly and lowdb?

Only lowdb is marked self-hostable. dragonfly is not.

Which license is easier to embed in a commercial product, dragonfly or lowdb?

dragonfly is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the dragonfly vs lowdb score?

dragonfly scores 84.8 and lowdb scores 83.3. This page calls that a narrow lead for dragonfly.

Related comparisons