Video Script
Oracle Java Licensing: The Billion-Dollar Confusion Strategy
Sheshagiri Anegondi (Sheshu) · Rythium Technologies · [Link]
Format: ~10 seconds intro before slide appears · ~25–30 seconds with slide on screen
Script while slide is visible is intentionally sparse — let the audience read.
SLIDE 1 | Oracle Java Licensing — The Billion-Dollar Confusion Strategy
BEFORE SLIDE APPEARS (~10 SEC)
Most companies think they know where their Oracle exposure is.
They’re watching the database. They’re watching the middleware.
They’re not watching Java. And that is exactly what Oracle is counting on.
SLIDE ON SCREEN (~25 SEC)
That phrase — ‘Confusion Strategy’ — is deliberate.
Oracle’s Java licensing is not complicated by accident.
[ Pause. Let them read. ]
Every layer of complexity serves the same purpose: to make the bill larger and harder to
challenge.
SLIDE 2 | Java Was Free. Then Oracle Changed the Rules.
BEFORE SLIDE APPEARS (~10 SEC)
For most of its history, Java was free. Genuinely free. You downloaded it, you used it, that
was the end of the story.
In January 2019, Oracle changed that. Quietly. Without sending anyone a bill.
They just changed the licence. And most companies didn’t find out until an auditor showed
up.
SLIDE ON SCREEN (~25 SEC)
Look at the right column. That last point is the one that catches companies completely off-
guard.
[ Pause. ]
If a third-party application you bought ships with Oracle JDK bundled inside it — that’s your
liability. Not the vendor’s.
You didn’t install it. You didn’t know it was there. Oracle doesn’t care.
SLIDE 3 | 5 Java Traps Oracle Sets on Purpose
BEFORE SLIDE APPEARS (~10 SEC)
These five traps are not quirks of a complicated licensing model.
They are features. Each one is designed to maximise Oracle’s claim and minimise your
ability to push back.
Let me walk you through them.
SLIDE ON SCREEN (~30 SEC)
[ Let them read. ]
Notice that traps one and three work together. The Employee Ambush inflates the count.
The Named User Illusion retroactively inflates old contracts.
And trap five — the OpenJDK Proximity Trap — is the one that catches companies who
think they’ve already fixed the problem.
You migrated to OpenJDK. Oracle’s scripts still found the old binaries. The exposure is still
there.
SLIDE 4 | Secret ±1 — The Per-Employee Pricing Bomb
BEFORE SLIDE APPEARS (~10 SEC)
Before 2023, Oracle’s Java pricing was based on the people who actually used Java.
In 2023, they changed to a model based on everyone in your company. Every single
employee. Whether they’ve ever opened a Java application or not.
This is not a minor change. For large enterprises, it is the difference between a manageable
cost and an existential one.
SLIDE ON SCREEN (~25 SEC)
Look at the middle card. That £185,000 figure is for a thousand-person company at
published rates.
[ Pause. ]
A hospital. A retailer. A logistics firm with ten thousand staff. The maths becomes brutal very
quickly.
And the third card is the one legal teams need to understand: your old Named User Plus
contract is not a shield.
SLIDE 5 | Secret ±2 — The ‘Commercial Use’ Trap
BEFORE SLIDE APPEARS (~10 SEC)
Here is the four-word phrase that has generated more unexpected Oracle invoices than
almost anything else in enterprise software.
‘Any commercial purpose, business function or operation.’
Read those words carefully, because Oracle’s lawyers have.
SLIDE ON SCREEN (~25 SEC)
Read the definition on the slide.
[ Pause. Let them absorb it. ]
Under that definition, running a batch job on a server counts. A developer laptop running
tests counts.
Look at the cloud card on the right. A lot of companies assume moving to AWS or Azure
takes them out of Oracle’s reach. It doesn’t.
SLIDE 6 | Secret ±3 — Oracle’s Java Audit Playbook
BEFORE SLIDE APPEARS (~10 SEC)
When Oracle decides to audit your Java estate, they already have a picture of it.
The LMS scripts they ask you to run are not a discovery exercise for them. They’re a
confirmation exercise.
Your job is to make sure your count is more accurate than theirs — and that you run it first.
SLIDE ON SCREEN (~25 SEC)
[ Let them read the left column first. ]
That third point on the left — third-party apps bundling JDK — is what fills Oracle’s report
with installs you didn’t know you had.
Now look at the right column. Every one of those counter-moves requires you to have
started before Oracle knocked.
If you’re already in an audit and haven’t done this work, you’re negotiating blind.
SLIDE 7 | The 3-Step Java Defence Strategy
BEFORE SLIDE APPEARS (~10 SEC)
Three steps. And the sequence is not optional.
You cannot negotiate a number you don’t have your own version of. You cannot remediate
exposure you haven’t found.
Discover first. Then remediate. Then negotiate.
SLIDE ON SCREEN (~25 SEC)
[ Let them read across the three columns. ]
The most important line in the Negotiate column is the last one.
Oracle’s proposal is a starting position. Not a legal obligation.
[ Pause. ]
Every number they put in front of you is the beginning of a conversation, not the end of one.
SLIDE 8 | About the Author + CTA
BEFORE SLIDE APPEARS (~10 SEC)
I led Java licensing strategy from inside Oracle for over a decade before leaving to work on
the other side of the audit room.
I have seen exactly how these claims are constructed and exactly where they fall apart.
SLIDE ON SCREEN (~25 SEC)
If Oracle is knocking — or if you think they might be — do not respond without an
independent count in your hands.
Do not sign a new Java agreement without knowing what the market actually charges.
[ Pause. ]
The book is on the slide. The website is [Link].
Thanks for watching.
Total estimated runtime: approx. 3–4 minutes · [Link]