ActivityWatch

Automatically track how you spend time on your devices.

Healthy · 73
73/100
Healthy

Actively maintained with regular releases.

Maintenance 15/40
Releases 25/25
Community 18/20
Momentum 15/15

Commit activity more than 38% of tracked projects; popularity more than 88%. How this is calculated.

Commits, last 11 months

2025-12: 0 commits 2026-01: 0 commits 2026-02: 3 commits 2026-03: 11 commits 2026-04: 26 commits 2026-05: 10 commits 2026-06: 8 commits 2026-07: 23 commits 2026-08: 21 commits 2026-09: 38 commits 2026-10: 44 commits
2025-12 184 total 2026-10
Stars20k
Latest releasev0.14.3 · 15 Nov 2026
Repo updated15 Nov 2026
LicenceMPL-2.0
Built withPython

Is ActivityWatch actively maintained?

Over the last 11 months the project absorbed 184 commits, of which 103 arrived in the most recent quarter — roughly 34 commits a month.

Activity is accelerating: the last quarter carried 151% more commits than the one before it.

The most recent tagged release, v0.14.3, shipped within the last month — a current, installable version exists today.

Of the 12 projects we track in Time Tracking, ActivityWatch ranks #3 by health score — in the top quarter of its category.

What ActivityWatch actually does

ActivityWatch is an open-source application designed to automatically monitor and record your device usage. It logs your active window titles, browser history, and application runtimes to give you an overview of how your hours are spent. All data remains locally stored on your machine rather than being sent to a third-party cloud service.

Best fit: It is well-suited for freelancers, developers, and privacy-conscious users who want to audit their daily habits without sharing telemetry data with external companies.

Worth knowing: The project relies on a beta release cycle and relies on various client-side watchers that can occasionally require manual troubleshooting across different operating systems. You should also expect to manage local storage growth over time as event logs accumulate.

Deployment notes

Because the backend is built with Python, running it as a persistent server typically requires setting up a process manager like systemd and ensuring adequate persistent storage for the local database. If you expose the web UI externally, you will need to configure a reverse proxy to handle TLS termination securely.


ActivityWatch as a replacement for


Alternatives to ActivityWatch

Projects in the same categories, ordered by health score.