ActivityWatchvsCrossWatch
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| ActivityWatch | CrossWatch | |
|---|---|---|
| Score | 80/100 | 55/100 |
| Rank in category | #1 of 11 in Time Tracking | #44 of 141 in Media Management |
| GitHub stars | 19 785 | 1 020 |
| Stars, last 30 days | +512 | +58 |
| Stable releases, 12 months | 15 | 57 |
| Latest release | v0.14.3 · 13 Nov 2026 | v0.14.8 · 22 Nov 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | No | Yes |
| License | MPL-2.0 | AGPL-3.0 |
| Main language | Python | Python |
Which one should you pick?
ActivityWatch scores 80/100 against 55/100 for CrossWatch, so it is the safer default.
CrossWatch ships more often: 57 stable releases in the past year, against 15 for ActivityWatch.
ActivityWatch is growing faster right now (+512 stars in 30 days).
Key differences
- License: ActivityWatch is MPL-2.0, CrossWatch is AGPL-3.0.
- Only CrossWatch ships an official Docker image.
- Platforms only ActivityWatch lists: Android, AppImage, Arch Linux, Debian and 3 more.
- Platforms only CrossWatch lists: Docker.
- Features only ActivityWatch lists: Application tracking, Categories, Data Export, REST API.
- Features only CrossWatch lists: Analyzer and debugging tools, Anime ID mapping, CLI-only mode, Custom mappings and 11 more.
ActivityWatch details →CrossWatch details →
Swap a project
Keep ActivityWatch, compare it with
Keep CrossWatch, compare it with