An end to end Oracle Java audit engagement, from the first letter to a signed settlement, built on a controlled response, a defensible evidence base, and credible OpenJDK leverage.
The flagship engagement runs an Oracle Java audit end to end, from the first letter to a signed settlement. The work is evidence first, scope tight, and built around a credible OpenJDK alternative that gives the buyer real leverage.
An Oracle Java audit moves fast once it starts. The flagship engagement exists to slow it down and put the buyer back in control.
The work is not about arguing. It is about building an evidence position Oracle cannot easily dispute, then negotiating from it.
It covers the whole lifecycle, from the first contact to a signed agreement. Nothing is handed back to the buyer half finished.
The work is led by advisors who sat inside Oracle and IBM. The team knows how the claim is built, which is what lets it be taken apart.
Oracle builds the claim from detection data and a broad reading of the metric. Understanding the construction is half the defense.
Oracle matches Java downloads against the corporate domain, as set out on the Java SE subscription page. Download logs are the usual starting point.
Oracle then applies the per employee metric to the whole organisation. The claim assumes the broadest possible scope unless the buyer narrows it with evidence.
The engagement phases at a glance
| Phase | Window | Buyer side goal |
|---|---|---|
| First response | Days 1 to 10 | Control scope and timeline |
| Estate sweep | Weeks 2 to 6 | Separate Oracle from OpenJDK |
| Position build | Weeks 4 to 8 | Defensible count and alternative |
| Settlement | Weeks 8 plus | Smallest defensible close |
The sequence is deliberate. Each step builds the evidence base before any number is conceded.
The opening response sets scope, channel, and timeline. It avoids handing Oracle raw data that widens the claim.
The estate sweep tags every Java instance by distribution and version. A payroll based employee baseline replaces Oracle's broad assumption.
A real OpenJDK migration plan, using builds such as Eclipse Temurin, Amazon Corretto, or the Microsoft Build of OpenJDK, gives the buyer a genuine walk away.
The common advice is to cooperate fully and fast, hand over the data, and buy the subscription to make the audit go away. We disagree. In our engagement experience, fast full cooperation usually widens the claim and removes the buyer's leverage. The better move is to control the first response, build a defensible evidence position before conceding any number, and hold a credible OpenJDK migration as the alternative. Buyers who do this settle materially lower than those who treat the subscription as the only safe exit, because the alternative changes what Oracle can realistically hold out for.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
An Oracle Java audit is won in the first response, not the last. The buyer who controls the evidence controls the number.
White Paper ยท Oracle
The Oracle Java Buyer Side Playbook
What the Universal Subscription really costs and how buyers push back. Read it free.
Settlement closes the gap between Oracle's claim and the defensible position. The alternative is what moves the number.
The defended employee count and the isolated Oracle footprint set the ceiling for any subscription. Oracle's opening number is treated as a starting point, not a fact.
A credible OpenJDK exit caps what Oracle can hold out for. The buyer can decline the subscription entirely if the terms do not improve.
The engagement ends with tooling locked to OpenJDK where chosen, so the same exposure does not return at the next renewal.
The engagement targets the smallest defensible commercial position and a clean estate. The numbers below reflect the pattern across recent work.
Settlements typically close well below the opening claim once evidence and an alternative are in place. Price protection terms cap future escalation.
It covers the full Oracle Java audit lifecycle, from the first notice to a signed settlement. The work includes the first response, the estate sweep, the position build, and the negotiated close.
It is led by advisors who worked inside Oracle and IBM. That background is what lets the team understand how Oracle builds the claim and where it can be narrowed.
Oracle builds the claim from download detection matched to the corporate domain, then applies the per employee metric to the whole organisation. The claim assumes the broadest scope unless evidence narrows it.
The first 30 days set the trajectory. A controlled, evidence led response keeps scope and timeline with the buyer, while a rushed data dump usually widens the claim.
A credible OpenJDK migration plan is the core leverage. When the buyer can genuinely walk away to a free runtime, Oracle cannot hold out for the full opening number.
Settlements commonly close well below the opening claim once a defensible employee count and a real alternative are in place. The exact figure depends on the estate and the evidence.
Not necessarily. Many buyers keep Oracle on a small critical cluster and move the rest to OpenJDK. The residual subscription is then sized to that narrow scope.
Do not reply before the response is planned. Engage independent advisory, start the estate sweep, and build the evidence position before any number is discussed with Oracle.
The Redress Java audit guarantee
Redress Compliance backs every Oracle Java audit defense with a services guarantee. You pay no fees for any backdated Java payments. If a backdated fee is ever assessed and you have to pay it, we reimburse you our full services fee.
Oracle is tracking download records and IP addresses, then reaching out for what they call friendly conversations about Java. It is an intimidation tactic, and it often ends in an audit or legal action. We have had six clients contacted directly by Oracle's legal department about their use of Java. Fredrik Filipsson, Co Founder and Group CEO, Redress Compliance
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.
We work for the buyer. Always. There is no other side of our table.
Audit signals, Universal Subscription pricing moves, OpenJDK migration patterns, and the buyer side leverage points across the Oracle Java estate.
