head to head · open source
AdGuardHome vs cloudflared
AdGuardHome has 38,159 GitHub stars, 2,596 forks, 1,253 open issues and last shipped 3 days ago. cloudflared has 16,443 stars, 1,518 forks, 545 open issues and last shipped 2 days ago. AdGuardHome leads on adoption by 132% (38,159 vs 16,443 stars). AdGuardHome is written in TypeScript under GPL-3.0; cloudflared is written in Go under Apache-2.0. AdGuardHome has attracted 7% as many forks as stars, cloudflared 9%. cloudflared 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 | cloudflared | |
|---|---|---|
| GitHub stars | ★ 38K | ★ 16K |
| License | GPL-3.0 | Apache-2.0 |
| Written in | TypeScript | Go |
| Last push | 2026-11-03 | 2026-11-04 |
| Forks | ⑂ 2.6K | ⑂ 1.5K |
| 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
pick cloudflared if
- You want the cloudflared feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Go
- You evaluated both and cloudflared 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 cloudflared
Cloudflare Tunnel client Contains the command line client for Cloudflare Tunnel, a tunneling daemon that proxies traffic from the Cloudflare network to your origins. This daemon sits between Cloudflare network and your origin (e.g. a webserver). Cloudflare attracts client requests and sends them to you via this daemon, without requiring you to poke holes on your firewall your origin can remain as closed as possible. Extensive documentation can be found in the Cloudflare Tunnel section of the Cloudflare Docs. All usages related with proxying to your origins are available under cloudflared tunnel help . You can…
read the full cloudflared 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 cloudflared more popular?
AdGuardHome has 38,159 GitHub stars and cloudflared has 16,443. AdGuardHome has the larger community by that measure.
Are AdGuardHome and cloudflared free?
Both are open source. AdGuardHome is licensed under GPL-3.0 and cloudflared under Apache-2.0. Neither carries a licence fee.
What is the difference between AdGuardHome and cloudflared?
AdGuardHome is written in TypeScript and cloudflared 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 cloudflared?
Choose AdGuardHome if you want the larger community (38,159 stars) or its GPL-3.0 licence terms. Choose cloudflared if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.