A regional health system was quoted an Oracle Java SE Universal Subscription priced on its entire workforce. We re-based the count on genuine Java usage and renegotiated the subscription 47% lower.
The health system received an Oracle Java SE Universal Subscription quote ahead of a renewal. The Universal Subscription is sold on the employee metric — and under Oracle's definition the employee metric counts the entire workforce, not the people who actually run Java.
Oracle's number was built on the health system's full headcount: clinicians, nursing staff, administrative teams, and facilities staff — the overwhelming majority of whom never touch an Oracle JDK. The quoted figure dwarfed the system's actual Java footprint, which sat on a contained set of application servers and a minority of clinical workstations.
The health system did not dispute that it needed some Oracle Java coverage. What it would not do was subscribe, at a per-employee rate, for thousands of people who would never start a Java runtime — and it wanted certainty that the same thing would not happen again at the next renewal.
We built a clear picture of which servers and workstations genuinely run Oracle Java SE, and separated Oracle JDK installations from OpenJDK builds that carry no Oracle subscription obligation.
We identified which installations genuinely require a paid subscription and which were already covered by free terms or running on a no-cost distribution — so only real, in-scope use drove the conversation.
The Universal Subscription metric is fixed by Oracle's contractual definition. We confirmed precisely who must be counted, removed the assumptions Oracle had built in, and documented a figure the health system could stand behind.
We costed a migration of the contained Java estate onto a free OpenJDK distribution, giving the renewal a genuine walk-away position rather than a bluff.
We took the corrected usage picture to Oracle and renegotiated the subscription to reflect the real footprint — with the metric definition and a multi-year uplift cap written into the contract.
The health system renewed its Oracle Java SE Universal Subscription 47% below Oracle's opening quote, with the subscription sized to genuine, in-scope Java usage rather than total headcount.
Beyond the immediate saving, the contract now fixes the employee-count definition in writing and caps future uplifts for three years — removing the uncertainty that had made the original quote impossible to budget against.
The renewal landed well below Oracle's opening per-employee number.
The employee count is agreed in writing and reflects real Java usage.
Future price uplifts are contractually limited, making the cost plannable.
If we take on your Oracle Java audit and cannot reduce the claim, we refund our fees. See how the guarantee works →
If Oracle has priced your Java SE Universal Subscription on total headcount, the number is almost always negotiable. We re-base it on real usage — independent of Oracle, on your side of the table.
Weekly Oracle Java updates, audit alerts, and negotiation intel.