# llama.cpp vs Signal TLS Proxy

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

| | llama.cpp | Signal TLS Proxy |
|---|---|---|
| Score | 93/100 ✓ | 49/100 |
| Rank in category | #2 of 25 in LLM Inference | #16 of 25 in Proxy |
| GitHub stars | 132 674 ✓ | 1 284 |
| Stars, last 30 days | +3 317 | — |
| Stable releases, 12 months | 1461 ✓ | 0 |
| Latest release | b11972 · 28 Oct 2026 | — |
| Setup | Moderate | Easy ✓ |
| Official Docker image | Yes ✓ | No |
| License | MIT | MIT |
| Main language | C++ | Shell |

## Which one should you pick?

llama.cpp scores 93/100 against 49/100 for Signal TLS Proxy, so it is the safer default.

llama.cpp ships more often: 1461 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; llama.cpp needs more configuration.

llama.cpp is growing faster right now (+3 317 stars in 30 days).

## Details

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