A · leads
activitywatch
93.6
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 2.7 · narrow
A · leads
93.6
19,662 stars · MPL-2.0
B
90.9
22,032 stars · GPL-3.0
activitywatch versus Matomo 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; Matomo is written mainly in PHP. The composite score is 93.6 for activitywatch and 90.9 for Matomo.
Matomo has 22,032 GitHub stars to activitywatch's 19,662, a gap of 2,370 (1.12×). Forks are 1,078 for activitywatch and 2,938 for Matomo. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 88 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and Matomo was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 2,563 for Matomo (0.116 per star). Issue-health scores are 84 and 52; 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. Matomo is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 78 for activitywatch and 64 for Matomo. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and Matomo (22,032 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, Matomo is open source.
The lead is split. activitywatch is furthest ahead on issue health (84 to 52), while Matomo is furthest ahead on fork community (100 to 88). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 93.6 against Matomo at 90.9, a 2.7 point narrow 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 | Matomo |
|---|---|---|
| GitHub stars | 19,662 | 22,032 |
| Forks | 1,078 | 2,938 |
| Open issues | 132 | 2,563 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 88 | 100 |
| Issue health | 84 | 52 |
| License | 78 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 93.6 | 90.9 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
Matomo is a web analytics platform built as a privacy-oriented alternative to Google Analytics. It has a long plugin history and is designed to run on your own server.
Matomo has more GitHub stars: 22,032 versus 19,662 for activitywatch. The gap is 2,370 stars.
Matomo 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 Matomo 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. Matomo is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
activitywatch scores 93.6 and Matomo scores 90.9. This page calls that a narrow lead for activitywatch.