temporalvsWeb Rendering Proxy (WRP)
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| temporal | Web Rendering Proxy (WRP) | |
|---|---|---|
| Score | 82/100 | 53/100 |
| Rank in category | #1 of 1 in Workflow | #11 of 25 in Proxy |
| GitHub stars | 24 054 | 1 306 |
| Stars, last 30 days | +776 | +0 |
| Stable releases, 12 months | 11 | 4 |
| Latest release | v1.30.8 · 12 Oct 2026 | 4.10.3 · 23 Apr 2026 |
| Setup | Advanced | Easy |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Go | Go |
Which one should you pick?
temporal scores 82/100 against 53/100 for Web Rendering Proxy (WRP), so it is the safer default.
temporal ships more often: 11 stable releases in the past year, against 4 for Web Rendering Proxy (WRP).
If you want the quickest setup, Web Rendering Proxy (WRP) is easier to run; temporal needs more configuration.
temporal is growing faster right now (+776 stars in 30 days).
temporal details →Web Rendering Proxy (WRP) details →
Swap a project
Keep temporal, compare it with
Keep Web Rendering Proxy (WRP), compare it with