A
langwatch
83.5
5,042 stars · Apache-2.0
Analytics
Umami leads by 15.6 · decisive
A
83.5
5,042 stars · Apache-2.0
B · leads
99.1
40,194 stars · MIT
langwatch 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 83.5 for langwatch and 99.1 for Umami.
Umami has 40,194 GitHub stars to langwatch's 5,042, a gap of 35,152 (7.97×). Forks are 433 for langwatch and 8,567 for Umami. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 67 versus 100.
Push history: langwatch 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 492 for langwatch (0.098 per star) and 136 for Umami (0.003 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
langwatch 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 langwatch and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both langwatch (5,042 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: langwatch 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 issue health at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against langwatch at 83.5, a 15.6 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 | langwatch | Umami |
|---|---|---|
| GitHub stars | 5,042 | 40,194 |
| Forks | 433 | 8,567 |
| Open issues | 492 | 136 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 67 | 100 |
| Issue health | 52 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 83.5 | 99.1 |
Open-Source Agent Observability & Evals for AI Platform teams. Trace, test, route and govern every agent & coding assistant in the company.
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 5,042 for langwatch. The gap is 35,152 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both langwatch and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
langwatch 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 langwatch scores 83.5. This page calls that a decisive lead for Umami.