# SeaweedFS vs Signal TLS Proxy

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

| | SeaweedFS | Signal TLS Proxy |
|---|---|---|
| Score | 81/100 ✓ | 49/100 |
| Rank in category | #1 of 11 in Cloud Storage | #16 of 25 in Proxy |
| GitHub stars | 35 794 ✓ | 1 284 |
| Stars, last 30 days | +869 | — |
| Stable releases, 12 months | 28 ✓ | 0 |
| Latest release | 4.51 · 25 Oct 2026 | — |
| Setup | Moderate | Easy ✓ |
| Official Docker image | Yes ✓ | No |
| License | Apache-2.0 | MIT |
| Main language | Go | Shell |

## Which one should you pick?

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

SeaweedFS ships more often: 28 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; SeaweedFS needs more configuration.

SeaweedFS is growing faster right now (+869 stars in 30 days).

## Details

- [SeaweedFS](https://selfhost.directory/project/seaweedfs) (markdown: https://selfhost.directory/project/seaweedfs.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/seaweedfs-vs-signal-tls-proxy