A
partytown
89.4
13,817 stars · MIT
Analytics
Umami leads by 9.7 · clear
A
89.4
13,817 stars · MIT
B · leads
99.1
40,194 stars · MIT
partytown versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 89.4 for partytown and 99.1 for Umami.
Umami has 40,194 GitHub stars to partytown's 13,817, a gap of 26,377 (2.91×). Forks are 460 for partytown and 8,567 for Umami. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 68 versus 100.
Push history: partytown was last pushed on 09 November 2026 (8 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1 for partytown (0.000 per star) and 136 for Umami (0.003 per star). Issue-health scores are 96 and 96; activity scores are 92 and 100.
Both partytown and Umami are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both partytown (13,817 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: partytown is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 32 points (68 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against partytown at 89.4, a 9.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 | partytown | Umami |
|---|---|---|
| GitHub stars | 13,817 | 40,194 |
| Forks | 460 | 8,567 |
| Open issues | 1 | 136 |
| Adoption | 90 | 100 |
| Activity | 92 | 100 |
| Community | 68 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 99.1 |
Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
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 13,817 for partytown. The gap is 26,377 stars.
Umami was pushed more recently: 17 November 2026 versus 09 November 2026 for partytown. That is 8 days apart.
Yes. This catalog marks both partytown and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
partytown 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. 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 partytown scores 89.4. This page calls that a clear lead for Umami.