Traefik is not acting like a sleepy ingress controller. It shipped 21 releases in 90 days, 11 release events in the last 30 days, and the repo still shows work landing across v2.11, v3.6, and v3.7 at the same time. That is a maintenance machine, not a one-off spike.
The official site now frames Traefik as an all-in-one, self-hosted, cloud-native, GitOps-driven application proxy, API gateway, and API management platform. It also pushes harder than the old ingress story, with product paths for API management, runtime governance, API mocking, and a banner for the Ingress NGINX Migration Kit. The message is clear: Traefik is betting on being the traffic layer for teams that want one control point across proxies, gateways, and API policy.
The release notes back that up. v3.7.0-rc.3 adds an ingress-nginx metamodel for dynamic config and limit-connections support. v3.6.15 and v2.11.44 both include the same core fixes, including the new errorRequestHeaders option for the Errors middleware and ACME dependency bumps. That kind of overlap says the team is keeping older lines alive while still pushing the newer branch forward.
The public site still says “50K stars on GitHub,” but GitHub shows 62,968 stars. I would treat the site number as marketing shorthand, not a precise count. The more useful signal is that the repo has 544 tags, 6,180 commits, and a release cadence that does not look stalled.
What this data does not tell you
ToolVitals can see stars, releases, commits, and uptime signals. It cannot tell you whether Traefik is easy to operate in your stack, whether the docs fit your team, whether the API management layer is worth the money, or whether the product is actually better than the alternatives in your environment. It also cannot prove code quality or customer satisfaction.
Two of the announcement URLs in the payload now return 404, so I could not use them as evidence for current messaging. That limits how hard I can lean on them. The live homepage and release pages still show enough to infer the current direction, though.
How it compares
Against Dapr, Traefik has the same 11 release events in the last 30 days, but Traefik has 62,968 GitHub stars versus Dapr’s 25,718. Against Open SRE, Traefik ships less often on the 30-day window, 11 versus 26 release events, but Traefik still has far more adoption by star count. This is not the hottest project by raw release count. It is the larger one that still moves.
Bottom line
If your team runs Kubernetes ingress, wants a proxy plus gateway in one place, or needs a migration path from ingress-nginx without freezing on old traffic patterns, Traefik is worth evaluating now. If you only need a narrow ingress layer and do not care about API management, ignore the bigger platform pitch and test the proxy path first. The product has clearly widened its scope, so make sure you want the whole thing before you buy into the story.