A · leads
Umami
99.1
40,194 stars · MIT
Analytics
Umami leads by 33.3 · decisive
A · leads
99.1
40,194 stars · MIT
B
65.8
2,839 stars · Apache-2.0
Umami versus whylogs 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; whylogs is written mainly in Jupyter Notebook. The composite score is 99.1 for Umami and 65.8 for whylogs.
Umami has 40,194 GitHub stars to whylogs's 2,839, a gap of 37,355 (14.16×). Forks are 8,567 for Umami and 144 for whylogs. On the log scale used inside this pair, adoption is 100 versus 75, and the fork community is 100 versus 55.
Push history: Umami was last pushed on 17 November 2026 (0 days ago), and whylogs was last pushed on 10 January 2025 (675 days ago). Open issues stand at 136 for Umami (0.003 per star) and 4 for whylogs (0.001 per star). Issue-health scores are 96 and 96; activity scores are 100 and 16.
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. whylogs 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. License scores in this pair are 96 for Umami and 96 for whylogs. This is a procurement signal, not legal advice.
In Analytics, both Umami (40,194 stars) and whylogs (2,839 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, whylogs 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 recent activity at 84 points (100 vs 16), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against whylogs at 65.8, a 33.3 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 | whylogs |
|---|---|---|
| GitHub stars | 40,194 | 2,839 |
| Forks | 8,567 | 144 |
| Open issues | 136 | 4 |
| Adoption | 100 | 75 |
| Activity | 100 | 16 |
| Community | 100 | 55 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 65.8 |
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.
An open-source data logging library for machine learning models and data pipelines. 📚 Provides visibility into data quality & model performance over time. 🛡️ Supports privacy-preserving data collection, ensuring safety & robustness. 📈
Umami has more GitHub stars: 40,194 versus 2,839 for whylogs. The gap is 37,355 stars.
Umami was pushed more recently: 17 November 2026 versus 10 January 2025 for whylogs. That is 675 days apart.
Yes. This catalog marks both Umami and whylogs 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. whylogs 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Umami scores 99.1 and whylogs scores 65.8. This page calls that a decisive lead for Umami.