The Java Runtime Environment is licensed under the per employee Java SE Universal Subscription. This guide covers the cost, the audit triggers, and the buyer side moves that cut the exposure.
The Oracle JRE is not free for business use in 2026. The per employee Java SE Universal Subscription covers the runtime, the cost scales with head count, and the cleanest fix is usually a supported OpenJDK runtime.
Many teams still treat the Java Runtime Environment as a free download. For current Oracle builds used in business, that is no longer true.
Oracle moved Java SE to a subscription in 2019 and to a per employee model in 2023. The runtime is covered only by that subscription, which changes the cost and the audit math.
No. Current Oracle JRE builds require a paid Java SE subscription for commercial use. The free era ended with the licensing changes that began in 2019.
Before 2019 the Oracle JRE was broadly free under the old binary code license. Oracle then introduced paid subscriptions and tightened the terms, which you can read on the Oracle Java SE subscription page.
Some newer releases are available under the Oracle No Fee Terms and Conditions for a limited period. Once that window closes, continued use of those builds needs a subscription.
The subscription is the single Oracle product that licenses the runtime today. It bundles the runtime, the development kit, and support under one per employee metric.
The Universal Subscription counts every employee in the organisation, not JRE installs or active users. Contractors with system access typically count under Oracle's definition.
White Paper ยท Oracle
The Oracle Java Buyer Side Playbook
What the Universal Subscription really costs and how buyers push back. Read it free.
Cost is a function of head count and tier, not of how many machines run the JRE. The list rate steps down as the employee band rises.
Indicative Java SE Universal Subscription bands
| Employee band | List direction | Buyer side note |
|---|---|---|
| 1 to 999 | Highest per employee rate | Compare against OpenJDK first |
| 1,000 to 9,999 | Stepped discount bands | Negotiate the band boundary |
| 10,000 to 49,999 | Lower per employee rate | Press on term and escalator |
| 50,000 plus | Lowest per employee rate | Model full OpenJDK exit |
Because the metric is per employee, a small JRE footprint can still carry a large bill. A company with a few hundred JRE machines and ten thousand staff pays for ten thousand.
The common advice is to simply buy the subscription so the runtime is covered and the audit risk disappears. We disagree. In most estates we review, paying per employee for a runtime that sits on a minority of devices is the most expensive option on the table. The buyer side move is to inventory every JRE, replace it with a supported OpenJDK runtime such as Temurin or Corretto wherever Oracle support is not contractually required, lock the developer tooling so Oracle builds cannot drift back, and only then price any residual Oracle need against a small, defensible scope rather than the whole head count.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The JRE feels free because it always was. The bill arrives because the metric counts people, not runtimes.
The runtime is the easiest thing for Oracle to detect. Three triggers recur.
Oracle matches JRE downloads from its site against the corporate domain. A single download log is a common audit starter.
Older Oracle JRE versions on business machines signal commercial use of a licensed runtime. Version strings are the evidence, not file names.
Java findings often surface in the months before a Database or middleware renewal, where they shape the wider negotiation.
The exposure falls fastest when the runtime is replaced, not just counted. Four moves work in sequence.
Find every JRE by version and distribution across desktops, servers, and images. Map each to an owner.
Move covered machines to a supported OpenJDK runtime such as Eclipse Temurin or Amazon Corretto. Both are free for commercial use.
Pin installers, images, and pipelines to the chosen OpenJDK build so Oracle JRE cannot return through a default download.
No. Current Oracle JRE builds require a paid Java SE subscription for commercial use. The broadly free era ended with the licensing changes that began in 2019.
The Java SE Universal Subscription is the only current Oracle product that covers the runtime. It bundles the runtime, the development kit, and support under one per employee metric.
It is priced per employee across the whole organisation, not per JRE install or per user. Contractors with system access typically count under Oracle's definition.
Because the metric counts people, not runtimes. A small JRE footprint on a large head count still pays for every employee, which is why total cost surprises buyers.
Yes. Supported OpenJDK runtimes such as Eclipse Temurin and Amazon Corretto are free for commercial use and replace the Oracle JRE for most workloads.
Download evidence is the most common trigger. Oracle matches JRE downloads against the corporate domain, and older version strings on business machines confirm commercial use.
Use of current Oracle builds in business needs a subscription. Some newer releases are free under limited No Fee terms, but continued use past that window requires a subscription.
Inventory the runtime, replace Oracle builds with a supported OpenJDK runtime, and lock the tooling so Oracle JRE cannot return. Replacement usually completes within weeks.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
We work for the buyer. Always. There is no other side of our table.
Audit signals, Universal Subscription pricing moves, OpenJDK migration patterns, and the buyer side leverage points across the Oracle Java estate.
