A · leads
activitywatch
95.8
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 4.6 · narrow
A · leads
95.8
19,662 stars · MPL-2.0
B
91.2
10,891 stars · AGPL-3.0
activitywatch versus lago 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; lago is written mainly in Go. The composite score is 95.8 for activitywatch and 91.2 for lago.
activitywatch has 19,662 GitHub stars to lago's 10,891, a gap of 8,771 (1.81×). Forks are 1,078 for activitywatch and 798 for lago. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 96.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and lago was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 17 for lago (0.002 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. lago is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 78 for activitywatch and 52 for lago. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and lago (10,891 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, lago is open source.
The lead is split. activitywatch is furthest ahead on license flexibility (78 to 52), while lago is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 95.8 against lago at 91.2, a 4.6 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 | lago |
|---|---|---|
| GitHub stars | 19,662 | 10,891 |
| Forks | 1,078 | 798 |
| Open issues | 132 | 17 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 84 | 96 |
| License | 78 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 95.8 | 91.2 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
activitywatch has more GitHub stars: 19,662 versus 10,891 for lago. The gap is 8,771 stars.
lago 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 lago 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. lago is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
activitywatch scores 95.8 and lago scores 91.2. This page calls that a narrow lead for activitywatch.