A
activitywatch
90.3
19,662 stars · MPL-2.0
Analytics
Umami leads by 8.8 · clear
A
90.3
19,662 stars · MPL-2.0
B · leads
99.1
40,194 stars · MIT
activitywatch versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. activitywatch is written mainly in Python; Umami is written mainly in TypeScript. The composite score is 90.3 for activitywatch and 99.1 for Umami.
Umami has 40,194 GitHub stars to activitywatch's 19,662, a gap of 20,532 (2.04×). Forks are 1,078 for activitywatch and 8,567 for Umami. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 77 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 136 for Umami (0.003 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
activitywatch is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. 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 78 for activitywatch and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 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: activitywatch is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is fork community at 23 points (77 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against activitywatch at 90.3, a 8.8 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 | activitywatch | Umami |
|---|---|---|
| GitHub stars | 19,662 | 40,194 |
| Forks | 1,078 | 8,567 |
| Open issues | 132 | 136 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 77 | 100 |
| Issue health | 84 | 96 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.3 | 99.1 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
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 19,662 for activitywatch. The gap is 20,532 stars.
Umami was pushed more recently: 17 November 2026 versus 15 November 2026 for activitywatch. That is 2 days apart.
Yes. This catalog marks both activitywatch and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
activitywatch is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. 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 activitywatch scores 90.3. This page calls that a clear lead for Umami.