Reactive ResumevsSignal TLS Proxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Reactive Resume | Signal TLS Proxy | |
|---|---|---|
| Score | 87/100 | 49/100 |
| Rank in category | #1 of 46 in Document Management | #16 of 25 in Proxy |
| GitHub stars | 45 003 | 1 284 |
| Stars, last 30 days | +1 630 | — |
| Stable releases, 12 months | 34 | 0 |
| Latest release | v6.0.7 · 26 Oct 2026 | — |
| Setup | Moderate | Easy |
| Official Docker image | Yes | No |
| License | MIT | MIT |
| Main language | Typescript | Shell |
Which one should you pick?
Reactive Resume scores 87/100 against 49/100 for Signal TLS Proxy, so it is the safer default.
Reactive Resume ships more often: 34 stable releases in the past year, against 0 for Signal TLS Proxy.
If you want the quickest setup, Signal TLS Proxy is easier to run; Reactive Resume needs more configuration.
Reactive Resume is growing faster right now (+1 630 stars in 30 days).
Reactive Resume details →Signal TLS Proxy details →
Swap a project
Keep Reactive Resume, compare it with
Keep Signal TLS Proxy, compare it with