A · leads
activitywatch
95.8
19,662 stars · MPL-2.0
Analytics
activitywatch leads by 8.5 · clear
A · leads
95.8
19,662 stars · MPL-2.0
B
87.3
9,535 stars · AGPL-3.0
activitywatch versus paradedb 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; paradedb is written mainly in Rust. The composite score is 95.8 for activitywatch and 87.3 for paradedb.
activitywatch has 19,662 GitHub stars to paradedb's 9,535, a gap of 10,127 (2.06×). Forks are 1,078 for activitywatch and 515 for paradedb. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 89.
Push history: activitywatch was last pushed on 15 November 2026 (2 days ago), and paradedb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 132 for activitywatch (0.007 per star) and 284 for paradedb (0.030 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. paradedb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 78 for activitywatch and 52 for paradedb. This is a procurement signal, not legal advice.
In Analytics, both activitywatch (19,662 stars) and paradedb (9,535 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, paradedb is open source.
activitywatch is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 26 points (78 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
activitywatch finishes ahead at 95.8 against paradedb at 87.3, a 8.5 point clear 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 | paradedb |
|---|---|---|
| GitHub stars | 19,662 | 9,535 |
| Forks | 1,078 | 515 |
| Open issues | 132 | 284 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 84 | 70 |
| License | 78 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 95.8 | 87.3 |
The best free and open-source automated time tracker. Cross-platform, extensible, privacy-focused.
One Postgres for your application data, full-text search, vector retrieval, and aggregations. Home of the pg_search extension.
activitywatch has more GitHub stars: 19,662 versus 9,535 for paradedb. The gap is 10,127 stars.
paradedb 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 paradedb 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. paradedb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
activitywatch scores 95.8 and paradedb scores 87.3. This page calls that a clear lead for activitywatch.