head to head · open source
frp vs acme-dns
frp has 110,484 GitHub stars, 15,306 forks, 48 open issues and last shipped 5 days ago. acme-dns has 2,874 stars, 307 forks, 192 open issues and last shipped 5 months ago. frp leads on adoption by 3,744% (110,484 vs 2,874 stars). frp is written in Go under Apache-2.0; acme-dns is written in Go under MIT. frp has attracted 14% as many forks as stars, acme-dns 11%. frp was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| frp | acme-dns | |
|---|---|---|
| GitHub stars | ★ 110K | ★ 2.9K |
| License | Apache-2.0 | MIT |
| Written in | Go | Go |
| Last push | 2026-11-05 | 2026-06-08 |
| Forks | ⑂ 15K | ⑂ 307 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick frp if
- You weight community size — 110K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick acme-dns if
- You want the acme-dns feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and acme-dns fits your workflow better
About frp
frp README 中文文档 Sponsors frp is an open source project with its ongoing development made possible entirely by the support of our awesome sponsors. If you'd like to join them, please consider sponsoring frp's development. Gold Sponsors High performance residential and ISP proxies for developers 90M+ residential IPs worldwide. Rotating IPs, sticky sessions, and traffic that never expires. From $0.55/GB. Use RAPID10 for 10% off. Try it for free. The complete IDE crafted for professional Go developers The sovereign cloud that puts you in control An open source, self hosted alternative to public clouds, built for…
About acme-dns
acme dns A simplified DNS server with a RESTful HTTP API to provide a simple way to automate ACME DNS challenges. Why? Many DNS servers do not provide an API to enable automation for the ACME DNS challenges. Those which do, give the keys way too much power. Leaving the keys laying around your random boxes is too often a requirement to have a meaningful process automation. Acme dns provides a simple API exclusively for TXT record updates and should be used with ACME magic "\ acme challenge" subdomain CNAME records. This way, in the unfortunate exposure of API keys, the effects are limited to the subdomain TXT…
read the full acme-dns overview →
More in Infrastructure & Operations
Related comparisons
More Networking & Connectivity projects
Compare either of these against the rest of the Networking & Connectivity field.
Frequently asked questions
Is frp or acme-dns more popular?
frp has 110,484 GitHub stars and acme-dns has 2,874. frp has the larger community by that measure.
Are frp and acme-dns free?
Both are open source. frp is licensed under Apache-2.0 and acme-dns under MIT. Neither carries a licence fee.
What is the difference between frp and acme-dns?
frp is written in Go and acme-dns in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, frp or acme-dns?
Choose frp if you want the larger community (110,484 stars) or its Apache-2.0 licence terms. Choose acme-dns if its feature set, stack or MIT licence fits better. Both are self-hostable.