ActivityWatchvsPostgREST
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| ActivityWatch | PostgREST | |
|---|---|---|
| Score | 80/100 | 79/100 |
| Rank in category | #1 of 11 in Time Tracking | #2 of 13 in API |
| GitHub stars | 19 428 | 27 737 |
| Stars, last 30 days | +452 | +60 |
| Stable releases, 12 months | 13 | 20 |
| Latest release | v0.14.1 · 10 Oct 2026 | v16.5 · 18 Oct 2026 |
| Setup | Moderate | Easy |
| Official Docker image | No | Yes |
| License | MPL-2.0 | MIT |
| Main language | Python | Haskell |
Which one should you pick?
ActivityWatch scores 80/100 against 79/100 for PostgREST, so it is the safer default.
PostgREST ships more often: 20 stable releases in the past year, against 13 for ActivityWatch.
If you want the quickest setup, PostgREST is easier to run; ActivityWatch needs more configuration.
ActivityWatch is growing faster right now (+452 stars in 30 days).
ActivityWatch details →PostgREST details →
Swap a project
Keep ActivityWatch, compare it with
Keep PostgREST, compare it with