head to head · open source
AdGuardHome vs landscape
AdGuardHome has 38,394 GitHub stars, 2,608 forks, 1,253 open issues and last shipped yesterday. landscape has 1,598 stars, 125 forks, 29 open issues and last shipped yesterday. AdGuardHome leads on adoption by 2,303% (38,394 vs 1,598 stars). AdGuardHome is written in TypeScript under GPL-3.0; landscape is written in Rust under GPL-3.0. AdGuardHome has attracted 7% as many forks as stars, landscape 8%. 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 | landscape | |
|---|---|---|
| GitHub stars | ★ 38K | ★ 1.6K |
| License | GPL-3.0 | GPL-3.0 |
| Written in | TypeScript | Rust |
| Last push | 2026-11-12 | 2026-11-12 |
| Forks | ⑂ 2.6K | ⑂ 125 |
| 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 landscape if
- You want the landscape feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches Rust
- You evaluated both and landscape 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 landscape
Landscape routes traffic by domain—not just IP. Each flow gets its own DNS server. DNS answers populate kernel eBPF maps. Packets are steered at XDP/TC. No userspace datapath. No iptables. Built with Rust / eBPF. 简体中文 English Documentation Screenshot Architecture Landscape separates traffic steering into two planes: DNS plane (userspace). A flow is a policy group that devices join by IP or MAC. Each flow gets its own isolated Hickory DNS server with independent cache, upstream (UDP/DoH/DoT/DoQ), and rules. DNS answers populate per flow eBPF maps in the kernel. Data plane (kernel). XDP and TC hooks read these…
read the full landscape 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 landscape more popular?
AdGuardHome has 38,394 GitHub stars and landscape has 1,598. AdGuardHome has the larger community by that measure.
Are AdGuardHome and landscape free?
Both are open source. AdGuardHome is licensed under GPL-3.0 and landscape under GPL-3.0. Neither carries a licence fee.
What is the difference between AdGuardHome and landscape?
AdGuardHome is written in TypeScript and landscape in Rust. 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 landscape?
Choose AdGuardHome if you want the larger community (38,394 stars) or its GPL-3.0 licence terms. Choose landscape if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.