A · leads
activitywatch
94.4
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 2.3 · narrow
A · leads
94.4
19,662 stars · MPL-2.0
B
92.1
9,083 stars · Apache-2.0
activitywatch versus delta 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; delta is written mainly in Scala. The composite score is 94.4 for activitywatch and 92.1 for delta.
activitywatch has 19,662 GitHub stars to delta's 9,083, a gap of 10,579 (2.16×). Forks are 1,078 for activitywatch and 2,224 for delta. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 91 versus 100.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and delta was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 1,061 for delta (0.117 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. delta 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 delta. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and delta (9,083 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, delta is open source.
The lead is split. activitywatch is furthest ahead on issue health (84 to 52), while delta is furthest ahead on license flexibility (96 to 78). Choose the dimension a rollout cannot compromise on.
activitywatch finishes ahead at 94.4 against delta at 92.1, a 2.3 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 | delta |
|---|---|---|
| GitHub stars | 19,662 | 9,083 |
| Forks | 1,078 | 2,224 |
| Open issues | 132 | 1,061 |
| Adoption | 100 | 92 |
| Activity | 100 | 100 |
| Community | 91 | 100 |
| Issue health | 84 | 52 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.4 | 92.1 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
An open-source storage framework that enables building a Lakehouse architecture with compute engines including Spark, PrestoDB, Flink, Trino, and Hive and APIs
activitywatch has more GitHub stars: 19,662 versus 9,083 for delta. The gap is 10,579 stars.
delta 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 delta 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. delta 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 94.4 and delta scores 92.1. This page calls that a narrow lead for activitywatch.