Azul versus Oracle Java, the runtime is settled and the contract is not
Azul Zulu and Oracle Java SE are both production grade JDK distributions built from the same upstream source, certified against the same compatibility kit: the runtime argument is close to settled. The contract, the counting metric, and the audit posture are where the two diverge, and that is where the money is.
Prepared by Redress Compliance · August 7, 2026 · Java advisory. Based on 30 to 40 Java estates benchmarked 2024 to 2025.
Executive summary
Azul prices what you run; Oracle prices who you employ. Azul Platform Core licenses per JVM or per core; the Oracle Universal Subscription counts every employee, contractor, and agent whether or not they touch Java, which is why the per employee subscription priced 2 to 5 times a per core support build on the same workloads. The metric breaks worst where Java is a minority workload, and again where contractor ratios run high: counted populations landed 20 to 30 percent above badged headcount in engineering firms, utilities, and public sector bodies.
Azul sells three things, and buyers routinely get quoted the wrong one. Zulu Builds are free and certified with no SLA; Platform Core is the commercial support subscription and the Oracle replacement in almost every case; Platform Prime is a performance runtime that solves latency problems, not licensing problems, and a Prime quote can land at several times the Core price for support you never scoped. Ask the quote to state the product line explicitly.
The migration is weeks and the parity is real. Technical migration to a certified OpenJDK build took 2 to 8 weeks per estate, not the quarters buyers feared, and support parity held in 9 of 10 estates, with the exception always an application vendor matrix and never the JVM. The carve outs decide the prize's size, not the decision's direction: WebLogic and most Oracle product stacks stay on Oracle Java, separated early.
The exit asymmetry is the durable leverage. Zulu is OpenJDK, so leaving Azul is a swap to Temurin at no fee; leaving Oracle is a termination plus a historic exposure review. That asymmetry protects the Azul renewal and disciplines the Azul terms, the per JVM container count and a growth band fixed before signature, because a per JVM metric on an autoscaling platform can multiply overnight. And an Azul quote moves Oracle's rate, never Oracle's metric: Oracle discounts, it does not redefine who counts.
The comparison, on the dimensions that carry money
| Dimension | Azul Zulu | Oracle Java SE | The buyer note |
|---|---|---|---|
| Pricing metric | Per JVM or per core | Per employee, contractors included | Only one tracks what you run |
| Certification | TCK certified | TCK certified | Runtime parity is not the argument |
| Free production option | Zulu Builds, no SLA | No Fee Terms, time limited | Diary the Oracle expiry date |
| Annual uplift | Negotiable: cap it in writing | Five to eight percent typical | Three year compounding decides the envelope |
| Growth event | More JVMs or cores | More people, acquisitions included | Oracle prices your acquisition; Azul does not |
| Exit cost | Swap to Temurin, no fee | Termination plus historic exposure review | The asymmetry is the leverage |
| Oracle product stacks | Not certified for WebLogic | Required | Carve out before modeling |
The three Azul products, and the one to price
- Zulu Builds of OpenJDK: free, certified, downloadable, no SLA. Reasonable for development, test, and workloads nobody pages you about at 3am.
- Azul Platform Core: the commercial support subscription and the Oracle Java SE replacement in almost every case. This is the product to price.
- Azul Platform Prime: a performance runtime, the Falcon compiler, the pauseless collector, warmup acceleration, solving latency problems rather than licensing ones, at several times the Core price.
Version coverage is part of the argument: Azul tracks the long term support lines on the same quarterly security cadence Oracle publishes, and supports Java 6 and 7 commercially, which for an estate carrying a 2011 application that cannot retire before 2028 is the whole case. Production scale is not the risk, Azul has shipped certified builds for over a decade with public references in banking and trading; the risk sits in application vendor matrices and operational assumptions, validated in that order, because that is the order in which projects actually fail.
The Java renewal and exit brief
The Oracle to Azul comparison inside the full option set: the subscription math, the migration patterns, the carve outs, and the contract terms on both sides.
Get the white paper →The Azul contract, negotiated before it is signed
The Azul terms deserve the same discipline as the Oracle exit: the counting basis for containers fixed before signature, because a per JVM metric applied to an autoscaling platform multiplies overnight; a growth band rather than an open meter; the annual uplift capped in writing, since it is negotiable in a way Oracle's is not; and the scope drawn around the workloads that carry external obligations rather than the whole estate. Compliance runs on a self declared count with a contractual verification right, a different order of magnitude of effort from Oracle's formal review of installs and downloads, and the fallback that disciplines every Azul renewal is Temurin, free, certified, and a swap away. The wider distribution field, Corretto and Temurin included, is compared in the OpenJDK alternatives comparison, and the full six option frame in the Java options guide.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Java estates, 2024 to 2025
Across roughly 30 to 40 Java estates Fredrik Filipsson benchmarked between 2024 and 2025, the move from Oracle Java to a supported build was rarely a technical decision:
The Oracle per employee price against a per core support build on identical workloads.
In the 1 of 10 estates without support parity, the cause was an application vendor's certification, never the JVM.
The honest presentation to a risk committee fits on one slide: runtime parity is certified, the give ups are ecosystem level, Oracle product certification and the single vendor relationship, and the carve outs, WebLogic and the Oracle stacks, stay behind on Oracle Java without changing the decision for everything else. What the Azul quote does to the Oracle negotiation is equally honest: it moves the rate, sometimes materially, and it never moves the metric, because Oracle discounts numbers and defends definitions. The audit posture that shadows the whole comparison sits in the Java audit defence sequence and the audit triggers analysis.
Your first five moves
- Price Platform Core, explicitly, and send back any Prime quote you did not scope, because the product line decides the number.
- Carve out the Oracle product stacks first, WebLogic and friends, so the model prices the movable estate honestly.
- Fix the container counting basis and growth band in the Azul order before signature, because autoscaling multiplies per JVM counts overnight.
- Cap the Azul uplift in writing and keep the Temurin fallback documented, the asymmetry that disciplines every renewal.
- Validate vendor matrices before runtimes, in that order, because that is the order projects fail in. The Java calculator and the Oracle practice run the comparison with you.
Frequently asked questions
Is Azul Zulu as good as Oracle Java?
At the runtime level, yes: both are production grade JDK distributions built from the same OpenJDK source and certified against the same Java SE Technology Compatibility Kit, on the same quarterly security cadence. The differences that carry money are commercial, the pricing metric, the audit posture, the uplift, and the exit cost, not technical.
How do Azul and Oracle Java pricing differ?
Azul Platform Core licenses per JVM or per core, tracking what you run; the Oracle Universal Subscription counts every employee, contractor, and agent regardless of Java use. On the same workloads the Oracle model priced 2 to 5 times the per core build, with the gap widest where Java is a minority workload or contractor ratios run high.
What is the difference between Zulu Builds, Platform Core, and Platform Prime?
Zulu Builds are free certified OpenJDK with no SLA, fit for development and unpaged workloads. Platform Core is the commercial support subscription and the Oracle replacement to price in almost every case. Platform Prime is a performance runtime solving latency problems at several times the Core price, and quotes should state the product line explicitly.
How long does migrating from Oracle Java to Zulu take?
Two to eight weeks per estate in our benchmarks, not the quarters buyers feared, with support parity holding in 9 of 10 estates. The failures were application vendor certification matrices, never the JVM, which is why vendor matrices validate before runtimes, and why WebLogic and the Oracle product stacks carve out early and stay on Oracle Java.
What should be negotiated in an Azul contract?
The container counting basis and a growth band before signature, because a per JVM metric on an autoscaling platform multiplies overnight; a written uplift cap, which Azul concedes and Oracle does not; and scope drawn to the workloads carrying external obligations. The Temurin fallback, a free certified swap, is the leverage that disciplines every Azul renewal.
Does an Azul quote reduce Oracle's price?
It moves the rate and not the metric: Oracle discounts the per employee number against a credible alternative, sometimes materially, but almost never redefines who counts as an employee. The quote is worth tabling for the rate movement alone, and the full escape from the metric requires the migration, not the negotiation.
