ChronoFramevsWakupator
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| ChronoFrame | Wakupator | |
|---|---|---|
| Score | 63/100 | 43/100 |
| Rank in category | #8 of 41 in Photo Management | #11 of 22 in Home Server |
| GitHub stars | 1 964 | 184 |
| Stars, last 30 days | +32 | — |
| Stable releases, 12 months | 3 | 1 |
| Latest release | v1.0.2 · 21 Oct 2026 | v1.2.0 · 6 Feb 2026 |
| Setup | Easy | Advanced |
| Official Docker image | Yes | No |
| License | AGPL-3.0 | MIT |
| Main language | Typescript | C |
Which one should you pick?
ChronoFrame scores 63/100 against 43/100 for Wakupator, so it is the safer default.
ChronoFrame ships more often: 3 stable releases in the past year, against 1 for Wakupator.
If you want the quickest setup, ChronoFrame is easier to run; Wakupator needs more configuration.
ChronoFrame is growing faster right now (+32 stars in 30 days).
ChronoFrame details →Wakupator details →
Swap a project
Keep ChronoFrame, compare it with
Keep Wakupator, compare it with