# openseo vs Web Rendering Proxy (WRP)

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

| | openseo | Web Rendering Proxy (WRP) |
|---|---|---|
| Score | 72/100 ✓ | 53/100 |
| Rank in category | #2 of 12 in Marketing Automation | #11 of 25 in Proxy |
| GitHub stars | 25 524 ✓ | 1 306 |
| Stars, last 30 days | +4 937 | — |
| Stable releases, 12 months | 38 ✓ | 4 |
| Latest release | v0.1.19 · 26 Oct 2026 ✓ | 4.10.3 · 23 Apr 2026 |
| Setup | Moderate | Easy ✓ |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Typescript | Go |

## Which one should you pick?

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

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

openseo is growing faster right now (+4 937 stars in 30 days).

## Details

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

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