The Java alternatives, same source, same tests, a different bill
Oracle Java SE moved to a per employee subscription in January 2023, counting the whole workforce including finance staff and contractors who never open a JVM, raising Java cost three to five times for most enterprises. Every credible alternative compiles from the same upstream OpenJDK source, and the real question is not compatibility, it is which vendor you want holding the security backport calendar.
Prepared by Redress Compliance · August 8, 2026 · Oracle advisory. Based on 35 to 45 Oracle Java engagements worked 2024 to 2025.
Executive summary
The certification, not the brand, is what an ISV support desk can be held to.
All six mainstream builds, Eclipse Temurin, Amazon Corretto, Azul Zulu, Red Hat's build, the Microsoft Build, and BellSoft Liberica, pass the Java SE Technology Compatibility Kit, the same certification Oracle JDK carries, and the free builds are not unsupported builds: Corretto, Temurin, Liberica.
And the Microsoft Build all ship the quarterly critical patch backports, usually inside 72 hours of the Oracle release.
The selection rule that resolves most decisions: pick the build whose vendor already owns something else in your stack.
The cost cut ran 70 to 92 percent, and the worked example is stark.
A manufacturer with 25,000 badged employees ran Java in about 800 instances at roughly $850,000 a year on the legacy processor metric.
The per employee count reached near 55,000 once contractors and outsourcer staff were included, and the quote came back at $4.45 million, while the same estate on a free certified build with paid support on production only modeled at $240,000.
The subscription prices the organization, not the usage, 40 JVMs and 4,000 JVMs at the same company pay identically, and growth is priced automatically at every true up.
The JVM is almost never what breaks, and compatibility held in nine of ten cases.
Applications ran unchanged on the same long term support line in roughly nine of ten migrations, and roughly nine in ten failures traced to startup flags, fonts, Java Web Start, or a monitoring agent, not application bytecode, with the exceptions clustering in desktop Java, reporting engines.
And vendor packaged stacks.
The duration scales with change windows, not code: a 200 JVM estate closes in 6 to 10 weeks, a 5,000 JVM regulated estate runs 12 to 20 months, and full cutover at large enterprises ran nine to fourteen months, gated by release governance rather than engineering.
Two boundaries catch buyers who move too fast.
Some JVMs cannot legally move: Oracle product stacks, WebLogic, Enterprise Manager, and the packaged applications, are certified on Oracle JDK, and moving them to Temurin loses Oracle product support, not just Java support, so those JVMs stay and everything else goes.
And a paid non Oracle contract covers the runtime only, never your ISV certifications, your third party library CVEs, or Oracle product support: the NFTC grant meanwhile keeps Oracle JDK 21 free until one year after the next LTS ships, then reverts to paid terms.
A saving and a cliff most buyers never read.
The six builds, compared
| Distribution | Vendor | Cost | Best for |
|---|---|---|---|
| Eclipse Temurin | Eclipse Foundation | Free, paid support via partners | The neutral default, no vendor tie |
| Amazon Corretto | AWS | Free, support included with AWS plans | AWS heavy estates |
| Azul Zulu | Azul | Free build, paid support contract | Legacy versions and audit grade support |
| Red Hat build of OpenJDK | Red Hat | Bundled with RHEL | RHEL estates and FIPS requirements |
| Microsoft Build of OpenJDK | Microsoft | Free on supported releases | Azure heavy estates |
| BellSoft Liberica | BellSoft | Free build, tiered commercial | JavaFX, embedded, and small containers |
One rule resolves most selections: pick the vendor already in your stack.
It puts the Java backport calendar inside a support relationship you already manage, Corretto for AWS estates, the Microsoft Build for Azure, Red Hat's build where RHEL runs.
And Temurin as the neutral default when no tie exists, with commercial support wrapped around it where a 2am escalation path is required.
Azul is the closest commercial analog to Oracle's own offering, covering retired versions back to Java 6 and 7, which matters when a 2011 application cannot decommission before 2028.
What actually breaks, and what legally cannot move
- The failure census: nine in ten migration failures traced to startup flags, fonts, Java Web Start, or monitoring agents, configuration artifacts fixed in hours, not application bytecode.
- The exception clusters: desktop Java, reporting engines, and vendor packaged stacks, the ten percent that needs real testing before the wave plan commits it.
- The JVMs that stay: WebLogic, Oracle Enterprise Manager, and Oracle packaged applications are certified on Oracle JDK, and moving them loses Oracle product support, not just Java support.
- The scope of a paid non Oracle contract: the runtime only, never ISV certifications, third party library CVEs, or Oracle product support, an assumption buyers make routinely and wrongly.
- The NFTC cliff: Oracle JDK 21 stays free until one year after the next LTS ships, then reverts to paid terms, a grant worth using and a date worth diarizing.
The Java SE renewal exit brief
The build selection method, the wave plan, the Oracle stack boundary, and the audit safe exit sequence worked end to end.
Get the white paper →The cost math, priced on the organization
The Universal Subscription severed the link between consumption and cost: the metric captures full time, part time, and temporary staff, agents, contractors, and outsourcer personnel supporting internal operations.
The rate starts near $15 per employee per month at the smallest tier and steps down by band without reaching zero, and acquisitions, insourcing, and outsourcing model changes all raise the counted population at the next true up without a single new Java install.
That is why the migration question surfaced in nearly every engagement and why the subscription rarely survived a clean cost model once a certified free build was on the table.
The tier arithmetic and worked bands run in the employee tier pricing analysis, the audit defense for the exit period in the Java audit defense guide, and the head to head on the commercial analog in the Azul Zulu comparison.
- 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 engagements, 2024 to 2025
Across roughly 35 to 45 Oracle Java engagements Fredrik Filipsson worked through in 2024 and 2025, the migration question surfaced in nearly every one:
Annual Java cost on a free certified build, net of the one time migration project.
Gated by release governance and pipeline discipline, not by code change.
The duration finding reframes the project: a 200 JVM estate closes in 6 to 10 weeks while a 5,000 JVM regulated estate runs 12 to 20 months on the same technical work, because the binding constraint is change windows and release governance.
Not engineering, which means the migration is scheduled like an operating system patch cycle, not a development program.
The boundary discipline completes it: the Oracle certified JVMs inventoried and excluded on day one, the NFTC estate documented with its expiry date.
And the remaining population waved by change window, with the audit posture maintained throughout, because the exit period is precisely when the Java outreach letters arrive.
Your first five moves
- Inventory the JVMs that legally cannot move, the WebLogic and Oracle product runtimes whose migration loses product support.
- Pick the build by existing vendor relationship, the one rule that resolves most selections.
- Model the free build against your employee count, where the cuts ran 70 to 92 percent net of the project.
- Wave the migration by change window, not code risk, since nine of ten failures are configuration, not bytecode.
- Diarize the NFTC expiry and keep the audit posture through the exit period. The Oracle practice runs the migration with you.
Frequently asked questions
Are OpenJDK builds really equivalent to Oracle Java?
The six mainstream builds, Temurin, Corretto, Zulu, Red Hat's build, the Microsoft Build, and Liberica, all compile from the same upstream OpenJDK source and pass the same Java SE Technology Compatibility Kit that Oracle JDK does.
Certification, not brand, is what an ISV support desk can be held to, and applications ran unchanged on the same LTS line in nine of ten migrations we reviewed.
How much does leaving Oracle Java save?
70 to 92 percent of annual Java cost across the estates we modeled, net of the one time migration project.
The worked example: 25,000 badged employees, priced near 55,000 once contractors counted, quoted at $4.45 million per year on the employee metric against $240,000 on a free certified build with paid support on production only, for the same 800 deployed instances.
Which OpenJDK build should we choose?
The one whose vendor already owns something in your stack: Corretto for AWS estates with support through existing AWS plans, the Microsoft Build for Azure, Red Hat's build on RHEL with FIPS, Temurin as the neutral default with commercial support wrapped where an SLA is needed.
And Azul Zulu where retired versions like Java 6 and 7 must stay supported.
The rule puts the backport calendar inside a relationship you already manage.
What breaks in a Java migration?
Almost never the application: roughly nine in ten failures traced to startup flags, fonts, Java Web Start, or monitoring agents, configuration artifacts rather than bytecode, with the real exceptions clustering in desktop Java, reporting engines, and vendor packaged stacks.
Duration scales with change windows, not code, 6 to 10 weeks for a 200 JVM estate, 12 to 20 months for a 5,000 JVM regulated one.
Which JVMs cannot move off Oracle JDK?
The ones inside Oracle product stacks: WebLogic, Oracle Enterprise Manager, and Oracle packaged applications are certified on Oracle JDK, and moving them to another build loses Oracle product support, not just Java support.
Those JVMs are inventoried and excluded on day one, they remain covered by the products' own licenses, and everything else migrates around them.
Is Oracle JDK still free for anyone?
Under the No Fee Terms and Conditions, Oracle JDK 21 remains free until one year after the next long term support release ships, at which point the grant reverts to paid terms.
The NFTC is both a saving and a cliff: worth using deliberately with the expiry diarized, and dangerous as an unread default, because the estate that never noticed the license will not notice the reversion either.
How to Negotiate the Oracle Java Employee Agreement: Honest Leverage in a Captive Deal
Priced per employee, every employee, from $15 down to $5.25. At renewal your leverage is thin and OpenJDK threats rarely land. The one-year runway, trading through the wider Oracle relationship, and containing what you sign.
