A · leads
Traefik
97.9
65,574 stars · MIT
DevOps
Traefik leads by 10.4 · clear
A · leads
97.9
65,574 stars · MIT
B
87.5
5,330 stars · BSD-3-Clause
Traefik versus tsuru is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 97.9 for Traefik and 87.5 for tsuru.
Traefik has 65,574 GitHub stars to tsuru's 5,330, a gap of 60,244 (12.30×). Forks are 6,319 for Traefik and 554 for tsuru. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 72.
Push history: Traefik was last pushed on 17 November 2026 (0 days ago), and tsuru was last pushed on 14 November 2026 (3 days ago). Open issues stand at 993 for Traefik (0.015 per star) and 24 for tsuru (0.005 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Traefik is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. tsuru is listed as BSD-3-Clause, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for Traefik and 96 for tsuru. This is a procurement signal, not legal advice.
In DevOps, both Traefik (65,574 stars) and tsuru (5,330 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Traefik is open source, tsuru is open source.
The lead is split. Traefik is furthest ahead on fork community (100 to 72), while tsuru is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Traefik finishes ahead at 97.9 against tsuru at 87.5, a 10.4 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Traefik | tsuru |
|---|---|---|
| GitHub stars | 65,574 | 5,330 |
| Forks | 6,319 | 554 |
| Open issues | 993 | 24 |
| Adoption | 100 | 77 |
| Activity | 100 | 100 |
| Community | 100 | 72 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 87.5 |
Traefik is a reverse proxy and ingress controller that configures itself from Docker, Kubernetes, or other orchestrators. It terminates TLS and routes traffic to services.
Open source and extensible Platform as a Service (PaaS).
Traefik has more GitHub stars: 65,574 versus 5,330 for tsuru. The gap is 60,244 stars.
Traefik was pushed more recently: 17 November 2026 versus 14 November 2026 for tsuru. That is 3 days apart.
Yes. This catalog marks both Traefik and tsuru as self-hostable. Confirm each project's deploy docs before you plan a migration.
Traefik is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. tsuru is listed as BSD-3-Clause, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Traefik scores 97.9 and tsuru scores 87.5. This page calls that a clear lead for Traefik.