# Encore vs Web Rendering Proxy (WRP)

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

| | Encore | Web Rendering Proxy (WRP) |
|---|---|---|
| Score | 72/100 ✓ | 53/100 |
| Rank in category | #4 of 14 in Platform as a Service | #11 of 25 in Proxy |
| GitHub stars | 12 652 ✓ | 1 306 |
| Stars, last 30 days | +167 | — |
| Stable releases, 12 months | 9 ✓ | 4 |
| Latest release | v1.58.8 · 20 Oct 2026 ✓ | 4.10.3 · 23 Apr 2026 |
| Setup | Moderate | Easy ✓ |
| Official Docker image | No | Yes ✓ |
| License | MPL-2.0 | Apache-2.0 |
| Main language | Go | Go |

## Which one should you pick?

Encore scores 72/100 against 53/100 for Web Rendering Proxy (WRP), so it is the safer default.

Encore ships more often: 9 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; Encore needs more configuration.

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

## Details

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

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