A
LocustDB
53.2
1,646 stars · license n/a
Analytics
Umami leads by 45.9 · decisive
A
53.2
1,646 stars · license n/a
B · leads
99.1
40,194 stars · MIT
LocustDB versus Umami 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; Umami is written mainly in TypeScript. The composite score is 53.2 for LocustDB and 99.1 for Umami.
Umami has 40,194 GitHub stars to LocustDB's 1,646, a gap of 38,548 (24.42×). Forks are 75 for LocustDB and 8,567 for Umami. On the log scale used inside this pair, adoption is 70 versus 100, and the fork community is 48 versus 100.
Push history: LocustDB was last pushed on 23 April 2026 (208 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 14 for LocustDB (0.009 per star) and 136 for Umami (0.003 per star). Issue-health scores are 84 and 96; 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. Umami 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 LocustDB and 96 for Umami. This is a procurement signal, not legal advice.
Only Umami is marked self-hostable here (40,194 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, Umami is open source.
Umami is ahead on every scored dimension that is not level. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is issue health at 12 points (84 vs 96).
Umami finishes ahead at 99.1 against LocustDB at 53.2, a 45.9 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 | Umami |
|---|---|---|
| GitHub stars | 1,646 | 40,194 |
| Forks | 75 | 8,567 |
| Open issues | 14 | 136 |
| Adoption | 70 | 100 |
| Activity | 36 | 100 |
| Community | 48 | 100 |
| Issue health | 84 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 53.2 | 99.1 |
Blazingly fast analytics database that will rapidly devour all of your data.
Umami is a small web analytics product with a simple dashboard over page and event data. It is MIT-licensed and is usually chosen when a team wants a short self-hosted setup.
Umami has more GitHub stars: 40,194 versus 1,646 for LocustDB. The gap is 38,548 stars.
Umami was pushed more recently: 17 November 2026 versus 23 April 2026 for LocustDB. That is 208 days apart.
Only Umami 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. Umami 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.
Umami scores 99.1 and LocustDB scores 53.2. This page calls that a decisive lead for Umami.