Practice v · Java
Oracle Java Licensing
Independent buyer side advisory for the Java SE Universal Subscription, the employee metric, and migration to alternative JDK distributions.
Independent buyer side advisory for the Java SE Universal Subscription, the employee metric, and migration to alternative JDK distributions.
Oracle Java licensing now runs on the SE Universal Subscription, priced per employee rather than per user or processor. That metric counts your whole workforce, not your Java users, so proposals routinely arrive an order of magnitude too high. A buyer side review models the real exposure, structures a carve out, and plans migration to OpenJDK where it pays.
In 2023 Oracle replaced its per user and per processor Java SE subscriptions with a single Employee for Java SE Universal Subscription. The metric is the most aggressive on the price list. It counts every full time and part time employee, every temporary worker, and every contractor and agent, whether or not they touch a single Java application. A company with nineteen thousand employees and eleven hundred Java users is quoted for nineteen thousand.
The result is proposals that bear no relation to operational reality. CFOs across thirty countries have opened renewal letters that multiply their prior Java spend many times over for the same installed footprint. The pricing assumes the org chart, and Oracle's audit position assumes that any Oracle JDK download against a commercial release confirms the obligation across the whole employee base.
The exposure is real but it is negotiable, and it is escapable. Most Java estates can be migrated to a free OpenJDK distribution, Eclipse Temurin, Amazon Corretto, Microsoft Build of OpenJDK, or Azul, with little or no code change, removing the subscription requirement entirely for those workloads. Where Oracle JDK features or support are genuinely needed, the population can be scoped and the metric challenged rather than accepted at face value.
We model the actual Java footprint, separate the workloads that need Oracle from those that do not, plan the migration of the rest, and negotiate the residual subscription against a defended active population rather than total headcount. The gap between the workforce and the Java estate is the entire negotiation.
A measurement of the real Java footprint, the Oracle JDK versions in use, and the employee count Oracle would apply, with the gap between them quantified.
A defended position on the population that should count, separating genuine Java dependency from incidental presence on the network.
A workload by workload plan to move from Oracle JDK to OpenJDK distributions, with the compatibility and support implications assessed.
Where Oracle is genuinely required, structuring the subscription around the workloads that need it rather than the whole organisation.
Assessment of historical Oracle JDK downloads and the audit triggers they create, with a documented response position.
Portability and reconciliation clauses that permit future migration without penalty and price the subscription to defined use.
We open the channel with Oracle on your terms, fix the scope of the conversation, lock the calendar, and ensure no measurement data leaves the perimeter without buyer side review.
An independent measurement against the same ruleset Oracle applies, performed earlier and with cleaner data. Every finding is categorised by exposure tier and tied to the contract clause that governs it.
Findings are documented and argued line by line. Concessions are priced. We have sat on Oracle's side of these tables and know which positions hold and which dissolve.
The settlement is converted into forward commercial value rather than backward payment, with renewal protections, audit cure provisions, and portability written into the result.
Java engagements scope to the size of the estate and whether an audit or renewal is live. A focused exposure model and migration plan fits a fixed fee. Ongoing migration oversight suits a retainer. Where a Universal Subscription proposal or audit is on the table, a gain share arrangement ties the fee to the reduction secured.
The right structure depends on the engagement. Read our engagement model overview to see when a fixed fee, a retainer, or a gain share arrangement fits, then request a consultation to scope your estate.
Since 2023 Oracle Java SE is sold as the Employee for Java SE Universal Subscription. It is priced per employee, where employee includes full time and part time staff, temporary workers, contractors, and agents, regardless of whether they use Java. The old per user and per processor subscriptions are no longer sold.
Yes. The metric counts the total employee population, not the people who run Java. That is why proposals often arrive an order of magnitude above operational need. The negotiation centres on defining the population that genuinely should count rather than accepting total headcount.
Frequently. Most workloads can run on a free OpenJDK distribution such as Eclipse Temurin, Amazon Corretto, the Microsoft Build of OpenJDK, or Azul, often with no code change. Migrating those workloads removes the subscription requirement for them entirely.
Downloads of the Oracle JDK against commercially licensed releases are the primary trigger. Oracle tracks download activity and uses it to open conversations. A documented review of historical downloads and the versions in use is the foundation of any defensible response.
For most purposes, yes. OpenJDK is the open source reference, and distributions built from it are functionally equivalent for the vast majority of applications. Differences exist in long term support cadence and a few commercial features, which is why a workload by workload assessment matters.
It varies with the gap between the workforce and the Java estate. Where that gap is large, reductions of seventy to eighty five percent against the opening Universal Subscription proposal are achievable through a defended population and migration of non dependent workloads.
Usually a blend. Migrate the workloads that can move to OpenJDK, and subscribe only for the residual that genuinely needs Oracle JDK, scoped and protected by a portability clause. Accepting a workforce wide subscription without testing migration is rarely the cheapest path.
End to end response when an Oracle Java download review or audit lands.
View the practice →How Java and other entitlements travel to OCI and the hyperscalers under BYOL.
View the practice →When Java sits inside a broader Oracle agreement that is worth restructuring as a whole.
View the practice →A buyer side model of your real Java footprint, with a migration plan and a defended employee population, turns a workforce wide proposal into a priced, escapable decision.