Contents
Key takeawaysIs the JRE free?How the updater changed itWhat it costsHidden JREsChecking your own installsWhat Oracle will sayWhat we have seenWhat to do nextFAQOracle JRE 8u202 and earlier are free for commercial use; 8u211 and later need the Java SE Universal Subscription for business use, which charges for every employee rather than every device running the runtime.
- The version string decides. Oracle JRE 8u202 and earlier stay free for commercial use, while 8u211 and later fall under the OTN license, which charges for business use.
- The updater made the change. Java Update offered post April 2019 builds from the system tray, so desktops became licensable one accepted prompt at a time, with no purchase on record.
- Headcount sets the price. A 3,000 employee company with the JRE on 400 desktops pays $378,000 a year at list for the Universal Subscription.
- Some uses are still covered. Personal use, development use and running listed Oracle products such as E-Business Suite or Forms need no Java subscription.
- Hidden runtimes decide audits. Bundled private JREs and jlink images built from an Oracle JDK are Oracle Java, and inventory tools usually miss them.
- Removal is usually cheaper. Replacing the runtime with a supported OpenJDK build removed the exposure within weeks in our engagements once tooling was fixed.
Is the Oracle JRE free for business use in 2026?
Only if the build is Java 8 Update 202 or earlier. Those builds shipped under the old Binary Code License (BCL), which allowed commercial use at no cost. From 8u211 onward, the JRE ships under the Oracle Technology Network (OTN) License Agreement for Oracle Java SE, and ordinary business use needs a paid subscription.
The installer looks the same either side of that line. The update number in the version string sets the obligation, so the question for every install is which build it is, whatever the reason someone downloaded it.
| What you find | License position | What to watch |
|---|---|---|
| Oracle JRE 8u202 or earlier | Free for commercial use under the old BCL terms | Frozen since 2019 with no security patches, which is a reason to replace it in its own right |
| Oracle JRE 8u211 or later | OTN license: personal use free, business use chargeable | Where the auto updater took most desktops, and the most common audit finding |
| Oracle JRE 8u211 or later used only to run Oracle E-Business Suite, Oracle Forms or another listed Oracle product | Covered by Oracle Approved Product Use under the OTN terms | Covers that use only; any other Java application on the same device brings it back into scope |
| Private JREs bundled inside third party applications | The application vendor's license or yours, depending on the bundle terms | Missing from the installed programs list, and the installs buyers miss most often |
| jlink runtime images built from an Oracle JDK | Oracle Java under whatever license covered that JDK build | The build tool does not change the license on the binaries it packages |
What the OTN license still allows without payment
Oracle lists four permitted uses under the OTN terms. Anything outside them needs a separate license.
- Personal Use. An individual running personal applications on a desktop or laptop under their own control. Running a line of business application at work does not qualify.
- Development Use. Your internal use to develop, test, prototype and demonstrate your own applications. Production use of those applications is not included.
- Oracle Approved Product Use. Running products on Oracle's Schedule A (for example Oracle SQL Developer) or Schedule B (for example Oracle E-Business Suite, Oracle Forms, JD Edwards and WebLogic Server client applications), which you must license separately.
- Oracle Cloud Infrastructure Use. Running Java on OCI services that Oracle identifies in the license.
Why almost every Oracle JRE you find is a Java 8 build
Oracle stopped offering a standalone JRE for general use after Java 8. The short lived Java 9 and 10 releases had JRE downloads, but from Java 11 Oracle ships only the JDK. An Oracle JRE on a corporate desktop is therefore almost always a Java 8 build.
How to Negotiate the Oracle Java Employee Agreement: Honest Leverage in a Captive Deal
How did free JRE installs become licensable without a purchase?
Through the Java auto updater. Java 8 on Windows installs a scheduler, jusched.exe, and a checker, jucheck.exe, that look for new builds at user login and offer them from the system tray. One click by the user installs the update.
Oracle's license change applied to releases from April 16, 2019. Every desktop where a user accepted a tray prompt after that date moved from BCL terms to OTN terms, without a procurement decision, a deployment project or a change request.
Teams that say nothing changed are right about their purchasing and deployment records. The change happened on each device, one accepted update at a time, and only a version inventory shows where.
Why purchasing records cannot tell you where you stand
A software asset team that looks for Java purchases or approved deployments will find none, and conclude there is nothing to license. Oracle does not start from your purchase records. It starts from the versions it believes you run, and from its own download data for your corporate domains.
Oracle's download records can tie Java updates fetched from its sites to your corporate network, which we cover in how Oracle uses download log evidence. Your answer to that data is your own inventory of version strings, device by device.
Java SE employee licensing analysis
The metric, who counts, the rate bands and the JRE and JDK scope questions in one guide.
Get the white paper →What does an Oracle JRE license cost?
The cost is set by your employee count, not by how many devices run the JRE. The subscription that covers a chargeable JRE is the same per employee Java SE Universal Subscription that covers every other Oracle Java use, and it prices your whole workforce.
Oracle's price list sets a monthly rate per employee by band, and the band rate applies to the full count. The rates run from $15 at the smallest band down to $5.25 at 40,000 to 49,999 employees.
| Employees counted | Monthly list price per employee |
|---|---|
| 1 to 999 | $15.00 |
| 1,000 to 2,999 | $12.00 |
| 3,000 to 9,999 | $10.50 |
| 10,000 to 19,999 | $8.25 |
| 20,000 to 29,999 | $6.75 |
| 30,000 to 39,999 | $5.70 |
| 40,000 to 49,999 | $5.25 |
| 50,000 and above | Quoted by Oracle |
Worked example: 400 JRE desktops at four company sizes
Take a company with 3,000 employees and the Oracle JRE on 400 desktops. At the $10.50 band that is $31,500 a month, or $378,000 a year at list. That is $945 per JRE desktop per year, for software whose open source equivalent costs nothing to license.
Keep the 400 desktops fixed and change only the headcount, and the cost per desktop rises with the workforce. The figures below are hypothetical and at list.
| Employees | Band rate | Annual subscription | Cost per JRE desktop |
|---|---|---|---|
| 900 | $15.00 | $162,000 | $405 |
| 3,000 | $10.50 | $378,000 | $945 |
| 12,000 | $8.25 | $1,188,000 | $2,970 |
| 45,000 | $5.25 | $2,835,000 | $7,087.50 |
That ratio explains why JRE findings weigh so heavily in audits. A small runtime footprint that no one had priced ends up pricing the entire workforce. Oracle typically adds a retroactive claim for the years since the updater crossed the line.
Who counts as an employee
Oracle's definition includes all full time, part time and temporary employees, plus the staff of agents, contractors, outsourcers and consultants who support your internal business operations, whether or not any of them use Java.
The full rate bands and discount history sit in our Oracle Java cost analysis. The Java license calculator prices your own headcount in a few minutes.
What if you still hold a legacy Java SE subscription?
Customers on the older Desktop Named User Plus or Processor subscriptions may renew where their existing order allows it, once Oracle confirms current usage matches the licensed counts. For a small, well counted JRE footprint that can cost far less than the employee metric. See renewing an Oracle Java legacy metric.
Where do hidden Oracle JREs sit on your devices?
Mostly inside other software. The installs that decide audits are the ones that standard inventory tools miss by default: private JREs bundled with third party applications, runtime images your own developers built, and old Java Web Start clients.
Private JREs bundled with third party applications
Many desktop applications ship their own JRE inside the application folder. These copies do not appear in the installed programs list and do not write the usual JavaSoft registry keys, so registry based discovery cannot see them. Finding them needs a filesystem scan for the runtime binaries themselves.
Whether the application vendor's license covers that bundled copy is a question each vendor can answer in writing. Where teams assumed coverage without asking, devices already marked clean often turned out to carry Oracle JREs. Our shadow install analysis sets out the scanning method.
Runtime images built with jlink
Since Java 9, developers can use jlink to assemble a trimmed runtime and ship it inside an internal tool. If the input was an Oracle JDK, the output is Oracle Java, and every machine that runs the tool carries it. The packaging step changes nothing about the license.
The license that applies depends on the JDK build.
- JDK 21. Updates were free under the No Fee Terms and Conditions (NFTC) through September 2026, and Oracle has said later updates go to the OTN license.
- JDK 25. Updates are under NFTC through September 2028.
- JDK 11 and 17. All Oracle JDK 11 builds, and JDK 17 updates after 17.0.12, sit under OTN, so images built from them need a subscription for production use.
Java Web Start and JNLP applications
Oracle removed Java Web Start from the JDK in Java 11. Legacy JNLP applications were left pinned to Oracle JRE 8, which often explains why a desktop still runs a current 8u build. OpenWebStart, an open source replacement, runs the same JNLP files on a supported OpenJDK build.
How do you check which JREs you actually run?
Scan the filesystem for Java binaries, then read the vendor and update number from each one. The installed programs list and the registry give you a starting point, never the full count.
- Find every runtime. Search all fixed drives for java.exe, javaw.exe and jvm.dll on Windows, and for java and libjvm.so on Linux and macOS. Microsoft Configuration Manager software inventory and most endpoint agents can collect files by name across the fleet.
- Read the vendor. Running java -version on an Oracle build prints "Java(TM) SE Runtime Environment". OpenJDK builds print "OpenJDK Runtime Environment" with the distributor's name. On Windows, the file properties of java.exe also show the company name.
- Read the update number. A build string such as 1.8.0_202 means Java 8 Update 202. Record whether each Oracle build sits at or below 8u202 or at 8u211 or later.
- Record the parent application. For each runtime outside the standard Java folders, note which product installed it. That list becomes your set of written questions to application vendors.
- Check the updater. Record where jusched.exe still runs, because any device where it runs can cross the line again.
Oracle offers its own Java Management Service to inventory Java, but that data sits in Oracle's cloud. Read our note on the JMS self report risk before you switch it on.
What will Oracle say about your JRE installs, and how should you answer?
Expect Oracle to argue in broad terms unless you bring version data. These are the lines we hear most often, with replies that hold up.
- "The JRE is part of Java SE, so all commercial use needs the Universal Subscription." Reply with your version inventory. Builds at or below 8u202 are under BCL terms, and devices that run the JRE only for Schedule B products such as E-Business Suite fall under Approved Product Use.
- "Our records show your domain downloaded Java 8 updates." A download is not an install. Ask Oracle to state which builds it believes are installed, and on how many devices.
- "You cannot subscribe for only the 400 desktops that use it." That is correct for new purchases, which is why removal is usually the better option. Give Oracle a dated removal plan instead of a purchase order.
- "Removing it now does not settle the past." Ask for the claimed period and how Oracle calculated it. Back period claims are negotiated, and dated decommission records shorten them.
Oracle's opening position in a formal review is covered in our Java audit response guide, and the steps for pushing back on the back fee are in challenging a retroactive Java fee.
What have we seen in recent Oracle Java engagements?
Across roughly 35 to 45 Oracle Java engagements I ran between 2024 and 2026, confusion about the JRE was a recurring root cause of exposure rather than a side issue.
- The free assumption persists. In 6 to 8 of every 10 companies, the team still worked on the pre 2019 belief that the JRE was free for business use, and no one had looked at the updater history.
- Clean devices were not clean. Legacy and bundled Oracle JRE installs sat on 15 to 35 percent of devices that the buyer's own inventory had already cleared.
- Removal was quick once tooling was fixed. Replacing the runtime with a supported OpenJDK build removed the exposure within weeks after packaging and deployment tooling were corrected.
The removal, priced and scheduled, then gave the buyer a strong position in the Java audit defense sequence. Oracle negotiates differently with a buyer who can show a date after which there will be nothing to license. Our OpenJDK comparison maps the replacement builds and their support options.
A JRE footprint no one priced can end up pricing your entire workforce.
Why pinning desktops at 8u202 only buys time
A common recommendation is to freeze every desktop on 8u202 and treat the problem as solved, because that build is free. We disagree with using it as an end state. 8u202 has had no security patches since January 2019, and the next patched Oracle build puts you back under OTN.
Security teams eventually insist on a patch. Freeze the updater to stop new exposure, then replace the runtime with a supported OpenJDK build on a fixed date.
What to do next
- This month. Inventory every Oracle JRE by version string at the filesystem level, bundled and private copies included, and mark each against the 8u202 line.
- Straight after the inventory. Switch off the auto updater wherever a pre 8u211 build legitimately remains, through the Update tab of the Java Control Panel or your desktop management tooling, and record the date.
- Within 30 days. Write to each third party application vendor that ships an Oracle JRE and get a written answer on whose license covers the bundled copy.
- Before any Oracle conversation. Price the residual footprint at your employee band and divide by the number of JRE desktops. That per desktop figure, taken from Oracle's own price list, is the business case for removal.
- Over the following weeks. Replace what stays with supported OpenJDK builds and decommission what goes, keeping dated records as set out in our Oracle Java audit defense guide.
- If Oracle has already written. Do not send data until your inventory is complete. Our Java audit defense service can run the review and the response with you.
Has Oracle contacted you about Java? Talk to us before you reply. Our Oracle Java audit defense is led by former Oracle insiders and runs on a fixed fee.
Frequently asked questions
Is the Oracle JRE free for business use?
Only up to Java 8 Update 202. Those builds shipped under the old Binary Code License, which allowed commercial use at no cost. Builds from 8u211, released from April 16, 2019, carry the OTN license, which is free for personal use and development but chargeable for ordinary business use. Check the update number on each install before anything else.
How did our JRE installs become licensable without any purchase?
Users accepted Java Update prompts that moved their desktops past 8u202, so each device changed license terms on its own. In 6 to 8 of every 10 companies we advised, the team still assumed the JRE was free. That is why every Java review we run begins with the updater history and a version inventory.
What does licensing the Oracle JRE actually cost?
The Java SE Universal Subscription is the Oracle product sold today to cover the runtime, and it is priced per employee, every employee. List rates run from $15 down to $5.25 per employee per month depending on headcount band. In our 3,000 employee example that works out to $945 a year for each desktop that actually runs the JRE.
Can we license only the desktops that run the Oracle JRE?
Not on a new purchase. The Universal Subscription counts your whole workforce, including contractors who support internal operations. Only customers who already hold legacy Desktop Named User Plus subscriptions may be able to renew on a per user basis, and Oracle will check that the counts match actual usage before it agrees.
Do JREs bundled inside third party applications count?
They can. A private JRE inside an application folder is still Oracle Java, and whether the application vendor's license covers it depends on that vendor's terms. Ask each vendor to confirm in writing. In our engagements these copies sat on 15 to 35 percent of devices buyers had believed were clean.
Are jlink runtime images from an Oracle JDK licensable?
Yes, when the JDK they were built from is under the OTN license. A jlink image is Oracle Java with a smaller footprint. Internal tools that ship such an image have distributed Oracle Java to every machine that runs them, which is a common way unrecorded Oracle Java spreads through a company.
What happened to Java Web Start, and what replaces it?
Oracle dropped Web Start from JDK 11, which left legacy JNLP applications tied to Oracle JRE 8. OpenWebStart, an open source launcher, runs the same JNLP files on a supported OpenJDK build. That removes both the dependency on Oracle JRE 8 and the license exposure, and in our engagements the switch took weeks once tooling was in place.
Is it safe to keep desktops on Oracle JRE 8u202 to avoid fees?
It stops new fees from accruing on those desktops, but it leaves a runtime that has received no security fixes since 2019, and any patched Oracle update brings the OTN terms back. Use a freeze only as a short holding measure while you move those desktops to a supported OpenJDK build.