Oracle Java SE moved from a per processor and per user metric to a per employee Universal Subscription in 2023. The new metric reshaped the buyer side calculation. Read the pillar before the next Java audit lands.
Oracle Java SE moved from per processor and per Named User Plus to per employee Universal Subscription in January 2023. The new metric counts every employee, regardless of who actually uses Java. The pillar covers history, mechanics, audit posture, alternatives, and buyer side moves.
Oracle Java SE was free until 2019. From 2019 to 2023, Oracle priced Java SE per processor and per Named User Plus on a subscription basis. In January 2023, Oracle replaced both metrics with the Universal Subscription, which prices per employee across the entire organisation.
The Universal Subscription is the most aggressive pricing change in enterprise software in the last decade. A company with one hundred Java servers and ten thousand employees now pays for ten thousand employees, regardless of how many of those employees actually touch Java. The pillar here covers the framework.
The Oracle Java metric has changed three times in five years. Each change carried a buyer side response.
Oracle Java SE was free for commercial use under the Binary Code License. Most enterprises ran Oracle Java without a contract.
Oracle introduced the Java SE Subscription with two metrics. Per processor for server side deployments. Per Named User Plus for desktop deployments. Contracts signed in this window remain valid.
Oracle introduced the Universal Subscription with a per employee metric. The metric replaces both prior metrics for new contracts. Pre 2023 contracts remain valid but cannot be expanded.
The metric counts every employee in the organisation, not Java users.
Oracle defines employee as every full time, part time, temporary, intern, and contractor associated with the organisation. The count is independent of Java use.
Pricing starts at fifteen dollars per employee per month at the smallest tier and steps down through volume bands. Large enterprises typically negotiate to single digit per employee rates.
The Universal Subscription covers Oracle Java SE on every device and server inside the organisation. No additional licensing is required for incremental deployments.
Oracle Java versus alternatives at a glance
| Distribution | Commercial use | Support model | Typical use |
|---|---|---|---|
| Oracle Java SE | Requires Universal Subscription | Oracle paid support | Enterprises preferring single vendor stack |
| Eclipse Temurin | Free | Community plus optional paid | Most common OpenJDK replacement |
| Amazon Corretto | Free | Amazon LTS at no charge | AWS heavy estates |
| Azul Zulu | Free, paid optional | Azul paid extended support | Latency sensitive workloads |
| Microsoft Build of OpenJDK | Free | Microsoft LTS at no charge | Azure and Microsoft heavy estates |
| BellSoft Liberica | Free, paid optional | BellSoft paid extended support | Embedded and lightweight workloads |
Oracle Java audit activity rose materially in 2024 and 2025. Three audit triggers recur.
Oracle audits enterprises that have downloaded Java from the Oracle website without a subscription. The download log is the trigger.
Oracle audits enterprises in the twelve months before a Database or EBS renewal. Java findings drive the renewal posture.
Oracle audits enterprises with documented large Java deployments through partner channels or public references.
The defense begins with an estate sweep. Identify every Java instance and the distribution it runs. Oracle Java requires a subscription. Non Oracle distributions do not.
The standard reseller pitch is that the Universal Subscription is the safe choice because it covers everything and avoids audit risk. We disagree. In our engagement experience, the Universal Subscription is the most expensive answer in roughly seven out of ten enterprise estates we have modeled. The buyer side move is to run the estate sweep first, isolate Oracle Java to the workloads that actually require Oracle support, migrate everything else to a free OpenJDK distribution, and only then negotiate the residual Universal Subscription against a much smaller employee envelope. This is not what the Oracle account team will suggest and it is not how the typical reseller frames the decision.
Eight major Java alternatives cover most enterprise workloads in 2026.
Eclipse Temurin is the community supported OpenJDK distribution from the Adoptium project. Free for commercial use. Supported by community and by paid vendors including IBM and Microsoft.
Amazon Corretto is the Amazon supported OpenJDK distribution. Free for commercial use. Long term support aligned to the OpenJDK release cadence.
Azul Zulu is the Azul supported OpenJDK distribution. Free at the community edition. Paid enterprise edition with extended support and additional features.
Microsoft Build of OpenJDK is the Microsoft supported OpenJDK distribution. Free for commercial use. Long term support for LTS versions.
BellSoft Liberica is the BellSoft supported OpenJDK distribution. Free for commercial use, with extended paid support.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The Universal Subscription is not a Java licence. It is a per employee fee that has nothing to do with how the technology is used. Treat it as a commercial choice, not a technical one.
Most enterprises pursue one of three migration patterns.
Replace every Oracle Java instance with an OpenJDK distribution. Lowest cost option. Highest engineering effort if the estate is large.
Keep Oracle Java on critical workloads with paid support. Migrate non critical workloads to OpenJDK. Mid cost, mid engineering effort.
Take the Universal Subscription but negotiate hard on the employee count, the tier price, and the contract term. Highest cost option but lowest engineering effort.
Five moves recur in every well managed Oracle Java estate.
Run a full Java discovery sweep across servers, desktops, and embedded systems. Identify the distribution per instance.
Tag every Oracle Java instance. Isolate non Oracle distributions from the audit conversation.
Build the migration plan with the right pattern. Full migration, hybrid, or Universal Subscription with optimisation.
If the Universal Subscription path is chosen, negotiate the employee count definition, the tier price, and the multi year term.
Lock developer tooling and CI CD pipelines to non Oracle distributions for new workloads. Prevent Oracle Java drift back into the estate.
The Universal Subscription is the current Oracle Java SE licensing model. It prices per employee across the entire organisation, regardless of how many employees actually use Java. It replaced the per processor and Named User Plus metrics from 2023 onward.
Yes. Pre 2023 perpetual and Named User Plus contracts remain valid. They cannot be expanded to cover new deployments. New deployments require the Universal Subscription.
Every full time, part time, temporary, intern, and contractor associated with the organisation. The count is independent of Java use. Contractors with system access typically count.
Yes. OpenJDK distributions including Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, and BellSoft Liberica are free for commercial use and provide community or vendor support.
Yes for the vast majority of workloads. Oracle Java and OpenJDK share the same core code base. Some advanced features in Oracle Java GraalVM and the Java Flight Recorder are differentiated. Test workload behaviour before migration.
An Oracle Java audit covers every Oracle Java deployment in the enterprise. Auditors collect download evidence, deployment evidence, and user counts. The findings drive a subscription proposal scaled to the discovered scope.
It depends on engineering capacity, audit posture, and the long term cost model. Full migration to OpenJDK is the lowest cost option. The hybrid pattern with subscription on critical and OpenJDK elsewhere is a middle path. The Universal Subscription with optimisation has the lowest engineering effort but highest cost.
Open with an inventory and entitlement baseline before any vendor conversation. Pull trailing twelve months of usage data, score it against contracted scope, and document the gap. The single most common reason buyers leave money on the table is opening the negotiation without a defensible baseline. The buyer side calendar starts at 270 days out, not at 60.
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.
Oracle Java is not the only Java. Every Java audit must start with one question. How much of the estate runs Oracle, and what is the alternative on the rest.
