# sdnext vs Signal TLS Proxy

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

| | sdnext | Signal TLS Proxy |
|---|---|---|
| Score | 71/100 ✓ | 49/100 |
| Rank in category | #3 of 11 in Image Generation | #16 of 25 in Proxy |
| GitHub stars | 7 362 ✓ | 1 284 |
| Stars, last 30 days | +16 ✓ | +0 |
| Stable releases, 12 months | 0 | 0 |
| Latest release | — | — |
| Setup | Moderate | Easy ✓ |
| Official Docker image | Yes ✓ | No |
| License | Apache-2.0 | MIT |
| Main language | Python | Shell |

## Which one should you pick?

sdnext scores 71/100 against 49/100 for Signal TLS Proxy, so it is the safer default.

If you want the quickest setup, Signal TLS Proxy is easier to run; sdnext needs more configuration.

sdnext is growing faster right now (+16 stars in 30 days).

## Details

- [sdnext](https://selfhost.directory/project/sdnext) (markdown: https://selfhost.directory/project/sdnext.md)
- [Signal TLS Proxy](https://selfhost.directory/project/signal-tls-proxy) (markdown: https://selfhost.directory/project/signal-tls-proxy.md)

---
Source: https://selfhost.directory/compare/sdnext-vs-signal-tls-proxy