A
helicone
86.7
6,286 stars · Apache-2.0
Analytics
Umami leads by 12.4 · clear
A
86.7
6,286 stars · Apache-2.0
B · leads
99.1
40,194 stars · MIT
helicone 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 86.7 for helicone and 99.1 for Umami.
Umami has 40,194 GitHub stars to helicone's 6,286, a gap of 33,908 (6.39×). Forks are 706 for helicone and 8,567 for Umami. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 72 versus 100.
Push history: helicone was last pushed on 17 November 2026 (0 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 194 for helicone (0.031 per star) and 136 for Umami (0.003 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
helicone 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 helicone and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both helicone (6,286 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: helicone is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 28 points (72 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against helicone at 86.7, a 12.4 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 | helicone | Umami |
|---|---|---|
| GitHub stars | 6,286 | 40,194 |
| Forks | 706 | 8,567 |
| Open issues | 194 | 136 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 72 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.7 | 99.1 |
🧊 Open source LLM observability platform. One line of code to monitor, evaluate, and experiment. YC W23 🍓
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 6,286 for helicone. The gap is 33,908 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both helicone and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
helicone 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 helicone scores 86.7. This page calls that a clear lead for Umami.