ChronoFramevsWeb Rendering Proxy (WRP)
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| ChronoFrame | Web Rendering Proxy (WRP) | |
|---|---|---|
| Score | 63/100 | 53/100 |
| Rank in category | #8 of 41 in Photo Management | #11 of 25 in Proxy |
| GitHub stars | 1 964 | 1 306 |
| Stars, last 30 days | +32 | +0 |
| Stable releases, 12 months | 3 | 4 |
| Latest release | v1.0.2 · 21 Oct 2026 | 4.10.3 · 23 Apr 2026 |
| Setup | Easy | Easy |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | Apache-2.0 |
| Main language | Typescript | Go |
Which one should you pick?
ChronoFrame scores 63/100 against 53/100 for Web Rendering Proxy (WRP), so it is the safer default.
Web Rendering Proxy (WRP) ships more often: 4 stable releases in the past year, against 3 for ChronoFrame.
ChronoFrame is growing faster right now (+32 stars in 30 days).
ChronoFrame details →Web Rendering Proxy (WRP) details →
Swap a project
Keep ChronoFrame, compare it with
Keep Web Rendering Proxy (WRP), compare it with