head to head · open source

caddy vs dns-proxy-server

caddy has 79,242 GitHub stars, 5,283 forks, 286 open issues and last shipped 2 days ago. dns-proxy-server has 854 stars, 82 forks, 8 open issues and last shipped 7 months ago. caddy leads on adoption by 9,179% (79,242 vs 854 stars). caddy is written in Go under Apache-2.0; dns-proxy-server is written in Java under Apache-2.0. caddy has attracted 7% as many forks as stars, dns-proxy-server 10%. caddy 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.

caddy ★ 79K dns-proxy-server ★ 854 category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

caddy dns-proxy-server
GitHub stars ★ 79K ★ 854
License Apache-2.0 Apache-2.0
Written in Go Java
Last push 2026-11-18 2026-04-29
Forks ⑂ 5.3K ⑂ 82
Self-hosting Yes Yes
Data ownership Your server Your server

pick caddy if

  • You weight community size — 79K 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 caddy profile →

pick dns-proxy-server if

  • You want the dns-proxy-server feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches Java
  • You evaluated both and dns-proxy-server fits your workflow better

full dns-proxy-server profile →

About caddy

a project Every site on HTTPS Caddy is an extensible server platform that uses TLS by default. Releases · Documentation · Get Help Powered by Special thanks to: Warp, built for coding with multiple AI agents Available for MacOS, Linux, & Windows Menu Features Install Build from source For development With version information and/or plugins Quick start Overview Full documentation Getting help About Features Easy configuration with the Caddyfile Powerful configuration with its native JSON config Dynamic configuration with the JSON API Config adapters if you don't like JSON Automatic HTTPS by default ZeroSSL and…

read the full caddy overview →

About dns-proxy-server

[![help me to keep DPS up to date][7]][6] Main features DPS is a lightweight end user (Developers, Server Administrators) DNS server tool which make it easy to develop in systems where one hostname can solve to different IPs based on the configured environment. Solve hostnames to [docker containers][11] Solve hostnames from local configuration database Recursive solving from a list of configured remote DNS servers Solve hostnames using wildcards/regex Graphic interface to Create/List/Update/Delete A/AAAA/CNAME records Solve host machine IP using host.docker hostname Checkout the [full list of features][4] with…

read the full dns-proxy-server 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 caddy or dns-proxy-server more popular?

caddy has 79,242 GitHub stars and dns-proxy-server has 854. caddy has the larger community by that measure.

Are caddy and dns-proxy-server free?

Both are open source. caddy is licensed under Apache-2.0 and dns-proxy-server under Apache-2.0. Neither carries a licence fee.

What is the difference between caddy and dns-proxy-server?

caddy is written in Go and dns-proxy-server in Java. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, caddy or dns-proxy-server?

Choose caddy if you want the larger community (79,242 stars) or its Apache-2.0 licence terms. Choose dns-proxy-server if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.