A
talivia
83.3
2,290 stars · MIT
Analytics
Umami leads by 15.8 · decisive
A
83.3
2,290 stars · MIT
B · leads
99.1
40,194 stars · MIT
talivia 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.3 for talivia and 99.1 for Umami.
Umami has 40,194 GitHub stars to talivia's 2,290, a gap of 37,904 (17.55×). Forks are 119 for talivia and 8,567 for Umami. On the log scale used inside this pair, adoption is 73 versus 100, and the fork community is 53 versus 100.
Push history: talivia was last pushed on 16 November 2026 (1 day ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3 for talivia (0.001 per star) and 136 for Umami (0.003 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
Both talivia 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 talivia (2,290 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: talivia is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 47 points (53 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against talivia at 83.3, a 15.8 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 | talivia | Umami |
|---|---|---|
| GitHub stars | 2,290 | 40,194 |
| Forks | 119 | 8,567 |
| Open issues | 3 | 136 |
| Adoption | 73 | 100 |
| Activity | 100 | 100 |
| Community | 53 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 83.3 | 99.1 |
Open-source, self-hosted revenue-first analytics for founders: web analytics, Session Replay, revenue attribution, and customer revenue integrations. datafast alternative
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 2,290 for talivia. The gap is 37,904 stars.
Umami was pushed more recently: 17 November 2026 versus 16 November 2026 for talivia. That is 1 days apart.
Yes. This catalog marks both talivia and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
talivia 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 talivia scores 83.3. This page calls that a decisive lead for Umami.