# nps vs Web Rendering Proxy (WRP)

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | nps | Web Rendering Proxy (WRP) |
|---|---|---|
| Score | 74/100 ✓ | 53/100 |
| Rank in category | #2 of 31 in Networking | #11 of 25 in Proxy |
| GitHub stars | 34 263 ✓ | 1 306 |
| Stars, last 30 days | +30 | — |
| Stable releases, 12 months | 0 | 4 ✓ |
| Latest release | — | 4.10.3 · 23 Apr 2026 |
| Setup | Moderate | Easy ✓ |
| Official Docker image | No | Yes ✓ |
| License | GPL-3.0 | Apache-2.0 |
| Main language | Go | Go |

## Which one should you pick?

nps scores 74/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 0 for nps.

If you want the quickest setup, Web Rendering Proxy (WRP) is easier to run; nps needs more configuration.

nps is growing faster right now (+30 stars in 30 days).

## Details

- [nps](https://selfhost.directory/project/nps) (markdown: https://selfhost.directory/project/nps.md)
- [Web Rendering Proxy (WRP)](https://selfhost.directory/project/wrp) (markdown: https://selfhost.directory/project/wrp.md)

---
Source: https://selfhost.directory/compare/nps-vs-wrp