retroassemblyvsWeb Rendering Proxy (WRP)
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| retroassembly | Web Rendering Proxy (WRP) | |
|---|---|---|
| Score | 56/100 | 53/100 |
| Rank in category | #5 of 5 in Emulation | #11 of 25 in Proxy |
| GitHub stars | 1 153 | 1 306 |
| Stars, last 30 days | +71 | — |
| Stable releases, 12 months | 3 | 4 |
| Latest release | v7.260719.1051 · 19 Jul 2026 | 4.10.3 · 23 Apr 2026 |
| Setup | Easy | Easy |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Typescript | Go |
Which one should you pick?
retroassembly scores 56/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 retroassembly.
retroassembly is growing faster right now (+71 stars in 30 days).
retroassembly details →Web Rendering Proxy (WRP) details →