budibasevsSignal TLS Proxy
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| budibase | Signal TLS Proxy | |
|---|---|---|
| Score | 74/100 | 49/100 |
| Rank in category | #2 of 17 in Low Code | #16 of 25 in Proxy |
| GitHub stars | 28 365 | 1 284 |
| Stars, last 30 days | +65 | — |
| Stable releases, 12 months | 75 | 0 |
| Latest release | v3.51.0-cloud.7 · 21 Oct 2026 | — |
| Setup | Moderate | Easy |
| Official Docker image | Yes | No |
| License | Other | MIT |
| Main language | Typescript | Shell |
Which one should you pick?
budibase scores 74/100 against 49/100 for Signal TLS Proxy, so it is the safer default.
budibase ships more often: 75 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; budibase needs more configuration.
budibase is growing faster right now (+65 stars in 30 days).
budibase details →Signal TLS Proxy details →