The infrastructure layer of cloud computing rarely makes headlines outside of developer circles. But when IBM’s stewardship of a widely used open-source project starts driving enterprise users toward a competitor, the business implications ripple far beyond code repositories.
Traefik Labs, the company behind the open-source Traefik Proxy, is positioning itself as the natural successor to Kubernetes Ingress NGINX — a project that has languished under IBM’s watch since the company acquired it through its Red Hat purchase. According to The Next Web, Traefik has been aggressively courting organizations looking to migrate away from Ingress NGINX, and the numbers suggest the pitch is landing.
This isn’t a minor skirmish over developer preferences. It’s a fight over who controls the front door of modern cloud applications.
Kubernetes ingress controllers manage how external traffic reaches services running inside a cluster. Every API call, every user request, every data payload passes through this layer. The company that owns that chokepoint owns an enormously valuable position in the enterprise software stack — one that can be monetized through premium features, support contracts, and adjacent product sales. Traefik Labs understands this. So does IBM, which is why the current situation is so revealing about the strategic missteps large acquirers make with open-source assets.
The backstory matters here. NGINX, originally an open-source web server created by Igor Sysoev in 2004, became one of the internet’s most critical pieces of infrastructure. F5 Networks acquired NGINX Inc. in 2019 for $670 million. Meanwhile, the Kubernetes-specific fork — Ingress NGINX — ended up under IBM’s umbrella through the Red Hat acquisition, which closed the same year at a staggering $34 billion. IBM got Ingress NGINX almost as an afterthought, bundled into Red Hat’s massive Kubernetes platform, OpenShift.
And that’s precisely the problem.
When a $34 billion acquisition treats a critical infrastructure component as a line item, maintenance suffers. Community contributions slow. Security patches arrive late. Enterprise users notice. According to The Next Web’s reporting, frustration with the pace of development and responsiveness around Ingress NGINX has been building for months, creating an opening that Traefik Labs has been quick to exploit.
Traefik’s growth numbers tell a compelling story. The project has been downloaded more than 3 billion times, according to the company’s own figures. It consistently ranks among the most popular ingress controllers in the Cloud Native Computing Foundation’s annual surveys. A 2022 CNCF survey found Traefik used by 28% of respondents, making it one of the top three ingress solutions alongside NGINX-based options. That share has almost certainly grown since, given the trajectory of community engagement and GitHub activity.
For Traefik Labs, the business model follows a well-established open-source playbook. Give away the core product. Build a community. Then sell an enterprise version — in this case, Traefik Enterprise and the Traefik Hub platform — that adds the management, security, and observability features large organizations demand. The company raised $10 million in a Series A round and has been growing its commercial customer base, though it remains privately held and doesn’t disclose revenue figures.
The strategic question for Traefik Labs is whether this moment of IBM-induced frustration can be converted into lasting enterprise relationships. Open-source migrations are sticky. Once a company standardizes on an ingress controller across hundreds or thousands of clusters, switching costs become significant. Every month that Traefik captures a new enterprise deployment is a month that locks in future support revenue and creates cross-selling opportunities for its broader API management tools.
For IBM, the calculus is different but no less consequential. Red Hat’s OpenShift is the company’s primary weapon in the hybrid cloud wars against Amazon Web Services, Microsoft Azure, and Google Cloud. OpenShift generated an estimated $1.2 billion in annual recurring revenue as of IBM’s most recent earnings disclosures. Losing credibility on a foundational component like ingress control doesn’t directly threaten that revenue stream — yet. But it erodes the developer trust that ultimately drives platform adoption. And developer trust, once lost, is extraordinarily expensive to rebuild.
IBM has been here before. The company’s history with open-source stewardship is mixed at best. It contributed heavily to Linux and Eclipse, earning goodwill that lasted decades. But it also let projects atrophy when they didn’t align with immediate commercial priorities. The Ingress NGINX situation fits the latter pattern uncomfortably well.
So what does this mean for the broader competitive field?
F5 Networks, which owns NGINX Inc. and sells the commercial NGINX Plus product, faces its own set of pressures. The company reported $2.8 billion in revenue for fiscal year 2024, with its software and subscription revenue growing but its legacy hardware business declining. F5 has been pushing hard to reposition NGINX as a modern API gateway and connectivity platform, but the confusion between NGINX (the commercial product), NGINX open source, and Kubernetes Ingress NGINX creates market fragmentation that benefits nimbler competitors like Traefik.
There’s also the question of what happens further up the stack. API gateways, service meshes, and ingress controllers are converging into a single connectivity layer. Kong, another open-source API gateway company, raised $100 million at a $1.4 billion valuation in 2021 and competes directly with both Traefik and NGINX-based solutions. Solo.io, the company behind the Gloo gateway built on Envoy Proxy, has raised over $180 million. The market is crowded, well-funded, and increasingly defined by which vendor can offer the most coherent story from the edge of the cluster all the way to individual microservices.
Traefik’s advantage in this race is simplicity. Developers consistently cite its ease of configuration and native Kubernetes integration as differentiators. In a world where platform engineering teams are stretched thin — Gartner estimates that 80% of large software organizations will have established platform engineering teams by 2026 — tools that reduce operational burden command premium pricing power. That’s a direct line from developer experience to enterprise revenue.
But simplicity alone won’t win the enterprise. Large organizations buying infrastructure software care about support SLAs, compliance certifications, and vendor stability. Traefik Labs, as a relatively small company, needs to demonstrate it can meet those requirements at scale. Every major enterprise deal will involve procurement teams asking uncomfortable questions about the company’s balance sheet and long-term viability. The $10 million Series A, while sufficient for a focused open-source company, looks modest next to competitors backed by hundreds of millions in venture capital or the balance sheets of IBM and F5.
The timing of this competitive shift also intersects with a broader trend: the growing enterprise appetite for multi-cloud and hybrid architectures. According to Flexera’s 2024 State of the Cloud report, 89% of enterprises have a multi-cloud strategy. Ingress controllers that work consistently across AWS, Azure, Google Cloud, and on-premises environments hold an inherent advantage. Traefik’s cloud-agnostic positioning fits this demand pattern. IBM’s OpenShift-centric approach, while powerful within its own sphere, can feel constraining to organizations that don’t want to commit to a single platform vendor.
None of this means IBM will abandon Ingress NGINX or that Traefik’s ascent is guaranteed. Corporate infrastructure decisions move slowly, governed by change management processes and risk aversion. Many organizations running Ingress NGINX today will continue running it for years, regardless of community sentiment. Inertia is a powerful force in enterprise IT.
Still, the direction is clear. The companies that invest in developer experience, maintain active open-source communities, and convert that goodwill into commercial products are winning the infrastructure layer. Traefik Labs is executing that playbook with discipline. IBM, distracted by the sheer scale of its hybrid cloud ambitions, is leaving an opening. And in enterprise software, openings like this don’t stay open for long.
The bottom-line impact will take time to materialize in earnings reports. But the strategic repositioning is happening now, one Kubernetes cluster at a time.
WebProNews is an iEntry Publication