Home  /  Research Videos  /  Oracle
Oracle · 4:37 · Buyer-side briefing

Renew or Exit, and How We Help With Either

Session 6 of the Microsoft EA Renewal 2027 Series. At twelve thousand employees an OpenJDK exit models at one point seven three million over three years against two point one to two point eight for a negotiated subscription. What the estate really looks like, why hybrid is the worst of the three, what notice actually requires, and how Redress works either side of the decision.

Share

The presenters in this briefing are AI generated avatars. The research, figures, and guidance are real, produced by Redress Compliance analysts from our consulting engagements and market network.

Transcript

Full narration of the briefing. Click a section heading to jump the player to that moment.

Two honest options 0:00

Everything so far leads to one decision with two honest answers. Renew, on much better terms than the ones you were offered. Or leave, and stop paying payroll rates for a runtime. Both are legitimate, and which one is right depends on your estate rather than on anybody's opinion about Oracle.

What we can do is put real numbers on each, from the thirty to forty Java exits we have guided and the engagements behind the earlier parts, so the decision is made on arithmetic rather than on the temperature of the last phone call.

The estate is smaller than the bill 0:35

Start with the fact that reframes the whole decision. Because the subscription prices per employee, the invoice is completely indifferent to your estate, and the estate is almost always smaller than everyone assumes. Across our guided exits, Oracle Java actually ran on ten to thirty percent of the machines the bill implied. So the exit blocker is never migration difficulty.

It is visibility, because you cannot remove what you have never inventoried. And that inventory has to reach past installer lists: filesystem scans for the runtime binaries, the private runtimes bundled inside third party applications, the images baked into internal tools, and the build pipelines pulling Oracle JDKs by default.

What OpenJDK covers 1:19

Then the technical question, which turns out to be the easy one. Free OpenJDK builds covered seventy to ninety five percent of workloads with no application change at all, and the distribution choice, Corretto, Temurin, Zulu, is an operational preference rather than a risk decision. A small number of workloads genuinely need a commercial build, and the discipline is to identify those from the inventory rather than assume them from fear. Net Java spend fell sixty to ninety percent once migrations completed, and at large enterprises those migrations ran nine to fourteen months, with tooling discipline rather than code as the blocker.

The three way comparison 1:57

Put the two paths side by side at twelve thousand employees. The OpenJDK exit models at one point seven two eight million over three years, everything included. A negotiated subscription over the same period runs two point one zero million to two point seven eight million, depending on how well it is negotiated, which is what parts two through four were about. And then there is the third option that reaches the shortlist most often and performs worst on cost: hybrid.

Keeping some Oracle Java while migrating the rest. You carry the whole employee metric and the whole migration programme at the same time, and pay for both.

Notice is a legal act 2:34

If you exit, two mechanics decide whether it works. First, notice is a legal act. Written non renewal notice, served to the party named in the notices clause of your agreement, is what stops an automatic renewal. An email to your account rep is not notice, however friendly the relationship.

Second, the term end date is absolute. The subscription grants term rights rather than perpetual ones, so every Oracle JDK binary has to be gone by the term end date, not shortly after it, and the removals documented, because the audit approach starts from download records rather than from your estate.

One binary, the whole workforce 3:11

And price the residual risk properly, because the metric prices it for you. One reinstalled binary after the term ends is a claim priced across your entire workforce: six hundred and thirty thousand dollars a year for a five thousand employee company at the ten fifty band, from a single machine. Which is why the technical controls that prevent reinstallation, blocking the download endpoints, pinning the build pipelines, removing the default from your images, are part of the commercial exit rather than an IT afterthought. The evidence pack is the other half: what ran where, when it was removed, and what replaced it, kept as your audit defence.

How we help, either way 3:51

So, how we can help, and it is the same offer whichever way you go. If you want to renew, we negotiate it with you: the count defended, the band modelled, the definition written into the order, the uplift capped, the floor removed. If you want to leave, we run the exit: the inventory, the disposition plan, the notice served correctly, the evidence pack built as you go. And if a letter has already arrived, we answer it layer by layer.

We work buyer side only, never vendor funded, on contingency: our fee is twenty five percent of what we save you, so if we save you nothing, you pay nothing. com. The first conversation costs nothing either way.

Negotiating a Oracle renewal this year?

Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.

Talk to a Oracle negotiator
Browse all 167 research videos