head to head · open source

AdGuardHome vs proxy.py

AdGuardHome has 38,471 GitHub stars, 2,613 forks, 1,253 open issues and last shipped 2 days ago. proxy.py has 3,559 stars, 625 forks, 103 open issues and last shipped 13 days ago. AdGuardHome leads on adoption by 981% (38,471 vs 3,559 stars). AdGuardHome is written in TypeScript under GPL-3.0; proxy.py is written in Python under BSD-3-Clause. AdGuardHome has attracted 7% as many forks as stars, proxy.py 18%. 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-over-https), 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.

AdGuardHome ★ 38K proxy.py ★ 3.6K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

AdGuardHome proxy.py
GitHub stars ★ 38K ★ 3.6K
License GPL-3.0 BSD-3-Clause
Written in TypeScript Python
Last push 2026-11-13 2026-11-02
Forks ⑂ 2.6K ⑂ 625
Self-hosting Yes Yes
Data ownership Your server Your server

pick AdGuardHome if

  • You weight community size — 38K 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

full AdGuardHome profile →

pick proxy.py if

  • You want the proxy.py feature set and don't need the biggest community
  • You prefer the BSD-3-Clause license terms
  • Your stack matches Python
  • You evaluated both and proxy.py fits your workflow better

full proxy.py profile →

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 proxy.py

[//]: (DO NOT REMOVE docs badges START) Table of Contents Features Install Using PIP Stable version Development version Using Docker Stable version from Docker Hub Development Version from GHCR Build container locally Using HomeBrew Stable version Development version Start proxy.py From command line when installed using PIP Run it Understanding logs Enable DEBUG logging From command line using repo source Docker Image Customize Startup Flags Plugin Examples HTTP Proxy Plugins ShortLink Plugin Modify Post Data Plugin Mock Api Plugin Redirect To Custom Server Plugin Filter By Upstream Host Plugin Cache Responses…

read the full proxy.py 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 proxy.py more popular?

AdGuardHome has 38,471 GitHub stars and proxy.py has 3,559. AdGuardHome has the larger community by that measure.

Are AdGuardHome and proxy.py free?

Both are open source. AdGuardHome is licensed under GPL-3.0 and proxy.py under BSD-3-Clause. Neither carries a licence fee.

What is the difference between AdGuardHome and proxy.py?

AdGuardHome is written in TypeScript and proxy.py in Python. 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 proxy.py?

Choose AdGuardHome if you want the larger community (38,471 stars) or its GPL-3.0 licence terms. Choose proxy.py if its feature set, stack or BSD-3-Clause licence fits better. Both are self-hostable.