Traefik is not coasting on being a familiar reverse proxy. The current signal is sharper: Traefik Labs is turning Ingress NGINX migration into a product wedge, and the project is shipping enough to back the message. ToolVitals sees 17 release events in 30 days, 25 GitHub releases in 90 days, 63,215 GitHub stars, a 94 shipping score, and a 97 overall ToolVitals score.

The Traefik homepage now positions the product as a self-hosted, cloud-native, GitOps-driven application proxy, API gateway, and API management platform. That is broader than the old mental model of Traefik as only ingress or reverse proxy plumbing. The recent content makes the direction clearer: win the Kubernetes gateway layer, then stretch that control point into API management and AI traffic governance.

The interesting signal: migration, not novelty

The Traefik Proxy 3.7 announcement is the center of the story. Traefik says v3.7 adds support for more than 85 Ingress NGINX annotations, a certificates view in the dashboard, middlewares on services, full Gateway API v1.5 support, and retries and failover driven by HTTP status codes. That is not a random bag of features. It is a migration program.

The surrounding blog series says the quiet part out loud. The audit post frames most Ingress NGINX migrations as mechanical, with the hard part being upfront discovery. The install guide recommends running Traefik side by side with Ingress NGINX under a separate IngressClass, then moving routes one by one. That is a practical pitch to platform teams: reduce blast radius first, then migrate.

This matters because infrastructure buyers rarely switch gateways for vibes. They switch when an existing component becomes risky, stale, expensive, or strategically limiting. Traefik is aiming at that moment with a compatibility story, not just a feature checklist.

The patch releases tell a similar story at maintenance level. GitHub release v3.6.16 includes Kubernetes CRD, Ingress NGINX, OpenTelemetry, Docker, and ECS fixes. v2.11.45 carries selected fixes for the older line. ToolVitals does not have 30-day commit counts for this payload, but 25 releases in 90 days is enough to show active release management.

The AI angle is gateway politics

Traefik’s AI gateway article argues that cross-cutting concerns such as auth, rate limits, observability, policy enforcement, prompt safety, model fallback, and token-cost control belong at a shared gateway layer, not scattered through app code. That is a positioning move.

It connects the Kubernetes migration push to a broader claim: the gateway is the place where platform teams regain control as traffic patterns get messier. Whether Traefik wins that AI control plane is not proven by ToolVitals data. But the bet is visible in first-party material, and it fits the product’s existing strengths.

What ToolVitals cannot infer

ToolVitals can say Traefik is highly active by release events, has strong GitHub attention at 63,215 stars, and has a high health score of 100 with data confidence of 91. It can also say the project has an MIT license signal and qualifies as OSI-approved open source in this payload.

ToolVitals cannot tell you whether Traefik 3.7’s Ingress NGINX compatibility works for your cluster. It cannot inspect your annotations, your ConfigMap defaults, your failure modes, your team skill, your security posture, or your migration risk. It also cannot infer customer satisfaction, revenue, support quality, or code quality from these metrics alone.

One browsing wrinkle: the RSS URLs in the payload for some Traefik posts resolved as 404 without the /blog/ path, while the same first-party articles were available under /blog/. That looks like a URL-shape issue, not evidence that the announcements disappeared. The prose here relies on the working first-party /blog/ URLs and GitHub release pages.

How it compares

Against LangChain, Traefik has fewer stars, 63,215 versus 137,031, and fewer 30-day release events, 17 versus 20. LangChain also has a 100 shipping score compared with Traefik’s 94. Different category pressure, but useful context: Traefik is not the loudest developer tool in this dataset. It is still shipping near the top tier.

Against n8n, the contrast is licensing and tempo. n8n shows 188,540 stars, 45 release events in 30 days, and a 100 shipping score, but ToolVitals classifies it as fair-code, not OSI-approved open source. Traefik’s payload classifies it as OSI-approved open source under MIT, with no hosted pricing tracked. For teams that care about license posture in infrastructure components, that distinction is not cosmetic.

Recommendation

If your team runs Ingress NGINX and already has migration pressure, evaluate Traefik 3.7 because the product work is aimed directly at your problem: annotation compatibility, Gateway API support, side-by-side deployment, and route-by-route cutover. Start with an audit. Do not rip out the old controller in one move unless you enjoy incident calls and bad coffee.

If you are only looking for a generic edge proxy, Traefik is still credible, but the strongest current reason to re-evaluate it is the migration path. The data says the project is alive. The first-party release material says the team knows exactly which door it wants platform engineers to walk through.

Sources