head to head · open source
AdGuardHome vs tsdproxy
AdGuardHome has 38,664 GitHub stars, 2,625 forks, 1,253 open issues and last shipped yesterday. tsdproxy has 1,735 stars, 84 forks, 29 open issues and last shipped 8 days ago. AdGuardHome leads on adoption by 2,128% (38,664 vs 1,735 stars). AdGuardHome is written in TypeScript under GPL-3.0; tsdproxy is written in Go under MIT. AdGuardHome has attracted 7% as many forks as stars, tsdproxy 5%. AdGuardHome 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
| AdGuardHome | tsdproxy | |
|---|---|---|
| GitHub stars | ★ 39K | ★ 1.7K |
| License | GPL-3.0 | MIT |
| Written in | TypeScript | Go |
| Last push | 2026-11-20 | 2026-11-13 |
| Forks | ⑂ 2.6K | ⑂ 84 |
| 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 tsdproxy if
- You want the tsdproxy feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and tsdproxy 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 tsdproxy
TSDProxy Tailscale Docker Proxy The easiest way to expose Docker containers on your Tailscale network. One label. Zero sidecars. Quick Start Get running in under a minute. One compose file, one label. Step 1: Create docker compose.yml Step 2: Start it up TSDProxy creates a default config at /config/tsdproxy.yaml on first run. Open the dashboard at click the proxy card, and authenticate with Tailscale. Your container is now available at .ts.net with automatic HTTPS. For automated (headless) setup, configure an AuthKey or OAuth before adding services. Key Features How It Works Under the hood: 1. Container Scanning…
read the full tsdproxy 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 tsdproxy more popular?
AdGuardHome has 38,664 GitHub stars and tsdproxy has 1,735. AdGuardHome has the larger community by that measure.
Are AdGuardHome and tsdproxy free?
Both are open source. AdGuardHome is licensed under GPL-3.0 and tsdproxy under MIT. Neither carries a licence fee.
What is the difference between AdGuardHome and tsdproxy?
AdGuardHome is written in TypeScript and tsdproxy 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, AdGuardHome or tsdproxy?
Choose AdGuardHome if you want the larger community (38,664 stars) or its GPL-3.0 licence terms. Choose tsdproxy if its feature set, stack or MIT licence fits better. Both are self-hostable.