Self-Hosted GatewayvsShadowsocks
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Self-Hosted Gateway | Shadowsocks | |
|---|---|---|
| Score | 57/100 | 69/100 |
| Rank in category | #10 of 31 in Networking | #6 of 26 in Proxy |
| GitHub stars | 1 742 | 16 191 |
| Stars, last 30 days | +2 | +6 |
| Stable releases, 12 months | 0 | 1 |
| Latest release | — | v3.3.6 · 9 Feb 2026 |
| Setup | Advanced | Moderate |
| Official Docker image | No | Yes |
| License | AGPL-3.0 | GPL-3.0 |
| Main language | Shell | C++ |
Which one should you pick?
Shadowsocks scores 69/100 against 57/100 for Self-Hosted Gateway, so it is the safer default.
Shadowsocks ships more often: 1 stable releases in the past year, against 0 for Self-Hosted Gateway.
If you want the quickest setup, Shadowsocks is easier to run; Self-Hosted Gateway needs more configuration.
Shadowsocks is growing faster right now (+6 stars in 30 days).
Key differences
- License: Self-Hosted Gateway is AGPL-3.0, Shadowsocks is GPL-3.0.
- Language: Self-Hosted Gateway is written mainly in Shell, Shadowsocks in C++.
- Only Shadowsocks ships an official Docker image.
- Features only Self-Hosted Gateway lists: Automatic TLS certificates, Basic Authentication, Multiple services per gateway, Mutual TLS authentication and 4 more.
- Features only Shadowsocks lists: Access control lists, Asynchronous DNS and multiple servers, IPv6 Support, Local port forwarding and 10 more.
Self-Hosted Gateway details →Shadowsocks details →