A
activitywatch
92.1
19,662 stars · MPL-2.0
Analytics
redash leads by 4.4 · narrow
A
92.1
19,662 stars · MPL-2.0
B · leads
96.5
28,887 stars · BSD-2-Clause
activitywatch versus redash 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; redash is written mainly in TypeScript. The composite score is 92.1 for activitywatch and 96.5 for redash.
redash has 28,887 GitHub stars to activitywatch's 19,662, a gap of 9,225 (1.47×). Forks are 1,078 for activitywatch and 4,645 for redash. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 83 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and redash was last pushed on 14 November 2026 (3 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 780 for redash (0.027 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. redash is listed as BSD-2-Clause, 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 redash. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and redash (28,887 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, redash is open source.
The lead is split. activitywatch is furthest ahead on issue health (84 to 70), while redash is furthest ahead on license flexibility (96 to 78). Choose the dimension a rollout cannot compromise on.
redash finishes ahead at 96.5 against activitywatch at 92.1, a 4.4 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 | redash |
|---|---|---|
| GitHub stars | 19,662 | 28,887 |
| Forks | 1,078 | 4,645 |
| Open issues | 132 | 780 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 83 | 100 |
| Issue health | 84 | 70 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.1 | 96.5 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
redash has more GitHub stars: 28,887 versus 19,662 for activitywatch. The gap is 9,225 stars.
activitywatch was pushed more recently: 15 November 2026 versus 14 November 2026 for redash. That is 1 days apart.
Yes. This catalog marks both activitywatch and redash 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. redash is listed as BSD-2-Clause, 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.
redash scores 96.5 and activitywatch scores 92.1. This page calls that a narrow lead for redash.