A
stampede
58.7
1,755 stars · AGPL-3.0
Analytics
Umami leads by 40.4 · decisive
A
58.7
1,755 stars · AGPL-3.0
B · leads
99.1
40,194 stars · MIT
stampede versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. stampede is written mainly in Java; Umami is written mainly in TypeScript. The composite score is 58.7 for stampede and 99.1 for Umami.
Umami has 40,194 GitHub stars to stampede's 1,755, a gap of 38,439 (22.90×). Forks are 116 for stampede and 8,567 for Umami. On the log scale used inside this pair, adoption is 70 versus 100, and the fork community is 53 versus 100.
Push history: stampede was last pushed on 25 October 2018 (2945 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 6 for stampede (0.003 per star) and 136 for Umami (0.003 per star). Issue-health scores are 96 and 96; activity scores are 16 and 100.
stampede 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. 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 52 for stampede and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both stampede (1,755 stars) and Umami (40,194 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: stampede is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: issue health, self-hosting. The widest gap is recent activity at 84 points (16 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against stampede at 58.7, a 40.4 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 | stampede | Umami |
|---|---|---|
| GitHub stars | 1,755 | 40,194 |
| Forks | 116 | 8,567 |
| Open issues | 6 | 136 |
| Adoption | 70 | 100 |
| Activity | 16 | 100 |
| Community | 53 | 100 |
| Issue health | 96 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 58.7 | 99.1 |
The ToroDB solution to provide better analytics on top of MongoDB and make it easier to migrate from MongoDB to SQL
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,755 for stampede. The gap is 38,439 stars.
Umami was pushed more recently: 17 November 2026 versus 25 October 2018 for stampede. That is 2945 days apart.
Yes. This catalog marks both stampede and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
stampede 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. 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 stampede scores 58.7. This page calls that a decisive lead for Umami.