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 evolve the Java estates you’re already responsible for.
Java 26 gives you concrete tools to do that.
What’s in the Release
Java 26 delivers 10 JDK Enhancement Proposals (JEPs) focused on performance, AI readiness, security, and language modernization, plus thousands of additional stability and reliability improvements.
From a DevOps perspective, a few stand out.
Startup and throughput. JEP 516 (Ahead-of-Time Object Caching) reduces application startup time and improves warm-up performance across any garbage collector, including the low-latency ZGC. JEP 522 increases throughput with the G1 garbage collector by reducing synchronization between application and GC threads. Both of these matter at scale — faster startup means faster scaling, and better throughput means doing more with the hardware you already have.
Concurrency for AI workloads. JEP 525 (Structured Concurrency) simplifies how teams build and manage multithreaded code. This is particularly relevant for agentic AI workloads, where coordinating multiple tasks across threads — and handling failures gracefully — is central to ensuring the reliability of those systems.
Security posture. JEP 500 enforces Java’s “integrity by default” principle, preventing unintended modifications to final fields. JEP 524 adds standardized PEM encoding for cryptographic objects, simplifying compliance workflows. Java 26 also introduces Hybrid Public Key Encryption (HPKE) out of the box and post-quantum ready JAR signing, which matters for teams starting to think about long-term supply chain security.
HTTP/3 support. JEP 517 adds HTTP/3 to the HTTP Client API, enabling Java microservices and APIs to benefit from reduced latency and more reliable connections with minimal code changes.
The Java Verified Portfolio Changes the Support Equation
The bigger operational story in this release may be the introduction of the Oracle Java Verified Portfolio (JVP). This is a new, curated set of Oracle-supported tools, frameworks, and libraries designed to extend enterprise support beyond the JDK itself.
At launch, JVP includes commercial support for three components:
Helidon is Oracle’s open-source, cloud-native microservices framework. It’s built on Java Virtual Threads, integrates with LangChain4j, and supports MCP-based AI agent development. Previously, commercial support for Helidon was only available to Oracle WebLogic and Coherence customers. JVP opens that up to all Java SE subscribers and OCI customers at no additional cost.
JavaFX is back under commercial support after a multi-year gap. Oracle is reintroducing it to meet demand for rich, interactive UIs — particularly in AI-driven analytics and data visualization. Support now covers all LTS versions during their five-year Premier Support window.
The Java Platform Extension for VS Code rounds out the portfolio. With over 5.1 million downloads and a perfect 5.0 rating, this extension now has enterprise-backed support, including compatibility with new JDK features as soon as they’re introduced.
For DevOps teams, JVP changes the conversation about supply chain risk. Instead of tracking multiple upstream sources with varying support timelines, you get a single, Oracle-governed source of truth for these components — with clear roadmap alignment to JDK releases.
The AI Strategy is Three-Pronged
Oracle’s approach to Java and AI isn’t limited to runtime improvements. The briefing team outlined a three-part strategy: agentic development (using tools like Embabel, Spring AI, and Oracle Code Assist to build AI-assisted development workflows), model integration from existing Java business applications (via Helidon MCP, LangChain4j, and the OCI SDK for Java), and model training and deployment (coming through future work in Projects Panama, Valhalla, and Babylon).
Georges Saab, senior vice president of the Oracle Java Platform, put it plainly during a pre-release briefing: “We think very carefully about what we put into Java. We try to balance a story of long-term stability for your workloads that need that, but also aggressively pushing with innovation on the things that need that.”
The near-term story for most enterprise teams is the middle layer: integrating AI capabilities into existing systems. Java 26 and the JVP make that easier without requiring a platform migration.
Donald Smith, VP of Java Product Management, pointed to rising demand as the driver behind some of the commercial support decisions in this release: “We’re seeing an increased interest in building analytics-type applications in Java, thanks to AI. That’s one of the reasons we’re bringing JavaFX back. And on top of that, we’re formalizing support for tools that customers have already been relying on — making it explicit that they can engage us directly.”
“Java 26 signals a deliberate move by Oracle to position the JVM as the control plane for enterprise AI workloads, not just a runtime for existing applications. The Java Verified Portfolio extends that claim into the tooling layer, giving DevOps teams a governed supply chain for frameworks and libraries that were previously managed through fragmented upstream sources. For teams running Java estates at scale, the support consolidation and concurrency improvements in this release are execution obligations, not future-state planning,” according to Mitch Ashley, VP and practice lead for software lifecycle engineering at The Futurum Group.
The Practical Takeaway
Java 26 isn’t an LTS release — Java 25 holds that designation as the next long-term support version. But for teams actively modernizing their Java estates or evaluating where to add AI capabilities, this release provides useful stepping stones: better performance, stronger security defaults, improved concurrency, and a new portfolio that simplifies the tooling ecosystem.
The case Oracle is making with Java 26 is straightforward: the infrastructure you’ve already built on Java is the right foundation for what comes next. This release is designed to help you close the gap between where your systems are today and where they need to be as AI workloads become operational.
Java 26 is available now at dev.java. JavaOne 2026 runs March 17–19 at the Oracle Conference Center in Redwood Shores, California.