head to head · open source
traefik vs landscape
traefik has 65,548 GitHub stars, 6,313 forks, 939 open issues and last shipped yesterday. landscape has 1,598 stars, 125 forks, 29 open issues and last shipped yesterday. traefik leads on adoption by 4,002% (65,548 vs 1,598 stars). traefik is written in Go under MIT; landscape is written in Rust under GPL-3.0. traefik has attracted 10% as many forks as stars, landscape 8%. traefik 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
| traefik | landscape | |
|---|---|---|
| GitHub stars | ★ 66K | ★ 1.6K |
| License | MIT | GPL-3.0 |
| Written in | Go | Rust |
| Last push | 2026-11-12 | 2026-11-12 |
| Forks | ⑂ 6.3K | ⑂ 125 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick traefik if
- You weight community size — 66K stars and counting
- You want the MIT 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 traefik
Traefik (pronounced traffic ) is a modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components (Docker, Swarm mode, Kubernetes, Consul, Etcd, Rancher v2, Amazon ECS, ...) and configures itself automatically and dynamically. Pointing Traefik at your orchestrator should be the only configuration step you need. . Overview . Features . Supported backends . Quickstart . Web UI . Documentation . . Support . Release cycle . Contributing . Maintainers . Credits . :warning: When migrating to a new major version of Traefik, please…
read the full traefik 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 traefik or landscape more popular?
traefik has 65,548 GitHub stars and landscape has 1,598. traefik has the larger community by that measure.
Are traefik and landscape free?
Both are open source. traefik is licensed under MIT and landscape under GPL-3.0. Neither carries a licence fee.
What is the difference between traefik and landscape?
traefik 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, traefik or landscape?
Choose traefik if you want the larger community (65,548 stars) or its MIT licence terms. Choose landscape if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.