Artificial intelligence is reshaping many industries, and open source is no exception. But the change is not about a surge in AI-focused open source projects or a battle over licenses. Instead, AI is accelerating a quiet transformation that has been underway for years: open source is becoming the control plane for modern infrastructure. The days of open source as a fringe alternative or a morality play are over. Today, it is where serious companies invest to shape the foundational layers on which AI and other workloads depend.
Infrastructure, not ideology
The numbers tell an unambiguous story. The Cloud Native Computing Foundation (CNCF) now hosts more than 230 projects with over 300,000 contributors worldwide. Its 2025 survey found that 98% of organizations have adopted cloud-native techniques, and 82% of container users run Kubernetes in production. GitHub's Octoverse report for 2025 records 1.12 billion contributions from more than 180 million developers, with a record 518.7 million merged pull requests. The Apache Software Foundation (ASF) reported 9,905 committers working across 295 projects, issuing 1,310 software releases in its fiscal year 2025. These are not signs of decline; they are evidence of mainstream maturation.
But beneath the aggregate numbers lies a more revealing pattern: who contributes and why. In 2025, CNCF Devstats showed Red Hat leading all contribution activity with 194,699 contributions. Microsoft was second with 107,645, and Google third with 91,158. Independent contributors placed fourth with 52,404, reminding us that open source retains a community fabric. However, the center of gravity is unmistakably corporate. The top contributors have remained consistent over the past decade, signaling a long-term strategic commitment. At the same time, the contributor base has broadened significantly, with thousands of organizations now participating.
This shift changes how we should interpret open source involvement. Too many discussions still frame contributions as philanthropy or civic virtue. Many open source program offices still try to convince engineers to contribute because "it's the right thing to do," hoping to ingratiate their company into a nebulous community. That narrative no longer fits. Open source is increasingly where vendors set defaults, normalize interfaces, and shape the operational assumptions that everyone else must follow. It is about control—not proprietary lock-in, but influence over the layers where ecosystems harden into standards. The companies investing upstream are not driven by altruism; they understand that whoever shapes the substrate gains leverage over everything built on top of it.
Strategic investments in key projects
Red Hat's dominance in CNCF contributions is easily explained. Its OpenShift platform is built around Kubernetes, and the company's business depends on Kubernetes remaining the de facto container orchestration standard. Red Hat's contributions are product strategy, not community service. Fortunately for Kubernetes, Red Hat is not alone—a growing, diverse contributor base across thousands of organizations ensures the project does not rely on any single patron.
Microsoft's position is even more telling. Once the embodiment of open source hostility, it now ranks second in CNCF contributions. The more interesting signal is where companies like Microsoft are directing their efforts. OpenTelemetry has become one of the fastest-rising CNCF projects, with a 39% increase in commits in 2025 and a contributor base that grew from 1,301 to 1,756 in a single year. Again, this is not charity. Observability standards are a land grab. Microsoft, Splunk, and other top contributors help shape OpenTelemetry so that their products integrate seamlessly and their customers are locked into compatible ecosystems.
Then there is Cilium, a project that proves even boring infrastructure can become exciting. Cilium's journey report shows the number of contributing companies rose 90% after it joined CNCF, from 533 to 1,011, while individual contributors jumped from 1,269 to 4,464. Google, Datadog, and Cloudflare all expanded their contributions as the project matured. Cilium sits at the intersection of networking, observability, and security—categories that become mission-critical once workloads become distributed, latency-sensitive, and expensive. AI may drive headlines, but the real strategic work often happens in projects like Cilium, where infrastructure determines whether AI workloads are governable, visible, and efficient.
The AI imperative
Nvidia's role illustrates the direction open source is heading in AI. Despite its immense resources, the company chooses to engage through developer communities rather than lump-sum cash payouts. Nvidia ranked 14th in Kubernetes contributions over the past two years, with 5,892 contributions. It has open sourced KAI Scheduler, a Kubernetes-native GPU scheduler from Run:ai, and describes itself as a key contributor to Kubeflow. Nvidia is not just selling chips; it is investing in the scheduling, orchestration, and workflow layers that determine how effectively those chips get used in real-world AI systems.
According to CNCF, 66% of organizations hosting generative AI models now use Kubernetes for some or all inference workloads. The foundation explicitly calls Kubernetes the de facto operating system for AI. While this self-serving statement deserves scrutiny, the underlying reality is undeniable: Kubernetes and Kubeflow are increasingly central to both training and inference pipelines. AI is making open infrastructure more important because few organizations want to build their future on opaque, inescapable infrastructure they cannot inspect or influence.
The evolution of open source mirrors the evolution of enterprise IT. It has moved from experimentation to standardization, from fringe to essential. The romantic stories of the early 2000s—developers coding for passion, licenses fighting for freedom—have given way to a more pragmatic reality. Open source is where the cloud-native stack gets standardized, where observability gets normalized, where platform engineering gets productized, and where AI infrastructure is increasingly being built. It is less romantic and more essential. And that is exactly what the industry needs.
Source:InfoWorld News