A
snowplow
84.4
7,051 stars · Apache-2.0
Analytics
Umami leads by 14.7 · clear
A
84.4
7,051 stars · Apache-2.0
B · leads
99.1
40,194 stars · MIT
snowplow versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. snowplow is written mainly in Scala; Umami is written mainly in TypeScript. The composite score is 84.4 for snowplow and 99.1 for Umami.
Umami has 40,194 GitHub stars to snowplow's 7,051, a gap of 33,143 (5.70×). Forks are 1,171 for snowplow and 8,567 for Umami. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 78 versus 100.
Push history: snowplow was last pushed on 19 October 2026 (28 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 59 for snowplow (0.008 per star) and 136 for Umami (0.003 per star). Issue-health scores are 84 and 96; activity scores are 78 and 100.
snowplow 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. 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 96 for snowplow and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both snowplow (7,051 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: snowplow is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 22 points (78 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against snowplow at 84.4, a 14.7 point clear 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 | snowplow | Umami |
|---|---|---|
| GitHub stars | 7,051 | 40,194 |
| Forks | 1,171 | 8,567 |
| Open issues | 59 | 136 |
| Adoption | 84 | 100 |
| Activity | 78 | 100 |
| Community | 78 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.4 | 99.1 |
The leader in Customer Data Infrastructure
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 7,051 for snowplow. The gap is 33,143 stars.
Umami was pushed more recently: 17 November 2026 versus 19 October 2026 for snowplow. That is 28 days apart.
Yes. This catalog marks both snowplow and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
snowplow 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. 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 snowplow scores 84.4. This page calls that a clear lead for Umami.