head to head · open source
caddy vs landscape
caddy has 79,021 GitHub stars, 5,257 forks, 286 open issues and last shipped 2 days ago. landscape has 1,598 stars, 125 forks, 29 open issues and last shipped yesterday. caddy leads on adoption by 4,845% (79,021 vs 1,598 stars). caddy is written in Go under Apache-2.0; landscape is written in Rust under GPL-3.0. caddy has attracted 7% as many forks as stars, landscape 8%. landscape 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
| caddy | landscape | |
|---|---|---|
| GitHub stars | ★ 79K | ★ 1.6K |
| License | Apache-2.0 | GPL-3.0 |
| Written in | Go | Rust |
| Last push | 2026-11-11 | 2026-11-12 |
| Forks | ⑂ 5.3K | ⑂ 125 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick caddy if
- You weight community size — 79K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- 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 caddy
a project Every site on HTTPS Caddy is an extensible server platform that uses TLS by default. Releases · Documentation · Get Help Powered by Special thanks to: Warp, built for coding with multiple AI agents Available for MacOS, Linux, & Windows Menu Features Install Build from source For development With version information and/or plugins Quick start Overview Full documentation Getting help About Features Easy configuration with the Caddyfile Powerful configuration with its native JSON config Dynamic configuration with the JSON API Config adapters if you don't like JSON Automatic HTTPS by default ZeroSSL and…
read the full caddy 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 caddy or landscape more popular?
caddy has 79,021 GitHub stars and landscape has 1,598. caddy has the larger community by that measure.
Are caddy and landscape free?
Both are open source. caddy is licensed under Apache-2.0 and landscape under GPL-3.0. Neither carries a licence fee.
What is the difference between caddy and landscape?
caddy is written in Go 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, caddy or landscape?
Choose caddy if you want the larger community (79,021 stars) or its Apache-2.0 licence terms. Choose landscape if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.