A · leads
activitywatch
93.6
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 2.0 · narrow
A · leads
93.6
19,662 stars · MPL-2.0
B
91.6
13,520 stars · Apache-2.0
activitywatch versus trino 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; trino is written mainly in Java. The composite score is 93.6 for activitywatch and 91.6 for trino.
activitywatch has 19,662 GitHub stars to trino's 13,520, a gap of 6,142 (1.45×). Forks are 1,078 for activitywatch and 3,880 for trino. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 84 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and trino was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 2,758 for trino (0.204 per star). Issue-health scores are 84 and 34; 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. trino is listed as Apache-2.0, 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 trino. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and trino (13,520 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, trino is open source.
The lead is split. activitywatch is furthest ahead on issue health (84 to 34), while trino is furthest ahead on license flexibility (96 to 78). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 93.6 against trino at 91.6, a 2.0 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 | trino |
|---|---|---|
| GitHub stars | 19,662 | 13,520 |
| Forks | 1,078 | 3,880 |
| Open issues | 132 | 2,758 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 84 | 100 |
| Issue health | 84 | 34 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.6 | 91.6 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)
activitywatch has more GitHub stars: 19,662 versus 13,520 for trino. The gap is 6,142 stars.
trino 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 trino 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. trino is listed as Apache-2.0, 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 93.6 and trino scores 91.6. This page calls that a narrow lead for activitywatch.