# imgproxy vs vLLM

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

| | imgproxy | vLLM |
|---|---|---|
| Score | 72/100 | 91/100 ✓ |
| Rank in category | #2 of 13 in Image Processing | #3 of 25 in LLM Inference |
| GitHub stars | 11 161 | 95 789 ✓ |
| Stars, last 30 days | +69 | +3 237 ✓ |
| Stable releases, 12 months | 23 ✓ | 14 |
| Latest release | v4.0.20 · 26 Oct 2026 ✓ | v0.32.0 · 17 Oct 2026 |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | Apache-2.0 |
| Main language | Go | Python |

## Which one should you pick?

vLLM scores 91/100 against 72/100 for imgproxy, so it is the safer default.

imgproxy ships more often: 23 stable releases in the past year, against 14 for vLLM.

If you want the quickest setup, imgproxy is easier to run; vLLM needs more configuration.

vLLM is growing faster right now (+3 237 stars in 30 days).

## Details

- [imgproxy](https://selfhost.directory/project/imgproxy) (markdown: https://selfhost.directory/project/imgproxy.md)
- [vLLM](https://selfhost.directory/project/vllm) (markdown: https://selfhost.directory/project/vllm.md)

---
Source: https://selfhost.directory/compare/imgproxy-vs-vllm