Oracle Java moved from a free use model to a commercial subscription in January 2019 with the launch of the Java SE Subscription. The model was revised again in January 2023 with the launch of the Java SE Universal Subscription, which moved the pricing metric from a per processor or per named user count to a per employee count. The change made the subscription cost a function of the company size rather than the deployment size. The result for buyers is that the cost of compliance with the Universal Subscription often exceeds the value Java provides to the business. Oracle has accelerated the audit programme to recover the licence fees from companies that continued to use Java in production after the metric change. The 2026 audit landscape is the most aggressive period in the history of the product. This article sets out the state of the audit programme, the Oracle position, and the buyer defence pattern.
The Java commercial use claim.
The Oracle position begins with the claim that Java SE has been a commercial product since 2019 and that any commercial use of Oracle Java SE after April 2019 required a paid subscription. Oracle constructs the claim from the licence terms of the Oracle Technology Network developer agreement and from the licence terms of the various Java SE binary distributions. The claim covers Java SE 8 updates after the public end of update date, Java SE 11 long term support updates, and Java SE 17 commercial use across the board.
The claim is broad and Oracle applies it broadly. Companies that downloaded Oracle Java SE binaries from oracle.com and deployed them in production environments are within the scope of the claim. Companies that distributed Oracle Java SE binaries with their own software products are also within the scope. The buyer position depends on the specific use case, on the binary version, and on the licence agreement in force at the time of use.
See the Java versus OpenJDK migration note for the technical alternative.
The Universal Subscription metric.
The Universal Subscription metric counts the total employee population of the buyer entity. The count includes full time employees, part time employees, temporary employees, and external contractors that perform services for the buyer. The count is not restricted to employees that use Java. Companies that deploy Java for a small workload pay the same per employee rate as companies that deploy Java across the technology estate.
The metric produces unusual cost outcomes. A company with five thousand employees that uses Java in one application pays the same subscription cost as a company with five thousand employees that uses Java in fifty applications. The cost is decoupled from the value of the use. The buyer that signs the Universal Subscription pays for the company size rather than for the Java deployment. The buyer that does not sign the subscription must remove Oracle Java SE from the production estate or take the audit risk.
See the Java SE Universal deal page for the structural mechanics.
The audit trigger patterns.
Oracle uses several trigger patterns to identify Java audit candidates. The first pattern is the historical download record from oracle.com. Oracle has historical records of which companies downloaded Java SE binaries and when. The download record creates an inference that the binary was deployed in production. The inference is not always correct but it serves as the audit trigger.
The second pattern is the Oracle Java SE customer database. Companies that purchased the Java SE Subscription before 2023 are in the database. Oracle is renewing those customers onto the Universal Subscription at a higher cost and is auditing the deployment of customers that decline the renewal. The third pattern is the soft outreach by the Java sales team. The Java sales team reaches out to companies that may use Java and asks for a deployment estimate. Responses to the soft outreach are processed into the audit pipeline.
The audit data request.
A Java audit typically begins with a request for the list of Java SE versions installed across the production estate and the count of devices on which each version is installed. Oracle then asks for the employee count of the buyer entity. The data request can be structured as a soft information request rather than as a formal audit notice. Buyers should treat any data request from the Oracle Java sales team as the opening of an audit and should manage the response carefully.
The buyer response should be coordinated through a single point of contact and reviewed by external advisors before submission. The response should distinguish between Oracle Java SE binaries and other Java implementations such as OpenJDK distributions, Eclipse Temurin, Amazon Corretto, and Azul Zulu. The non Oracle binaries are not within the scope of the Oracle subscription claim and should be excluded from the count.
The defence position.
The buyer defence position has four pillars. The first pillar is the inventory of Oracle Java SE binaries. The inventory should be built from internal asset management data, from the developer machine surveys, and from the production deployment surveys. The inventory must distinguish Oracle binaries from non Oracle binaries.
The second pillar is the licence position for each Oracle binary in the inventory. Some Java SE versions are covered by the OTN Free Use Terms and Conditions which permit certain types of use without a subscription. Some versions are covered by the Java SE NFTC licence which permits broader use. The licence position should be documented version by version. The third pillar is the migration plan that removes Oracle binaries from the inventory through replacement with OpenJDK distributions. The fourth pillar is the negotiation strategy that minimises the Universal Subscription cost if any subscription is required.
See the Eclipse Temurin migration note for the technical migration pattern.
The settlement economics.
Java audit settlements have a specific economic pattern. Oracle prefers settlements that include a multi year Universal Subscription commitment. The subscription commitment is the strategic objective. The audit finding is the lever. The buyer that focuses only on minimising the audit finding while ignoring the subscription commitment will exit the audit at a manageable cost in year one and then face the subscription cost in years two and beyond.
The buyer that negotiates the audit and the subscription as a single conversation can often produce a better outcome. The buyer can accept a smaller audit settlement in exchange for a shorter subscription term, or in exchange for an exit ramp at the end of year one. The settlement should be structured to support the buyer Java strategy rather than to support the Oracle revenue model.
Engaging an independent advisor.
Java audits move quickly and the buyer position needs to be assembled in weeks rather than months. An independent advisor that has run Java audit defences across multiple clients can compress the timeline and can produce the technical inventory, the licence position, the migration plan, and the negotiation strategy on a coordinated track.
For the wider cluster see Audit Defense. For the service see Audit Defense. For the deal structure see the Java SE Universal deal page. For the Oracle product see the Oracle Java product page. For the full research read the Oracle Java Negotiation Guide white paper.
The contract construction.
Oracle constructs the Java commercial use claim from a series of licence agreements that govern different Java SE distributions. The licence agreements have changed over time and the version in force at the time of the download determines the buyer rights. The OTN Developer Licence is the most restrictive licence and permits use for development and testing only. The Java SE OTN Free Use Terms and Conditions licence permits broader use including production use for personal applications and certain types of internal business use.
The licence position should be documented version by version. The buyer that can produce the licence in force at the time of each download has a stronger defence position than the buyer that cannot. The licence position is the legal basis for the buyer use. Without the licence position the buyer is dependent on the Oracle interpretation of the commercial use claim.
A worked example.
A European logistics buyer received a Java audit notice in early 2025. The buyer had twenty thousand employees and used Oracle Java SE 8 for legacy applications and Oracle Java SE 17 for newer applications. The Oracle proposal was a Universal Subscription at the published employee price for three years plus a back fee for the historical use period. The total commercial demand was approximately twelve million dollars.
The buyer engaged an independent advisor at the start of the audit. The advisor built the inventory and identified that approximately seventy percent of the Java workloads were running Eclipse Temurin rather than Oracle Java SE. The Temurin workloads were excluded from the Oracle scope. The advisor also identified that the Java SE 17 workloads were covered by the NFTC licence for the production use that the buyer was performing.
The final settlement was a one year Universal Subscription for the residual Oracle Java SE workloads at a negotiated price, with no back fee for the historical period and with a defined exit ramp at the end of year one. The total commercial outcome was approximately eight hundred thousand dollars, a reduction of eleven point two million dollars from the original demand. The buyer used the one year subscription period to complete the migration of the residual workloads off Oracle Java SE.