A · leads
activitywatch
91.4
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 2.8 · narrow
A · leads
91.4
19,662 stars · MPL-2.0
B
88.6
37,546 stars · license n/a
activitywatch versus langfuse 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; langfuse is written mainly in TypeScript. The composite score is 91.4 for activitywatch and 88.6 for langfuse.
langfuse has 37,546 GitHub stars to activitywatch's 19,662, a gap of 17,884 (1.91×). Forks are 1,078 for activitywatch and 4,243 for langfuse. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 84 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and langfuse was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 1,173 for langfuse (0.031 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. langfuse is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 78 for activitywatch and 30 for langfuse. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and langfuse (37,546 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, langfuse is unpriced in this catalog.
The lead is split. activitywatch is furthest ahead on license flexibility (78 to 30), while langfuse is furthest ahead on fork community (100 to 84). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 91.4 against langfuse at 88.6, a 2.8 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 | langfuse |
|---|---|---|
| GitHub stars | 19,662 | 37,546 |
| Forks | 1,078 | 4,243 |
| Open issues | 132 | 1,173 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 84 | 100 |
| Issue health | 84 | 70 |
| License | 78 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 91.4 | 88.6 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
🪢 Open source AI engineering platform: AI Gateway, agent observability, evals, and prompt/skill management, built on OpenTelemetry. One open platform for every AI call and every agent. Self-host or use Langfuse Cloud.
langfuse has more GitHub stars: 37,546 versus 19,662 for activitywatch. The gap is 17,884 stars.
langfuse 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 langfuse 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. langfuse is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
activitywatch scores 91.4 and langfuse scores 88.6. This page calls that a narrow lead for activitywatch.