AdGuard HomevsWeb Rendering Proxy (WRP)
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| AdGuard Home | Web Rendering Proxy (WRP) | |
|---|---|---|
| Score | 84/100 | 53/100 |
| Rank in category | #2 of 41 in DNS | #11 of 25 in Proxy |
| GitHub stars | 37 810 | 1 306 |
| Stars, last 30 days | +766 | — |
| Stable releases, 12 months | 16 | 4 |
| Latest release | v1.0.0-b.1 · 30 Sept 2026 | 4.10.3 · 23 Apr 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | GPL-3.0 | Apache-2.0 |
| Main language | Typescript | Go |
Which one should you pick?
AdGuard Home scores 84/100 against 53/100 for Web Rendering Proxy (WRP), so it is the safer default.
AdGuard Home ships more often: 16 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; AdGuard Home needs more configuration.
AdGuard Home is growing faster right now (+766 stars in 30 days).
AdGuard Home details →Web Rendering Proxy (WRP) details →
Swap a project
Keep AdGuard Home, compare it with
Keep Web Rendering Proxy (WRP), compare it with