Signal TLS Proxyvssupabase
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Signal TLS Proxy | supabase | |
|---|---|---|
| Score | 49/100 | 92/100 |
| Rank in category | #16 of 25 in Proxy | #1 of 40 in Database Management |
| GitHub stars | 1 284 | 114 288 |
| Stars, last 30 days | +0 | +3 540 |
| Stable releases, 12 months | 0 | 8 |
| Latest release | — | v1.26.08 · 7 Aug 2026 |
| Setup | Easy | Advanced |
| Official Docker image | No | Yes |
| License | MIT | Apache-2.0 |
| Main language | Shell | Typescript |
Which one should you pick?
supabase scores 92/100 against 49/100 for Signal TLS Proxy, so it is the safer default.
supabase ships more often: 8 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; supabase needs more configuration.
supabase is growing faster right now (+3 540 stars in 30 days).
Signal TLS Proxy details →supabase details →
Swap a project
Keep Signal TLS Proxy, compare it with
Keep supabase, compare it with