JoplinvsWeb Rendering Proxy (WRP)
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Joplin | Web Rendering Proxy (WRP) | |
|---|---|---|
| Score | 83/100 | 53/100 |
| Rank in category | #2 of 81 in Notes & Editors | #11 of 25 in Proxy |
| GitHub stars | 56 916 | 1 306 |
| Stars, last 30 days | +440 | — |
| Stable releases, 12 months | 18 | 4 |
| Latest release | v3.7.22 · 28 Oct 2026 | 4.10.3 · 23 Apr 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | Other | Apache-2.0 |
| Main language | Typescript | Go |
Which one should you pick?
Joplin scores 83/100 against 53/100 for Web Rendering Proxy (WRP), so it is the safer default.
Joplin ships more often: 18 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; Joplin needs more configuration.
Joplin is growing faster right now (+440 stars in 30 days).
Joplin details →Web Rendering Proxy (WRP) details →
Swap a project
Keep Joplin, compare it with
Keep Web Rendering Proxy (WRP), compare it with