Practice

Java licensing advisory.

The Java SE Universal Subscription is priced per employee and counts every employee and contractor regardless of use, and Gartner predicts 1 in 5 Java users will face an Oracle audit by 2026. We map real usage, challenge the metric, and plan the OpenJDK exit.

Per employeeThe metric we contest
1 in 5Java users audited by 2026
OpenJDKThe exit we plan
01 The problem

Why did Java licensing get so expensive?

Oracle moved Java SE to a subscription priced on total employee count, not on who actually runs Java. The bill is built on headcount, so it climbs far faster than usage.

The per employee metric counts all employees and contractors, whether or not they ever touch Java. That is the mechanism behind the Java audit wave of this era.

Java downloads without a subscription are a frequent audit trigger, because Oracle can see the download history. The preliminary demand then arrives inflated at list price across your entire workforce. The buyer move is to separate where Oracle Java SE is genuinely needed from where an open distribution will do, and to contest a metric that bills people who never run the software.

01

The subscription counts every employee and contractor, regardless of use.

02

Java downloads without a subscription are a common audit trigger.

03

Gartner predicts 1 in 5 Java users face an Oracle audit by 2026.

04

A line by line review of findings typically cuts the claim 60 to 80 percent.

02 What we do

Four moves that take the metric apart.

01
Map

We map where Java actually runs across the estate and reconcile it against download history and entitlements.

02
Challenge

We contest the per employee count, the scope of the metric, and any usage that was never operationally meaningful.

03
Migrate

We plan a defensible move to OpenJDK or another distribution wherever Oracle Java SE is not required.

04
Settle

We negotiate the position to a number you can defend, with the future state documented to keep it closed.

03 Worked example

How the per employee metric inflates a Java bill.

Illustrative only. The per employee metric counts headcount, not Java users. Indicative figures, anonymized.
MeasureMid sized firm
Total employees and contractors5,000
Staff who actually run Java120
Counted under the per employee metric5,000
Workloads that could move to OpenJDKMost
Buyer moveMap, contest, migrate

The gap between 120 real users and 5,000 counted employees is the whole exposure. Closing it is a mix of contesting the metric on the workloads that must stay on Oracle Java SE and migrating the rest. For the full mechanics, read the Oracle Java licensing guide, then see License Compliance Review and Audit Defense.

04 FAQ

Java licensing questions, answered.

It is priced per employee and counts all employees and contractors regardless of whether they use Java. A company of 5,000 people pays for 5,000 even if only a handful run Java.
Java downloads without a subscription are a common trigger, because Oracle can see the download record. Gartner predicts 1 in 5 Java users will face an Oracle audit by 2026.
Often yes. OpenJDK and other distributions cover many workloads. We map where Oracle Java SE is genuinely needed and plan a defensible migration that removes the per employee exposure. Some answers here are contract dependent and we flag them as such.
Two models. A Fixed Fee scoped up front, or Gainshare, a share of verified savings with zero retainer and no risk to you. We guarantee that we reduce your Oracle exposure or we reimburse our service fee.
05 Get started

Have a Java letter or a download you cannot explain?

Tell us where you are with Java. We reply with a scoped Fixed Fee or a no risk Gainshare proposal, and a clear read on whether the per employee count can be cut.

Read the Oracle Java licensing guide

The License Position

Stay ahead of the Java audit wave.

A short weekly note, buyer side. One development, why it matters, and one move you can make this week.

Buyer side only. Unsubscribe anytime. Last reviewed June 2026