The six Java options, and the two that need no migration
Most Java advice starts by asking which OpenJDK build to download, and that is the fourth question. The first is which of six destinations your estate is actually heading for, and two of them involve no runtime change at all: the cheapest routes out of an Oracle Java problem are frequently contractual rather than technical, and a team that starts by evaluating builds never finds them.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 30 to 45 Java option reviews run 2024 to 2025.
Executive summary
Six destinations, and the frame is usually too narrow. Pay Oracle, run Oracle free on the No Fee Terms clock, use rights you already hold, run a free non Oracle build, buy a supported non Oracle build, or remove Java from the workload.
Buyers arrived having framed the question as Oracle versus Temurin, having priced neither of the two options that involve no runtime change, and the option set was almost always too narrow at the start.
One option does not exist, and it is the most assumed. Unlike Oracle Database, you cannot buy third party support and keep running the Oracle binary: the binary is licensed by Oracle, no supplier can grant the right to run it, and every non Oracle support contract supports a non Oracle build.
On Database you change supplier and keep the software; on Java you change the software or keep paying Oracle. There is no third door.
One estate in five is already partly covered.
Java rights arrive inside other agreements: restricted use rights in Oracle middleware and applications entitlements, pre 2023 perpetual Named User Plus and Processor licenses still valid for what they cover, vendor supplied runtimes licensed under the vendor's own agreement.
And cloud platform services with a supported JDK inside. Paying a Java subscription for machines already covered is a live overspend we find regularly, and the embedded terms are the ones Oracle reads most narrowly: confirm scope in writing.
The estate sweep changes the plan before the plan starts. Sweeps found Oracle binaries on 15 to 35 percent of servers the buyer believed were already clear, and where paid support was bought, it was scoped to the whole estate rather than the workloads carrying an external obligation.
Support is a scope decision, not a safety blanket: the contract covers the runtime, never your application vendor's certification matrix or dependency tree.
The six destinations, and what each really is
| Option | What it is | The obligation it carries |
|---|---|---|
| Oracle, paid | The Java SE Universal Subscription on total counted employees | Annual renewal, headcount reconciliation, notice discipline |
| Oracle, free | Oracle JDK under the No Fee Terms, zero cost inside the window | A whole estate upgrade at every window close, on Oracle's calendar |
| Rights already held | Java inside middleware, applications, OEM, or cloud entitlements | Prove the scope in writing, and stay inside it |
| Free non Oracle build | A community OpenJDK build, self supported | You own patch currency and escalation |
| Supported non Oracle build | A commercial distribution with an SLA, priced per core, server, or desktop | A supplier relationship, scoped to real need |
| Remove Java | Retire, replace, or move the workload to a managed platform | A retirement plan somebody actually owns |
The free Oracle route is a treadmill, not a destination.
The No Fee Terms genuinely permit free production use of an Oracle JDK long term support release, for a bounded window, and the obligation is the price: the whole estate moves to the next LTS release inside each window, on Oracle's calendar rather than yours.
An estate whose change governance cannot absorb that cadence is not on the free option; it is on a delay timer to the paid one.
Routing by estate shape, not by preference
| If your estate looks like this | Start with | And rule out |
|---|---|---|
| Large workforce, modest Java footprint | A free or supported non Oracle build | Oracle paid, at any discount: the employee metric punishes the shape |
| Small workforce, dense Java platform | Oracle paid, priced honestly against option five | Assuming migration always wins |
| Java mostly inside Oracle products | The rights you already hold | Swapping the runtime under a certified product |
| Regulated, external SLA obligations | A supported build, scoped narrowly to those workloads | Free and self supported across the whole estate |
| A handful of retiring legacy applications | Removing Java | A migration program you will never finish |
| Strong platform team, aggressive refresh | A free non Oracle build | Paying for support you will not call |
The Java renewal and exit brief
The six options priced against each other: the subscription math, the NFTC cadence, the entitlement audit, and the migration patterns cost modeled.
Get the white paper →The rights you already hold, checked in four places
Before pricing anything, check what is already paid for. Oracle middleware and applications entitlements carry restricted use Java rights for the servers running those products.
Pre 2023 perpetual Named User Plus and Processor Java licenses remain valid for what they cover, unexpandable but not abandonable. Application vendors who ship and support the runtime inside their product generally carry its licensing under their own agreement, confirmed in writing.
And managed cloud runtimes frequently include a supported JDK inside the service, taking those workloads out of scope entirely.
Where options four and five do apply, every mainstream build shares the OpenJDK codebase under GPL with the Classpath Exception, and the build selection, Corretto, Temurin, or Zulu, is a separate later decision, with the commercial tier compared in the Azul versus Oracle analysis.
- 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 option reviews, 2024 to 2025
Across roughly 30 to 45 Oracle Java engagements Fredrik Filipsson ran or reviewed in 2024 and 2025, the option set on the table at the start was almost always too narrow:
The no change routes, existing rights and the honest Oracle comparison, absent from the initial frame.
Servers believed clear where Oracle binaries turned up, resetting the option set before the plan.
Two findings organize the rest.
Staying and paying is sometimes the honest answer, when counted headcount is small relative to the Java footprint or the applications carrying Java are Oracle products under an Oracle certification matrix, both more common in software and engineering businesses than the general advice suggests.
And where support is bought, it scopes to the workloads carrying external obligations rather than the whole estate, because a non Oracle contract covers the runtime and nothing above it.
The migration economics themselves, three patterns cost modeled, sit in the migration patterns analysis, the decision gate in the migration decision guide, and the audit shadow over every option in the Java audit guide.
Your first five moves
- Sweep the estate before choosing anything, vendor string per host, because 15 to 35 percent of clear servers were not.
- Audit the rights you already hold: middleware entitlements, pre 2023 perpetuals, vendor runtimes, and cloud services, in writing.
- Route by estate shape, the employee to JVM ratio, the certification matrices, and the upgrade capacity, not by preference.
- Scope any support purchase to the obligated workloads, never the whole estate, because the contract covers the runtime alone.
- Price the honest Oracle comparison where the shape favors it, against written terms rather than a verbal rate. The Java calculator and the Oracle practice run the options with you.
Frequently asked questions
What are the alternatives to Oracle Java?
Six destinations, not two: pay Oracle, run Oracle free under the No Fee Terms, use Java rights already held inside other agreements, run a free community OpenJDK build, buy a supported non Oracle distribution, or remove Java from the workload.
Only three involve changing a runtime, and the two contractual routes are the ones most buyers never price.
Can you buy third party support for Oracle Java?
No, and it is the most common false assumption in the market: unlike Oracle Database, no supplier can grant the right to run the Oracle binary, so every non Oracle support contract supports a non Oracle build.
Leaving Oracle support means changing the binary first; there is no equivalent of keeping the software and switching the maintenance.
Is OpenJDK really free for production use?
Yes: every mainstream build, Temurin, Corretto, Zulu, and others, comes from the OpenJDK project under GPL version 2 with the Classpath Exception, which permits free production use.
The free option's real cost is operational, you own patch currency and escalation, and the build choice is a separate decision after the destination is set.
Might we already have Java rights without knowing?
Roughly one estate in five is already partly covered: restricted use rights inside Oracle middleware and applications entitlements, pre 2023 perpetual licenses still valid for their scope, vendor supplied runtimes carried under the vendor's agreement, and cloud managed services with a JDK inside.
Confirm scope in writing, because the embedded terms are the ones Oracle reads most narrowly.
Is Oracle's free Java option viable long term?
As a treadmill, not a destination: the No Fee Terms genuinely permit free production use of an LTS release for a bounded window, and the price is a whole estate upgrade inside every window on Oracle's calendar.
Estates whose change governance can absorb that cadence save the subscription; estates that cannot are on a delay timer to paying.
When is staying on paid Oracle Java the right answer?
When counted headcount is small relative to the Java footprint, since the employee metric prices people rather than JVMs, or when the Java carrying applications are Oracle products under an Oracle certification matrix.
Both are real and more common in software and engineering businesses than the standard advice allows, priced against written subscription terms rather than a verbal rate.
