A · leads
Umami
99.1
40,194 stars · MIT
Analytics
Umami leads by 30.4 · decisive
A · leads
99.1
40,194 stars · MIT
B
68.7
3,012 stars · BSD-3-Clause
Umami versus weld is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Umami is written mainly in TypeScript; weld is written mainly in Rust. The composite score is 99.1 for Umami and 68.7 for weld.
Umami has 40,194 GitHub stars to weld's 3,012, a gap of 37,182 (13.34×). Forks are 8,567 for Umami and 253 for weld. On the log scale used inside this pair, adoption is 100 versus 76, and the fork community is 100 versus 61.
Push history: Umami was last pushed on 17 November 2026 (0 days ago), and weld was last pushed on 13 April 2026 (218 days ago). Open issues stand at 136 for Umami (0.003 per star) and 75 for weld (0.025 per star). Issue-health scores are 96 and 70; activity scores are 100 and 36.
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. weld is listed as BSD-3-Clause, 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 Umami and 96 for weld. This is a procurement signal, not legal advice.
In Analytics, both Umami (40,194 stars) and weld (3,012 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: Umami is open source, weld 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 64 points (100 vs 36), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against weld at 68.7, a 30.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 | Umami | weld |
|---|---|---|
| GitHub stars | 40,194 | 3,012 |
| Forks | 8,567 | 253 |
| Open issues | 136 | 75 |
| Adoption | 100 | 76 |
| Activity | 100 | 36 |
| Community | 100 | 61 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 68.7 |
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.
High-performance runtime for data analytics applications
Umami has more GitHub stars: 40,194 versus 3,012 for weld. The gap is 37,182 stars.
Umami was pushed more recently: 17 November 2026 versus 13 April 2026 for weld. That is 218 days apart.
Yes. This catalog marks both Umami and weld as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. weld is listed as BSD-3-Clause, 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 weld scores 68.7. This page calls that a decisive lead for Umami.