A · leads
activitywatch
95.3
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 16.6 · decisive
A · leads
95.3
19,662 stars · MPL-2.0
B
78.7
11,031 stars · MIT
activitywatch versus dashboards 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; dashboards is written mainly in HTML. The composite score is 95.3 for activitywatch and 78.7 for dashboards.
activitywatch has 19,662 GitHub stars to dashboards's 11,031, a gap of 8,631 (1.78×). Forks are 1,078 for activitywatch and 1,386 for dashboards. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 96 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and dashboards was last pushed on 02 November 2021 (1841 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 6 for dashboards (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 16.
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. dashboards 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 dashboards. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and dashboards (11,031 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, dashboards is open source.
The lead is split. activitywatch is furthest ahead on recent activity (100 to 16), while dashboards is furthest ahead on license flexibility (96 to 78). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 95.3 against dashboards at 78.7, a 16.6 point decisive 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 | dashboards |
|---|---|---|
| GitHub stars | 19,662 | 11,031 |
| Forks | 1,078 | 1,386 |
| Open issues | 132 | 6 |
| Adoption | 100 | 94 |
| Activity | 100 | 16 |
| Community | 96 | 100 |
| Issue health | 84 | 96 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.3 | 78.7 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
Responsive dashboard templates 📊✨
activitywatch has more GitHub stars: 19,662 versus 11,031 for dashboards. The gap is 8,631 stars.
activitywatch was pushed more recently: 15 November 2026 versus 02 November 2021 for dashboards. That is 1839 days apart.
Yes. This catalog marks both activitywatch and dashboards 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. dashboards 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.3 and dashboards scores 78.7. This page calls that a decisive lead for activitywatch.