A
activitywatch
91.3
19,662 stars · MPL-2.0
Analytics
PostHog leads by 3.4 · narrow
A
91.3
19,662 stars · MPL-2.0
B · leads
94.7
40,849 stars · MIT
activitywatch versus PostHog is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 91.3 for activitywatch and 94.7 for PostHog.
PostHog has 40,849 GitHub stars to activitywatch's 19,662, a gap of 21,187 (2.08×). Forks are 1,078 for activitywatch and 3,696 for PostHog. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 85 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and PostHog was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 4,463 for PostHog (0.109 per star). Issue-health scores are 84 and 52; 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. PostHog 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 PostHog. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and PostHog (40,849 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, PostHog is freemium.
The lead is split. activitywatch is furthest ahead on issue health (84 to 52), while PostHog is furthest ahead on license flexibility (96 to 78). Choose the dimension a rollout cannot compromise on.
PostHog finishes ahead at 94.7 against activitywatch at 91.3, a 3.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 | PostHog |
|---|---|---|
| GitHub stars | 19,662 | 40,849 |
| Forks | 1,078 | 3,696 |
| Open issues | 132 | 4,463 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 85 | 100 |
| Issue health | 84 | 52 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.3 | 94.7 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
PostHog is a product-analytics suite: events, funnels, session replay, and feature flags. The core is open source and most teams choose between self-hosting and PostHog Cloud.
PostHog has more GitHub stars: 40,849 versus 19,662 for activitywatch. The gap is 21,187 stars.
PostHog 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 PostHog 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. PostHog 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.
PostHog scores 94.7 and activitywatch scores 91.3. This page calls that a narrow lead for PostHog.