acme.sh vs imgproxy
A side-by-side comparison of two self-hosted reverse proxy & gateways options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
acme.sh
Pure shell ACME client for TLS certificates
VS
imgproxy
Fast and secure standalone server for resizing and converting remote
| Feature | acme.sh | imgproxy |
|---|---|---|
| Category | Reverse Proxy & Gateways | Reverse Proxy & Gateways |
| License | GPL-3.0 | MIT |
| Language | Shell | Go |
| Setup difficulty | Easy | Medium |
| Min. RAM | 32 MB | 512 MB |
| Deployment | binary, source | docker, kubernetes |
| GitHub stars | ★ 47,426 | ★ 10,997 |
| First released | 2016 | 2026 |
| Replaces | Certbot | — |
Why pick each one
Choose acme.sh if…
- Released under the GPL-3.0 license
- Easy to set up — beginner-friendly
- Mature project with 47.4k GitHub stars
- Written in Shell
Choose imgproxy if…
- Released under the MIT license
- First-class Docker support for quick deployment
- Kubernetes-ready with Helm charts available
- Mature project with 11k GitHub stars
Frequently asked questions
Is acme.sh or imgproxy better?
acme.sh is the stronger all-round pick: it has both the larger community and the simpler easy setup. Consider imgproxy if its specific feature set fits your needs better.
Are acme.sh and imgproxy free and open-source?
Yes. acme.sh is licensed under GPL-3.0 and imgproxy under MIT. Both can be self-hosted at no software cost.
Can I run acme.sh and imgproxy with Docker?
acme.sh: check the project docs for container support. imgproxy: yes.