A
LocustDB
52.8
1,646 stars · license n/a
Analytics
Metabase leads by 36.6 · decisive
A
52.8
1,646 stars · license n/a
B · leads
89.4
50,382 stars · AGPL-3.0
LocustDB versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. LocustDB is written mainly in Rust; Metabase is written mainly in Clojure. The composite score is 52.8 for LocustDB and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to LocustDB's 1,646, a gap of 48,736 (30.61×). Forks are 75 for LocustDB and 7,016 for Metabase. On the log scale used inside this pair, adoption is 68 versus 100, and the fork community is 49 versus 100.
Push history: LocustDB was last pushed on 23 April 2026 (208 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 14 for LocustDB (0.009 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 84 and 52; activity scores are 36 and 100.
LocustDB 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. Metabase is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 30 for LocustDB and 52 for Metabase. This is a procurement signal, not legal advice.
Only Metabase is marked self-hostable here (50,382 stars, deploy score 100). LocustDB is not (1,646 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: LocustDB is unpriced in this catalog, Metabase is freemium.
The lead is split. LocustDB is furthest ahead on issue health (84 to 52), while Metabase is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against LocustDB at 52.8, a 36.6 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 | LocustDB | Metabase |
|---|---|---|
| GitHub stars | 1,646 | 50,382 |
| Forks | 75 | 7,016 |
| Open issues | 14 | 4,696 |
| Adoption | 68 | 100 |
| Activity | 36 | 100 |
| Community | 49 | 100 |
| Issue health | 84 | 52 |
| License | 30 | 52 |
| Self-hosting | 35 | 100 |
| Composite | 52.8 | 89.4 |
Blazingly fast analytics database that will rapidly devour all of your data.
Metabase is a business-intelligence tool that lets teams ask questions of a SQL database without writing a report from scratch. It is commonly self-hosted next to the warehouse it reads.
Metabase has more GitHub stars: 50,382 versus 1,646 for LocustDB. The gap is 48,736 stars.
Metabase was pushed more recently: 17 November 2026 versus 23 April 2026 for LocustDB. That is 208 days apart.
Only Metabase is marked self-hostable. LocustDB is not.
LocustDB 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. Metabase is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and LocustDB scores 52.8. This page calls that a decisive lead for Metabase.