head to head · open source
AdGuardHome vs dns-proxy-server
AdGuardHome has 38,564 GitHub stars, 2,617 forks, 1,253 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. AdGuardHome leads on adoption by 4,416% (38,564 vs 854 stars). AdGuardHome is written in TypeScript under GPL-3.0; dns-proxy-server is written in Java under Apache-2.0. AdGuardHome has attracted 7% as many forks as stars, dns-proxy-server 10%. AdGuardHome was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (dns), so they are genuine substitutes rather than adjacent tools.
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
| AdGuardHome | dns-proxy-server | |
|---|---|---|
| GitHub stars | ★ 39K | ★ 854 |
| License | GPL-3.0 | Apache-2.0 |
| Written in | TypeScript | Java |
| Last push | 2026-11-18 | 2026-04-29 |
| Forks | ⑂ 2.6K | ⑂ 82 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick AdGuardHome if
- You weight community size — 39K stars and counting
- You want the GPL-3.0 license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
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
About AdGuardHome
Privacy protection center for you and your devices Free and open source, powerful network wide ads & trackers blocking DNS server. AdGuard.com Wiki Reddit Twitter Telegram AdGuard Home is a network wide software for blocking ads and tracking. After you set it up, it'll cover ALL your home devices, and you don't need any client side software for that. It operates as a DNS server that re routes tracking domains to a “black hole”, thus preventing your devices from connecting to those servers. It's based on software we use for our public [AdGuard DNS] servers, and both share a lot of code. [AdGuard DNS]: Getting…
read the full AdGuardHome 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 AdGuardHome or dns-proxy-server more popular?
AdGuardHome has 38,564 GitHub stars and dns-proxy-server has 854. AdGuardHome has the larger community by that measure.
Are AdGuardHome and dns-proxy-server free?
Both are open source. AdGuardHome is licensed under GPL-3.0 and dns-proxy-server under Apache-2.0. Neither carries a licence fee.
What is the difference between AdGuardHome and dns-proxy-server?
AdGuardHome is written in TypeScript 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, AdGuardHome or dns-proxy-server?
Choose AdGuardHome if you want the larger community (38,564 stars) or its GPL-3.0 licence terms. Choose dns-proxy-server if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.