From Singapore: The developer tooling market is undergoing a quiet but consequential power shift, and Amazon Web Services is placing its chips accordingly. This week, the Eclipse Foundation confirmed that AWS has made a strategic infrastructure investment in the Open VSX Registry, the vendor-neutral extension registry used by editors built on VS Code's open-source codebase. Core services will migrate to AWS infrastructure hosted in Europe, with a secondary on-premises environment retained in Canada for resilience.
The move is not philanthropic. Open VSX powers a growing ecosystem of AI-enabled and cloud-based developer platforms, including Amazon's own Kiro, Google's Antigravity, Cursor, IBM's Bob, VSCodium, Windsurf, and Ona. For AWS, underwriting the registry's infrastructure means securing the extension supply chain for its own IDE product while simultaneously strengthening a commons that its commercial rivals also depend on. That is a calculated form of open-source investment, not altruism.
With peak daily traffic exceeding 50 million requests and more than 10,000 extensions from over 6,500 publishers, Open VSX has become a critical production dependency for developer platforms serving millions of users worldwide. The registry now sits on apparently firm footing, with over 300 million monthly downloads, a striking contrast to its near-collapse just three years ago.
The backstory is instructive. The Open VSX project was started by GitPod (now Ona) in early 2020 as a vendor-neutral registry for use by Code-OSS forks, including VSCodium and Theia. The reason such a registry exists at all comes down to a deliberate restriction by Microsoft: Open VSX provides extensions unencumbered by the restriction Microsoft places on its VS Code marketplace, which bars alternative products built on a fork of the Code-OSS repository from accessing it. Microsoft cites security and compatibility as reasons, and there is no business case to "run a full-scale global service for everyone to use," in the words of Chris Dias, who was head of product for VS Code at the time.
That Microsoft restriction, reasonable on its own terms, has had the unintended effect of spurring a parallel ecosystem. In early 2023, Eclipse community manager John Kellerman appealed for funding, warning that "we will be forced to decommission the Open VSX registry by the end of May." The AI development boom changed the calculus entirely; suddenly, dozens of AI-native editors needed a workable extension registry, and Open VSX was the only viable option.
The infrastructure changes announced this week go beyond simply adding cloud capacity. There is also work in progress on a new verification framework, which will attempt to block malicious and impersonated extensions. Supply chain security in developer tooling has become a serious concern as automated pipelines proliferate, and the Eclipse Foundation is positioning the registry as enterprise-grade infrastructure rather than a community side project. Separately, Open VSX is no longer free for all users: in January, the project introduced usage tiers, with subscriptions required for organisations generating more than 75 requests per second.
That commercialisation decision will be contentious in open-source circles. Defenders of the model argue that the existing funding model of open source registries and repositories is fundamentally broken, because they are now embedded within software engineering workflows in ways that were never intended. Critics, for their part, will note the irony of an open alternative to a proprietary marketplace introducing its own paywalled tier. Both arguments have merit.
Meanwhile, the 2025 State of Rust survey, published this week by the Rust Survey Team, offers a concrete data point on where developer preferences are heading. VS Code usage among Rust developers has declined from 61.7 percent to 51.6 percent in three years. The Rust-powered Zed editor has grown from almost nothing to 18.6 percent usage, while JetBrains' dedicated Rust Rover IDE has seen a slight decline, from 16.4 percent to 14.4 percent. Rust developers are a technically sophisticated cohort, and their preferences often anticipate broader trends.
For Australian software businesses and developers, the trade implications are direct. The IDEs their teams use shape which cloud services they consume, which extension marketplaces they depend on, and ultimately which vendors they are locked into. A more competitive IDE market, anchored by a healthier Open VSX, is good for choice and potentially good for procurement budgets. The 2025 Stack Overflow developer survey still placed VS Code at 76.2 percent usage among professional developers globally, so Microsoft's position is not under immediate threat. But the Rust data, and the AWS investment, suggest the competitive pressure is real and growing.
The honest read on this story is that no single actor is clearly in the right or wrong. Microsoft has legitimate reasons to restrict its marketplace. AWS has legitimate commercial motivations for its generosity. The Eclipse Foundation faces genuine sustainability pressures that usage tiers help address. What is clear is that the developer tooling market is becoming more contested, and the AI development wave is the primary accelerant. For developers and the organisations that employ them, that competition is likely to produce better tools. The uncertainty is whether the open-source infrastructure underpinning all of it will receive the sustained investment it needs before the next near-collapse.