A · leads
activitywatch
95.8
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 7.6 · clear
A · leads
95.8
19,662 stars · MPL-2.0
B
88.2
13,157 stars · license n/a
activitywatch versus openreplay 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; openreplay is written mainly in TypeScript. The composite score is 95.8 for activitywatch and 88.2 for openreplay.
activitywatch has 19,662 GitHub stars to openreplay's 13,157, a gap of 6,505 (1.49×). Forks are 1,078 for activitywatch and 891 for openreplay. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 97.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and openreplay was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 193 for openreplay (0.015 per star). Issue-health scores are 84 and 84; 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. openreplay is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 78 for activitywatch and 30 for openreplay. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and openreplay (13,157 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, openreplay is unpriced in this catalog.
activitywatch is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 48 points (78 vs 30), and the tightest is self-hosting at 0 points (100 vs 100).
activitywatch finishes ahead at 95.8 against openreplay at 88.2, a 7.6 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 | openreplay |
|---|---|---|
| GitHub stars | 19,662 | 13,157 |
| Forks | 1,078 | 891 |
| Open issues | 132 | 193 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 97 |
| Issue health | 84 | 84 |
| License | 78 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 95.8 | 88.2 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
activitywatch has more GitHub stars: 19,662 versus 13,157 for openreplay. The gap is 6,505 stars.
openreplay 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 openreplay 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. openreplay is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
activitywatch scores 95.8 and openreplay scores 88.2. This page calls that a clear lead for activitywatch.