The Commission called the SAP settlement a benchmark, and Redress understands Brussels and Oracle are already talking. What an Oracle equivalent would change, and how to use it now, from support terms to the quiet Exadata repricing.
The presenter in this briefing is an AI generated avatar. The research, figures, and guidance are real, produced by Redress Compliance analysts from our consulting engagements and market network.
The Commission framed the SAP settlement as a benchmark, and Redress understands Brussels and Oracle are already talking. Daniel explains why Oracle most likely ends up on the same route, how to negotiate as if it is coming, and why the quiet Exadata repricing means you should not wait for the regulator to fix your bill.
The full narration, section by section. Click a section heading to jump the player to that moment.
If a regulator just rewrote the economics of SAP maintenance, why would Oracle be any different? That is not a rhetorical question. It is the question every Oracle customer should be planning around for the next eighteen months.
Here is what we know. The European Commission closed the SAP case in July with binding commitments: reinstatement fees abolished, back maintenance capped, the right to split the estate, termination rights for unused licenses. Ten years, worldwide, enforceable. And the Commission did not frame it as a one off.
It framed the settlement as a benchmark, with further decisions in cloud markets expected before the end of twenty twenty six. Oracle's support model shares the same architecture the Commission just dismantled at SAP: support at twenty two percent of license value, repricing rules that punish partial reductions, and re entry costs that make leaving support a one way door. From our client work and conversations in the market, Redress understands that the Commission and Oracle are already talking. Our read is that Oracle most likely ends up on the same route, or concedes large parts of it to avoid a formal case.
What should you do about a settlement that has not happened yet? Use it twice.
First, negotiate as if it is coming, because either way you win. Put SAP equivalent protections on the table in every Oracle negotiation this year: capped re entry, the right to reduce support on shelved licenses, termination for products you no longer run. Oracle can refuse, but every refusal is now measured against what a regulator just extracted from its closest peer, and account teams know exactly how that reads.
Second, do not wait for Brussels to fix your current bill, because the pressure today is moving the other way. Effective Exadata cloud rates have roughly doubled against prior generation pricing, with no announcement. It surfaces in quotes and at renewal. The new X eleven M generation is sold in ECPUs while earlier generations used OCPUs, which makes every quote genuinely hard to compare, so normalize each one to a common unit of compute before you accept any number.
Hardware moved first, with selected lines up forty to fifty percent. And multicloud does not save you. Database at AWS and Database at Azure price identically to OCI, so the increase follows you everywhere, including Cloud at Customer with its four year committed floor. Remember that a list change does not rewrite a signed contract, so your exposure sits in exactly four places: expiring Exadata and Cloud at Customer renewals, pay as you go and overage billed at the current rate card, new workloads drawing down Universal Credits at that card, and any contract where Oracle reserved the right to adjust rates mid term.
Check which of the four apply to you before the account team calls, because they already have.
So audit every Oracle cloud order document this quarter: renewal dates, rate protection, overage exposure, and any mid term repricing rights Oracle reserved. Demand per service price holds on any Universal Credits commitment, plus a credit reduction right if Oracle moves service prices mid term. And if you are inside twelve months of an Exadata or support renewal, start benchmarking now, because under Oracle's merged sales organization the applications and technology relationship is one negotiation, and it should be played as one.
Regulation is finally moving toward the buyer, but leverage only counts if you use it before it gets priced in. If you want help doing that, Redress works on contingency: twenty five percent of what we save you, and nothing otherwise.