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