Java migration to Azul Platform Core.

Azul Platform Core is the leading independent commercial OpenJDK distribution, offering a fully compatible Java SE runtime under a commercial support model that competes directly with Oracle Java SE Universal. For customers facing the Java SE Universal employee count economics, Azul Platform Core represents a credible alternative that can reduce the Java total cost of ownership by 60 to 80 percent, while preserving the commercial support, security patching, and certification benefits that drove the original Oracle Java commitment.

This article walks through the migration economics, the technical equivalence analysis, the Oracle audit defence considerations, and the buyer side framework for evaluating and executing the migration.

Why customers move from Oracle Java to Azul

The primary driver of the migration is the cost. The Java SE Universal employee count model produces a Java cost that scales with the entire workforce, regardless of the actual Java footprint. A 10,000 employee customer with a modest Java estate pays Oracle 1 million to 2 million dollars per year for a runtime that, on a per usage basis, is worth a small fraction of that figure. Azul Platform Core is priced on a per JVM or per core basis, which aligns the cost to the actual usage. The same 10,000 employee customer with the same modest Java estate typically pays Azul 150,000 to 400,000 dollars per year for equivalent coverage.

The secondary driver is the contractual posture. Azul does not impose an enterprise wide subscription. Azul does not have an audit team that monitors the customer's headcount. Azul does not bundle the runtime with broader Oracle product offerings that create cross product audit risk. The contractual model is materially simpler and less adversarial. Employee count negotiation covers the Oracle model in detail.

The technical equivalence and gap analysis

Azul Platform Core is built on the OpenJDK source, with the same Java SE specification compliance that Oracle Java carries. The runtime is functionally equivalent for the vast majority of Java applications. The compatibility is verified through the Java SE Technology Compatibility Kit, with Azul publishing the compliance results for each release.

The technical gaps that customers must analyse before migration are concentrated in three areas. First, Java Flight Recorder and Java Mission Control are available in both Oracle and Azul distributions, but the integration with Oracle Enterprise Manager is Oracle proprietary. Customers using Oracle Enterprise Manager for Java monitoring need to evaluate equivalent monitoring under the Azul distribution. Second, the Oracle proprietary garbage collectors, including the original Shenandoah variant, may differ from the Azul distribution. Most customers use the standard G1 or ZGC, which are common to both. Third, the security patch cadence differs slightly, with Oracle patching on a quarterly cycle and Azul patching on a monthly cycle. The Azul cadence is generally more favourable. Oracle Java covers the product detail.

The commercial model differences

The Azul Platform Core commercial model differs from Oracle Java in three substantive ways. First, the metric. Azul charges per JVM instance or per CPU core, depending on the deployment, with both options available to the customer based on the use pattern. The metric aligns the cost to the actual usage rather than to the employee count. Second, the contract term. Azul typically offers one year, two year, and three year contract options, with discounts at each multi year tier. The flexibility is greater than Oracle's standard three year commitment with no early termination. Third, the price stability. Azul publishes a transparent price list and offers a price hold across the contract term, with annual increases capped at a defined percentage. The standard Oracle Java SE Universal contract does not contain a price hold provision in its default form.

The combined commercial differences produce a Java cost that is typically 20 to 35 percent of the Oracle Java SE Universal equivalent. The savings are largest for customers with high employee count to JVM ratios, including financial services, retail, and healthcare. The savings are smallest for customers with low employee count to JVM ratios, including specialised technology firms where the Java footprint approaches the employee count. Java SE Universal covers the Oracle deal structure.

The migration timeline and Oracle co existence

The Java migration is technically simple but contractually delicate. The technical work involves replacing the Java runtime on the deployed estate, validating the application behaviour, and updating the operational tooling to recognise the Azul distribution. The work typically completes in 90 to 180 days for a medium complexity estate, with longer timelines for customers with heavily customised Java environments or with embedded Java in vendor applications.

The contractual delicacy is the Oracle co existence period. During the migration, both Oracle Java and Azul Platform Core are deployed in the estate, with the Oracle subscription still active for the un migrated portion. Oracle's audit position during this period is that the customer is using Oracle Java across the entire employee population, including the population that has migrated to Azul, until the Oracle subscription is formally terminated. The buyer side response is to time the Oracle subscription termination at the migration completion, not at the natural Oracle anniversary, and to negotiate a defined migration window in the final Oracle Java contract before the termination decision is made. Cloud migration advisory covers the related migration discipline.

The certification and support implications

The Java certification and support implications are limited but real. Some third party vendors certify their applications specifically on Oracle Java, with the certification not formally extended to Azul Platform Core or to other OpenJDK distributions. The most common examples are in the Oracle application ecosystem itself, including Oracle Enterprise Business Suite and Oracle PeopleSoft, where the Oracle Java runtime is the only formally certified option. The certification gap does not mean that Azul Platform Core fails to run the applications. It means that the vendor will not provide support for issues that arise on the alternative runtime.

The buyer side response is to map the third party application certifications before the migration, identify the applications that require Oracle Java for vendor support, and either retain Oracle Java for those specific applications under a scoped subscription or push the vendor to extend the certification to Azul Platform Core. Most major vendors have extended their certifications over the past two years as the Java SE Universal subscription has driven customer migration. Java compliance covers the related compliance dimension.

Pricing benchmarks for Azul Platform Core

The Azul Platform Core pricing benchmarks for a typical medium enterprise deployment range from 250 to 600 dollars per JVM per year, depending on the support tier, the contract term, and the deployment density. The benchmarks compare favourably to the Oracle Java SE Universal benchmarks of 100 to 200 dollars per employee per year, when the employee count substantially exceeds the JVM count. For a 10,000 employee customer with 500 JVMs, the Azul cost at 400 dollars per JVM is 200,000 dollars per year, compared to the Oracle cost at 150 dollars per employee of 1.5 million dollars per year. The difference is over 1 million dollars per year, with the savings exceeding the entire Azul commitment by a factor of seven.

The savings figure is the foundation of the business case for migration. The savings figure is also the foundation of the negotiation lever against Oracle, because Oracle understands that the credible alternative reduces the customer's willingness to accept Oracle's standard Java SE Universal terms. Pricing and discounts covers the related commercial dimension.

The Oracle exit risk and audit defence

The Oracle exit risk is the single largest concern for customers considering the Azul migration. Oracle Licence Management Services routinely audits customers who have notified Oracle of the intent to terminate the Java SE Universal subscription, with the audit framed as a verification that the customer has fully removed Oracle Java from the estate. The audit verification is technical, involving deployment scans of the customer's environment, and is exacting in the standard applied.

The buyer side response is to plan the audit defence before the migration begins, with a complete deployment inventory of Oracle Java in the starting estate, a removal log for each Oracle Java instance, and a verification scan that confirms the removal at the migration completion. The audit defence file is the customer's contractual defence against the post termination audit finding, and the file must be assembled during the migration, not after the audit notice arrives. Audit defense covers the broader response.

The buyer side framework for migration

The buyer side framework for a Java migration to Azul Platform Core reduces to five moves. First, run the business case with the actual employee count, the actual JVM count, and the realistic Azul pricing benchmarks. Second, map the third party application certifications and identify the residual Oracle Java requirement. Third, plan the migration timeline with the Oracle subscription termination aligned to the migration completion, not to the Oracle anniversary. Fourth, build the audit defence file during the migration. Fifth, negotiate a scoped Oracle Java subscription for the residual requirement, if any, at the lowest defensible employee count.

Executed with discipline, the migration delivers a Java cost reduction of 60 to 80 percent with no material loss in capability, support, or compliance. Executed without the framework, the migration produces an audit dispute that consumes the savings and damages the procurement team's credibility. For the full framework download The Java Negotiation Guide.