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