The Oracle JRE, free until one version string says otherwise
The Oracle JRE is not free for business use in 2026, and the only Oracle product that covers it is the per employee subscription, which bills your headcount rather than your install count. The version string decides everything: 8u202 and earlier are free for commercial use, 8u211 and later are not, and the auto updater crossed that line for millions of desktops without a change request.
Prepared by Redress Compliance · August 6, 2026 · Oracle Java advisory. Based on 35 to 45 Java engagements run 2024 to 2026.
Executive summary
The line is a version string.
Oracle stopped publishing a separate JRE after Java 8, so an Oracle JRE in your estate is almost certainly a Java 8 build, and the update number decides the obligation: 8u202 and earlier are free for commercial use.
8u211 and later carry the Oracle Technology Network license, free for personal use, chargeable for business, same installer.
The auto updater crossed the line for you. The Windows Java updater moved millions of desktops past 8u202 without a change request, converting free estates into licensable ones one silent update at a time.
In our engagements, 6 to 8 of every 10 estates still believed the JRE was free for business use under an assumption formed before 2019.
The bill scales with employees, not installs. The per employee Java SE Universal Subscription is the only Oracle product covering the runtime, so a 3,000 employee company running the JRE on 400 desktops pays $378,000 a year at list, $945 per JRE desktop.
The arithmetic is the argument for removal: few runtimes on few machines pricing the entire workforce.
The hidden installs decide audits. Private JREs bundled inside third party desktop applications are the most commonly missed exposure, absent from the installed programs list, and in our engagements legacy Oracle JRE installs sat on 15 to 35 percent of devices the buyer assumed were clean.
A jlink built runtime from an Oracle JDK is still Oracle Java; the tool does not change the license on the bits. The exit is real: a supported OpenJDK build removes the exposure in weeks once the tooling is fixed.
The version line, and how estates crossed it
| What you find | The license position | The note |
|---|---|---|
| Oracle JRE 8u202 or earlier | Free for commercial use under the old BCL terms | Frozen in 2019: no security patches, which is its own argument for replacement |
| Oracle JRE 8u211 or later | OTN license: personal use free, business use chargeable | The auto updater's destination, and the audit's favorite finding |
| Bundled private JREs in third party apps | The vendor's license or yours, per the bundle terms | Invisible in installed programs, present on 15 to 35 percent of assumed clean devices |
| jlink runtime images from an Oracle JDK | Still Oracle Java, still licensable | The build tool does not change the license on the bits it packages |
The updater was the compliance event. No procurement decision, no deployment project, no change request: the Windows auto updater carried estates across the 8u211 line automatically, which is why the belief that nothing changed is both universal and wrong.
The version string inventory, not the purchasing history, is the truth.
The employee metric math, why small estates price big
The subscription that covers a chargeable JRE is the same per employee Java SE Universal Subscription that covers everything else, counting every employee and supporting contractor regardless of who touches Java.
The worked example is the whole argument: 3,000 employees at the $10.50 band is $378,000 a year at list, for 400 desktops running a runtime, $945 per desktop, for software whose open source equivalent is free.
That ratio is why JRE findings punch above their weight in audits: a residual runtime estate nobody valued prices the entire workforce, and the retroactive layer reaches back across the years since the updater crossed the line.
The full rate bands sit in the cost analysis, and the license calculator prices your own headcount in minutes.
The Java SE employee licensing analysis
The metric's full construction: who counts, the rate bands, the JRE and JDK scope questions, and the negotiation positions that bound the employee definition.
Get the white paper →The hidden estate, bundled JREs and built runtimes
The installs that decide audits are the ones inventory tools miss by default.
Third party desktop applications ship private JREs inside their own directories, absent from the installed programs list and invisible to registry based discovery; finding them takes filesystem level scanning for the runtime's actual binaries.
Whether the application vendor's license covers that bundled copy is a per vendor question with a documented answer, and assuming coverage is how 15 to 35 percent of assumed clean devices turned out otherwise.
The modern variant is the built runtime: jlink images assembled from an Oracle JDK carry Oracle Java inside whatever they ship with, and the packaging step changes nothing about the license.
Legacy Java Web Start estates face the same reckoning from the other direction, the technology left the Oracle JDK at 11, and pinned JNLP applications have a supported open source route out rather than a reason to keep paying. The scanning method sits in the shadow install 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 engagements, 2024 to 2026
Across roughly 35 to 45 Oracle Java engagements Fredrik Filipsson ran between 2024 and 2026, JRE confusion was a recurring root cause of exposure rather than a footnote to it:
Teams still operating on the pre 2019 assumption that the JRE was free for business use, updater history unexamined.
Legacy and bundled Oracle JRE installs on machines the buyer's inventory had already cleared.
The resolution pattern was consistent and fast: replacing the runtime with a supported OpenJDK build removed the exposure in weeks once the tooling was fixed, and the removal, priced and scheduled, became the negotiation leverage the audit defense sequence runs on.
The OpenJDK comparison maps the replacement builds and their support paths.
Your first five moves
- Inventory by version string, at the filesystem level: every Oracle JRE, its update number against the 8u202 line, bundled and private copies included.
- Freeze the auto updater wherever a pre 8u211 estate legitimately persists, and document the freeze date.
- Resolve the bundle question per vendor: which third party applications ship Oracle JREs, and whose license covers each, in writing.
- Run the employee math on the residual estate, because $945 per desktop is the business case for removal written in Oracle's own arithmetic.
- Replace and retire on a schedule: supported OpenJDK builds for what stays, decommission records for what goes, per the audit defense guide. The Java defense service runs the estate with you.
Frequently asked questions
Is the Oracle JRE free for business use?
Not since Java 8u211. Oracle JRE 8u202 and earlier remain free for commercial use under the old terms; 8u211 and later carry the OTN license, free for personal use and chargeable for business, from the same installer.
The version string on each install, not the original download decision, decides the obligation.
How did our JRE estate become licensable without any purchase?
The Windows Java auto updater moved desktops past the 8u202 line automatically, converting free installs into OTN licensed ones with no change request.
Six to 8 of every 10 estates in our engagements still assumed the pre 2019 position, which is why the updater history and version inventory are where every Java review starts.
What does licensing the Oracle JRE actually cost?
The per employee Java SE Universal Subscription is the only Oracle product covering the runtime, and it prices headcount, not installs: a 3,000 employee company with the JRE on 400 desktops pays $378,000 a year at list, $945 per desktop.
The arithmetic is usually the business case for removal rather than subscription.
Do JREs bundled inside third party applications count?
They are the most commonly missed installs: private JREs ship inside application directories, invisible to the installed programs list, and sat on 15 to 35 percent of devices buyers assumed clean.
Whether the application vendor's license covers the bundled copy is a per vendor question that needs a documented answer, not an assumption.
Are jlink runtime images from an Oracle JDK licensable?
Yes. A runtime image built with jlink from an Oracle JDK is still Oracle Java, and the packaging step does not change the license on the bits. Teams shipping built runtimes inside internal tools have distributed Oracle Java wherever those tools run, which is exactly how invisible estates assemble.
What happened to Java Web Start, and what replaces it?
Oracle removed Web Start from JDK 11, leaving legacy JNLP applications pinned to Oracle JRE 8. The supported route out is open source, OpenWebStart with a supported OpenJDK build, which removes both the pinned dependency and the license exposure.
In our engagements the replacement took weeks once the tooling was fixed.
