e2bvsWeb Rendering Proxy (WRP)
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| e2b | Web Rendering Proxy (WRP) | |
|---|---|---|
| Score | 76/100 | 53/100 |
| Rank in category | #14 of 209 in AI Agents | #11 of 25 in Proxy |
| GitHub stars | 14 596 | 1 306 |
| Stars, last 30 days | +658 | — |
| Stable releases, 12 months | 76 | 4 |
| Latest release | @e2b/code-interpreter-python@2.11.6 · 28 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 | Python | Go |
Which one should you pick?
e2b scores 76/100 against 53/100 for Web Rendering Proxy (WRP), so it is the safer default.
e2b ships more often: 76 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; e2b needs more configuration.
e2b is growing faster right now (+658 stars in 30 days).
e2b details →Web Rendering Proxy (WRP) details →