A · leads
activitywatch
95.8
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 3.0 · narrow
A · leads
95.8
19,662 stars · MPL-2.0
B
92.8
10,049 stars · MIT
activitywatch versus ClickStack 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; ClickStack is written mainly in TypeScript. The composite score is 95.8 for activitywatch and 92.8 for ClickStack.
activitywatch has 19,662 GitHub stars to ClickStack's 10,049, a gap of 9,613 (1.96×). Forks are 1,078 for activitywatch and 526 for ClickStack. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 90.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and ClickStack was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 297 for ClickStack (0.030 per star). Issue-health scores are 84 and 70; 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. ClickStack 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 ClickStack. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and ClickStack (10,049 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, ClickStack is open source.
The lead is split. activitywatch is furthest ahead on issue health (84 to 70), while ClickStack is furthest ahead on license flexibility (96 to 78). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 95.8 against ClickStack at 92.8, a 3.0 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 | ClickStack |
|---|---|---|
| GitHub stars | 19,662 | 10,049 |
| Forks | 1,078 | 526 |
| Open issues | 132 | 297 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 90 |
| Issue health | 84 | 70 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.8 | 92.8 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
Resolve production issues, fast. An open source observability platform unifying session replays, logs, metrics, traces and errors powered by ClickHouse and OpenTelemetry.
activitywatch has more GitHub stars: 19,662 versus 10,049 for ClickStack. The gap is 9,613 stars.
ClickStack 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 ClickStack 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. ClickStack 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.
activitywatch scores 95.8 and ClickStack scores 92.8. This page calls that a narrow lead for activitywatch.