head to head · open source

frp vs acme-dns

frp has 109,614 GitHub stars, 15,220 forks, 48 open issues and last shipped 10 days ago. acme-dns has 2,832 stars, 304 forks, 192 open issues and last shipped 4 months ago. frp leads on adoption by 3,771% (109,614 vs 2,832 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.

frp ★ 110K acme-dns ★ 2.8K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

frp acme-dns
GitHub stars ★ 110K ★ 2.8K
License Apache-2.0 MIT
Written in Go Go
Last push 2026-09-15 2026-06-08
Forks ⑂ 15K ⑂ 304
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

full frp profile →

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

full acme-dns profile →

About frp

frp is a fast reverse proxy written in Go that exposes a local server behind a NAT or firewall to the internet, built for operators and developers who need inbound access to machines they cannot port forward.

read the full frp overview →

About acme-dns

acme dns is a limited, self hosted DNS server written in Go that exposes a RESTful HTTP API for updating TXT records, letting operators automate ACME DNS 01 challenges without handing broad DNS control to their automation.

read the full acme-dns overview →

More in Infrastructure & Operations

kubernetes ★ 128K Immich ★ 115K Uptime Kuma ★ 92K worldmonitor ★ 87K mall ★ 85K NetData ★ 81K

Related comparisons

frp vs caddy frp vs traefik frp vs adguardhome frp vs nginx frp vs algo frp vs nginx-proxy frp vs plakar frp vs pluton caddy vs traefik immich vs openvpn n8n vs huginn uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana uptime-kuma vs prometheus netdata vs grafana n8n vs kestra langchain vs haystack kubernetes vs rancher ansible vs compose ansible vs conductor ansible vs xxl-job

More Networking & Connectivity projects

Compare either of these against the rest of the Networking & Connectivity field.

frp vs caddy frp vs traefik frp vs AdGuardHome frp vs nginx frp vs algo frp vs nginx-proxy frp vs goproxy frp vs openvpn-install frp vs cloudflared frp vs amnezia-client frp vs OpenVPN frp vs coredns

Frequently asked questions

Is frp or acme-dns more popular?

frp has 109,614 GitHub stars and acme-dns has 2,832. 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 (109,614 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.