Skip to main content

Eclipse Foundation Unfurls Managed VSX Registry Service

The Eclipse Foundation today announced it will make available a managed instance of the Open VSX Registry available to industry partners for a fee.

Thabang Mashologu, chief marketing officer and head of products at the Eclipse Foundation, said the Open VSX Managed Registry provides an economically sustainable approach to providing access to a registry that is now widely invoked within application development workflows that incorporate tools based on open source VS Code.

Initial customers of the Open VSX Managed Registry include Amazon Web Services (AWS), Google, and Cursor, which will continue to incorporate the registry in the services they provide application developers. That approach provides a means to support application development teams using those tools without requiring them to sign up for an additional service provided by the Eclipse Foundation.

That registry maintained by the Eclipse Foundation has been consuming significant infrastructure resources as more AI coding tools from AWS, Google, Cursor, Windsurf and IBM are more widely adopted, noted Mashologu.

The Open VSX Registry already serves more than 300 million downloads per month, with peak daily traffic exceeding 200 million requests. The registry also hosts more than 12,000 extensions from more than 8,000 publishers.

Hosting a global extension registry at this scale requires significant investment in compute capacity, bandwidth, storage, security operations, and the engineering expertise necessary to maintain availability and resilience, noted Mashologu. In the AI era, those costs have skyrocketed, he added.

Designed to run in multiple regions, the Open VSX Managed Registry provides enterprise-grade reliability and accountability while preserving open governance, vendor neutrality, and free access for developers, said Mashologu. The usage-aligned model ensures commercial consumption funds the operational investment required to keep Open VSX secure, resilient, and sustainable, he added

Specifically, it provides 99.95% availability targets with service credits, a set of defined usage tiers based on request-per-second consumption, 24/7 monitoring and tier-based incident response aligned with defined service level agreements (SLAs), capacity planning for high-volume automated workloads and identity-based access controls and usage dashboards.

It’s not clear to what degree other open source software projects that have become integral elements of software engineering workflows might follow the Eclipse Foundation’s approach for providing a managed service to defer infrastructure costs.

Each software engineering team will need to determine for itself to what degree dependencies on free services that might not be economically sustainable have been embedded into its workflows. Last year, leading stewards of several major open source projects issued a joint open letter calling for major changes to be made to the way the IT infrastructure used to support these initiatives is funded, operated and maintained. Posted on the Open Source Security Foundation (OpenSSF) website, the open letter signed by representatives from open source projects such as Maven Central/Sonatype, OpenJS, The Python Software Foundation and The Rust Foundation called for fundamental reforms to be made in terms of both how IT infrastructure is funded and the way open source software is being consumed.

One way or another, the one certain thing is that, unlike open source software itself, the infrastructure used to host these projects is anything but free.



from DevOps.com https://ift.tt/aD290gr
Labels:

Comments

Post a Comment

Popular posts from this blog

Claude Code’s Ultraplan Bridges the Gap Between Planning and Execution

Planning a complex code change is hard enough. Reviewing it in a terminal window shouldn’t make it harder. Anthropic is addressing that friction with a new capability called Ultraplan, currently in research preview as part of Claude Code. The feature moves the planning phase of a coding task from your local terminal to the cloud — and gives developers a richer environment to review, revise, and approve a plan before a single line of code changes. It’s a small workflow shift with real practical value, especially for teams working on large-scale migrations, service refactoring, or anything that requires careful coordination before execution begins. How it Works Ultraplan connects Claude Code’s command-line interface (CLI) to a cloud-based session running in plan mode. When a developer triggers it — either by running /ultraplan followed by a prompt, typing the word “ultraplan” anywhere in a standard prompt, or choosing to refine an existing local plan in the cloud — Claude picks u...
Post a Comment
Read more

Security as Code is Becoming the New Baseline: Continuous Compliance in DevOps 

There was a time when compliance meant a quarterly ritual. Someone from security would walk over with a spreadsheet, ask a few questions, tick a few boxes and disappear until the next audit cycle. The infrastructure team would scramble to prove that yes, encryption was enabled, and no, that S3 bucket was not public anymore. Everyone felt relieved, went back to shipping features and quietly hoped nothing would drift before the next review.   That model is dead; it just hasn’t been buried yet.   The problem is not that teams lack security awareness. Most engineering organizations today understand that vulnerabilities need catching early and that production environments need hardening. The problem is that compliance has historically lived outside the delivery pipeline — treated as a checkpoint rather than a continuous practice. In a world where teams deploy dozens of...
Post a Comment
Read more

Java 26 Arrives With AI Integration and a New Ecosystem Portfolio — What It Means for DevOps Teams

Oracle released Java 26 on March 17, 2026, and while every six-month release comes with its own set of improvements, this one carries a broader message: Java isn’t just keeping pace with the AI era — it’s actively positioning itself as the infrastructure layer where AI workloads will run. For DevOps teams managing large Java estates, that’s worth paying attention to. The Scale of What You’re Already Running Before getting into what’s new, it helps to remember what’s already in place. According to a 2025 VDC study, Java is the number one language for overall enterprise use and for cloud-native deployments. There are 73 billion active JVMs running today, with 51 billion of those in the cloud. That scale matters when you’re thinking about where AI fits in. Most of the systems where agentic AI will eventually operate — transactional platforms, backend services, data pipelines — are already running on Java. The question for DevOps teams isn’t whether to adopt Java for AI. It’s how to ...
Post a Comment
Read more