Oracle's per employee Java SE pricing model has pushed enterprise customers to revisit OpenJDK alternatives. Eclipse Temurin, Amazon Corretto, Azul, Red Hat OpenJDK, Microsoft Build, and BellSoft Liberica each carry distinct positioning. This article maps the comparison, the costs, the support boundaries, and the migration mechanics.
Oracle Java SE moved to a per employee subscription in January 2023. The metric counts the whole workforce, including finance staff, contractors, and outsourcer personnel who never open a JVM. For most enterprises that single change raised Java cost by three to five times.
Every credible alternative compiles from the same upstream source. OpenJDK is the reference implementation, and Oracle JDK, Eclipse Temurin, Amazon Corretto, Azul Zulu, BellSoft Liberica, and the Microsoft Build are all derived from it. The real question is which vendor you want holding the security backport calendar.
Read this alongside the Oracle knowledge hub, the Java pricing 2026 article, the employee based licensing article, the head to head Azul Zulu versus Oracle Java comparison, and the Vendor Shield subscription.
They are leaving because the price is no longer connected to how much Java they run. The Universal Subscription prices the organization, so an estate of 40 JVMs and an estate of 4,000 JVMs at the same company pay identically. That severs the link between consumption and cost.
Pick the build whose vendor already owns something else in your stack. That single rule resolves most of these decisions, because it puts the Java backport calendar inside a support relationship you already manage. Everything below is a refinement of it.
| Distribution | Vendor | Cost | Support | Best for |
|---|---|---|---|---|
| Eclipse Temurin | Eclipse Foundation | Free | Community, paid via partners | The neutral default; no vendor tie |
| Amazon Corretto | AWS | Free | Free, included with AWS support | AWS heavy estates |
| Azul Zulu | Azul | Free build, paid support | Commercial SLA, Java 6 upward | Legacy versions and audit grade support |
| Red Hat build of OpenJDK | Red Hat | Bundled with RHEL | Red Hat subscription support | RHEL estates and FIPS requirements |
| Microsoft Build of OpenJDK | Microsoft | Free | Free while on a supported release | Azure heavy estates |
| BellSoft Liberica | BellSoft | Free build, paid support | Tiered commercial | JavaFX, embedded, and small containers |
Temurin is the neutral reference. It is produced by the Eclipse Adoptium project, which runs the AQAvit quality suite on top of the Java SE compatibility tests. Choose it when you do not want the runtime tied to a cloud vendor.
The trade is that there is no vendor to escalate to at 2am. Adoptium publishes fixes on the quarterly cycle and nothing more. Several commercial vendors sell support contracts wrapped around Temurin binaries if you want the neutrality and the SLA together.
Corretto is free everywhere, not only on AWS, and that is the point most buyers miss. AWS commits to long term support releases with security and quality backports, and Corretto issues are handled through normal AWS support plans for customers who have one.
It ships x86 and ARM builds across Linux, Windows, macOS, and container images. For an estate already running on AWS, this is the lowest friction answer available.
Azul is the closest commercial analog to what Oracle sells. It covers versions Oracle has retired, including Java 6 and 7, which matters when a bank cannot decommission a 2011 application before 2028.
Zulu builds are free to download. What you buy is the support contract, the extended version coverage, and the stability commitment. The full head to head sits in the Azul versus Oracle comparison.
If you pay for Red Hat Enterprise Linux, you already own supported Java. The runtime is covered by the RHEL subscription, and Red Hat maintains the OpenJDK 8 and 11 update projects upstream, so the fixes originate in house rather than being consumed downstream.
Red Hat is also the practical answer when the estate must run in FIPS mode, because the JDK integrates with the system wide cryptographic policy. Rebuilding that behavior on another build is possible but rarely worth the effort.
Microsoft distributes its own OpenJDK build free for any use, with support included for customers on a supported Azure or Microsoft agreement. Microsoft runs very large Java estates internally, which is a reasonable proxy for how seriously the builds are tested.
The caution is version coverage. Microsoft supports a narrower set of releases than Azul or BellSoft, so estates with a long tail of Java 8 should confirm the roadmap before standardizing.
BellSoft publishes the widest build matrix in the ecosystem, including full JDK bundles that still contain JavaFX, standalone JRE packages, and Alpine musl builds for small containers. That combination solves two specific problems Oracle created.
Desktop Java teams need JavaFX back in the bundle. Platform teams need a JRE that is 40 megabytes rather than 300. Liberica is usually the fastest route to both.
White Paper · Oracle Java
The buyer side route out of the Java SE subscription. Read it free.
Yes, provided it is TCK certified, and every mainstream build listed above is. The Technology Compatibility Kit is the conformance suite that decides whether a binary may be called Java SE compatible, and access is granted through the OpenJDK community TCK licence. A build that passes it is not a clone. It is the specification, implemented and proven.
Your engineers already know the code runs. Certification matters because it is the sentence you put in front of an ISV support desk that wants to reject a ticket. It converts a debate about brands into a statement about a published conformance standard.
Oracle publishes recent long term support releases under the No Fee Terms and Conditions. Under that licence, production use of the covered release is free, including updates, until one year after the next long term support release ships.
That creates a real but temporary window. A team can run Oracle JDK 21 with no subscription today, then face a hard stop when the grant lapses and the release reverts to paid terms. Treat it as a bridge, never as a destination, and diary the expiry the day you adopt it.
It saves 70 to 92 percent of annual Java spend in the estates we have modeled, and the saving compounds because the subscription carries an annual uplift. The migration project is a one time cost measured in tens of thousands. The subscription is a recurring cost measured in millions.
| Scenario | Year 1 | Year 3 | Year 5 | 5 year total |
|---|---|---|---|---|
| Oracle Java SE per employee (8 percent uplift) | 4,450,000 | 5,188,160 | 6,049,432 | 26,103,000 |
| Eclipse Temurin free plus paid support on production | 240,000 | 254,628 | 270,148 | 1,273,000 |
| Amazon Corretto free in an AWS heavy estate | 0 | 0 | 0 | 0 |
| Saving versus Oracle (paid support scenario) | 4,210,000 | 4,933,532 | 5,779,284 | 24,830,000 |
Figures are modeled from the Redress Compliance engagement file and assume the counted population, not the badged headcount. Your own numbers will differ mainly on the contractor ratio, which is the single largest swing factor in the Oracle quote.
Straightforward on the same release line, and the hard parts are never the ones people expect. Moving Oracle JDK 17 to Temurin 17 is a binary swap for the overwhelming majority of server side applications. The failures cluster in a short and predictable list.
UnlockCommercialFeatures will refuse to start on a non Oracle build. It is a one line fix, but it fails at launch and it is everywhere in older run scripts.| Estate size | Elapsed time | What sets the pace |
|---|---|---|
| Under 200 JVMs, one platform team | 6 to 10 weeks | Image rebuild and one change window |
| 200 to 1,000 JVMs | 4 to 7 months | Application owner sign off, not engineering |
| 1,000 to 5,000 JVMs | 9 to 14 months | Release calendar and freeze periods |
| Over 5,000 JVMs or regulated | 12 to 20 months | Validation evidence and change advisory board |
| Desktop Java estate of any size | Add 3 to 6 months | Web Start, applets, and packaging |
It covers the runtime, and almost nothing else. That is a fair deal at the price, but buyers consistently assume they are buying a like for like replacement for an Oracle relationship, and they are not. Read the scope before you present the saving to a risk committee.
Expect contact, and prepare for it before you serve notice. Oracle's Java review teams work from download telemetry tied to corporate accounts and email domains, so the trigger is usually a download record rather than an installed agent. The defense is documentary and it has to be built in advance.
The detail of each trigger sits in the Java audit triggers article, which is worth reading before the notice letter goes out rather than after.
The standard reseller and Oracle account team position is that staying on the subscription is the safe choice because it avoids migration risk and audit exposure. We disagree. Across the estates we modeled in 2024 and 2025, the subscription was the most expensive answer in roughly seven of ten cases, and it did not remove audit risk, because Oracle reviews download history regardless of subscription status. The buyer side move is to sweep the estate first, move the bulk of workloads to a certified free build, and reserve paid support for the narrow set of applications that genuinely require it.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Work the sequence below in order. It takes a Java owner from an Oracle subscription to a defended estate inside twelve months, and it front loads the two steps that decide everything: the inventory and the ownership split.
Yes for the large majority of enterprise applications, because Oracle Java SE is itself built from OpenJDK. On the same release line the swap is effectively binary, and application code normally needs no change.
The differences that matter are packaging and licensing rather than language behavior. Validate desktop Java, reporting engines, and anything with a JVM agent during the pilot.
Eclipse Temurin is the safest neutral default, and Amazon Corretto is the safest default for an AWS estate. Both are TCK certified and both ship the quarterly security backports.
Choose Azul or BellSoft when you need versions upstream has retired, and Red Hat when the estate runs RHEL or requires FIPS mode. The vendor you already pay is usually the right answer.
Yes, but only for releases still covered by the No Fee Terms and Conditions, and only until that grant expires. Oracle publishes recent long term support releases under those terms, with free production use and free updates for a defined window.
The window closes one year after the following long term support release ships. Diary the date, because after it passes updates require a paid subscription.
Java Web Start applications break most often, followed by commercial startup flags that exist only in Oracle JDK 8. Both fail at launch rather than subtly, which at least makes them easy to find.
The quieter failures are fonts in PDF generation and monitoring agents pinned to a vendor version string. Test reporting output and check that dashboards still receive data after cutover.
Six to ten weeks for an estate under 200 JVMs, and nine to fourteen months for an estate of a few thousand. The variable is change governance, not engineering effort.
Plan backward from the contract anniversary so the termination notice lands inside the contractual window. Missing the notice date buys another full year of subscription.
Not economically, because the Universal Subscription prices the organization rather than the installs. Keeping ten Oracle JVMs costs the same as keeping ten thousand.
The exception is a stack where an Oracle product certification requires Oracle JDK. In that case, price the subscription as a cost of that product and decide whether the product itself still earns its place.
It helps but it does not settle the question on its own. A support contract proves what you run today. An Oracle review is usually about what was downloaded and installed historically.
The protection comes from the sealed inventory, the termination notice, and the closure of Oracle download channels. Keep the support contract as corroboration, not as the primary defense.
Redress runs Java alternatives advisory inside the Vendor Shield subscription, the Oracle services practice, and the Software Spend Assessment. The output is an inventory, a build recommendation, a migration plan, a five year cost model, and the evidence pack lodged before termination.
The work is led by senior Oracle commercial professionals on the buyer side, across pharma, banking, manufacturing, and public sector estates running 50 to 5,000 deployed instances.
Redress runs Java alternatives advisory inside the Vendor Shield subscription, the Oracle services practice, the Software Spend Assessment, and the Renewal Program.
Read the related Java pricing 2026 article, the employee based licensing facts, the Java audit triggers, the Oracle knowledge hub, the renewal and exit paper, the database licensing guide, the VirtualBox licensing article, the leverage assessment, the benchmarking page, the management team page, and the contact page.
The buyer side moves that keep your Oracle estate honest at renewal.
Independent. Buyer side. Built for Oracle customers running the next renewal cycle.
Open the white paper in your browser. Corporate email only.
Open the Paper →Java is open source. The Oracle Java SE subscription pays for Oracle's branded distribution and support, not for the Java language itself. The buyer that understands this distinction recovers 70 to 90 percent of the Java spend within 12 months.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Java, EBS, database, and ULA lessons from every Oracle engagement we run. Migration patterns, audit defense, distribution comparisons, and the moves that ended the Oracle Java subscription.