acme.sh vs Blocky
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
Blocky
Fast DNS proxy and ad-blocker for local networks
| Feature | acme.sh | Blocky |
|---|---|---|
| Category | Reverse Proxy & Gateways | Reverse Proxy & Gateways |
| License | GPL-3.0 | Apache-2.0 |
| Language | Shell | Go |
| Setup difficulty | Easy | Easy |
| Min. RAM | 32 MB | 128 MB |
| Deployment | binary, source | docker, binary |
| GitHub stars | ★ 47,426 | ★ 6,844 |
| First released | 2016 | 2019 |
| Replaces | Certbot | Pi-hole, AdGuard Home |
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 Blocky if…
- Released under the Apache-2.0 license
- Easy to set up — beginner-friendly
- First-class Docker support for quick deployment
- Mature project with 6.8k GitHub stars
Frequently asked questions
Is acme.sh or Blocky better?
Neither is universally better. acme.sh has the larger community; both share a easy setup difficulty, so the decision comes down to features and licensing.
Are acme.sh and Blocky free and open-source?
Yes. acme.sh is licensed under GPL-3.0 and Blocky under Apache-2.0. Both can be self-hosted at no software cost.
Can I run acme.sh and Blocky with Docker?
acme.sh: check the project docs for container support. Blocky: yes.