# MediaCMS vs Web Rendering Proxy (WRP)

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

| | MediaCMS | Web Rendering Proxy (WRP) |
|---|---|---|
| Score | 67/100 ✓ | 53/100 |
| Rank in category | #2 of 3 in Video Hosting | #11 of 25 in Proxy |
| GitHub stars | 5 171 ✓ | 1 306 |
| Stars, last 30 days | +46 ✓ | +0 |
| Stable releases, 12 months | 26 ✓ | 4 |
| Latest release | v9.4.0 · 26 Oct 2026 ✓ | 4.10.3 · 23 Apr 2026 |
| Setup | Moderate | Easy ✓ |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | Apache-2.0 |
| Main language | Python | Go |

## Which one should you pick?

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

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

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

## Details

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

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