Support Costs and Optimization

The Unsupported Oracle Estate Risk Calculation

The unsupported estate risk calculation weighs the roughly 22 percent annual support saving from dropping Oracle support against the cost of lost patches, a frozen version, and the risk of reinstating support later at a repriced rate. The buyer move is to run the calculation per system rather than across the whole estate, because a stable workload near end of life is a very different case from a fast moving production platform.

What is the unsupported estate risk calculation?

The unsupported estate risk calculation is the comparison of the roughly 22 percent annual support saving from dropping Oracle support against the cost of lost patches, no version upgrades, and the risk of needing to reinstate support later at a higher reset price. It exists because support is the largest recurring Oracle cost for most estates, and the question of whether to keep paying it is legitimate, but the saving is never free. The calculation makes the trade off explicit so the decision is made on numbers rather than fear or wishful thinking.

This sits within the broader cost and negotiation strategy set out in the Oracle negotiation guide. The point of the calculation is not to argue for or against support in general, but to identify which specific systems are good candidates and which are not.

The buyer takeaway

Support is roughly 22 percent of license value every year, escalating. That is a large saving to leave on the table, but the value of a patch on the day you need it can dwarf a year of fees. Run the calculation system by system.

Can you keep using Oracle software without support?

Yes, a perpetual license lets you keep running the software without support, but you lose access to patches, security updates and new versions, so the running estate is frozen at its current release. This is the structural fact that makes going unsupported possible at all: the license to use the software is separate from the contract to support it, and dropping the latter does not remove the former. The software keeps running exactly as it did. What stops is the flow of fixes and the right to upgrade.

For a stable workload that is not changing and is scheduled for retirement, a frozen version may be entirely acceptable. For a platform that needs security patches and new capability, freezing is a serious constraint. The decision is therefore inseparable from the lifecycle of each system, which is why the calculation is per system rather than a single estate wide verdict.

What are the risks of going unsupported on Oracle?

The main risks of going unsupported are unpatched vulnerabilities, no upgrade path, the cost of reinstating support at a repriced rate if you return, and the loss of Oracle's compliance cover. Each one belongs in the calculation. Unpatched vulnerabilities are a security and regulatory exposure that can dwarf the saving if exploited. No upgrade path constrains the system's future. The reinstatement risk is often underweighted: returning to Oracle support can require back support fees and a repricing, so the saving you banked can be partly clawed back if you change your mind.

Third party support is the alternative that many estates consider here, because it offers a lower cost than Oracle support while still providing fixes, though it carries its own audit considerations covered in third party support and audit risk. The reinstatement and repricing dynamics connect directly to repricing risk when dropping licenses, because the support basis does not stay still while you are away.

Indicative inputs to the unsupported risk calculation
FactorSaving sideRisk side
Annual support feeAbout 22 percent savedEscalation avoided too
Patches and securityNoneUnpatched exposure
UpgradesNoneVersion frozen
ReinstatementNoneBack fees and repricing

A worked example of the calculation

Consider two systems in the same estate. System A is a legacy database supporting a workload scheduled for retirement in two years, stable, not changing, with no need for new features. System B is a production platform under active development with regulatory security requirements. Going unsupported on System A saves roughly 22 percent a year for two years against a low risk, because a frozen, soon to be retired system rarely needs a patch and never needs an upgrade. The calculation favours dropping support. Going unsupported on System B saves the same percentage, but against the risk of an unpatched vulnerability on a regulated production platform and a constrained upgrade path, which is a poor trade.

The same percentage saving produces opposite answers because the risk side differs entirely. This is the heart of the calculation: the saving is uniform, the risk is not, so the decision must be made where the risk lives, which is the individual system.

Contract dependent

Reinstatement terms, back support fees and repricing on return are contract dependent and governed by your support policies and Oracle Master Agreement. The figures here are indicative and meant to show the structure of the calculation, not predict your outcome. Confirm your terms before deciding.

How do you decide per system?

You decide per system by scoring each one on lifecycle stage, change rate, security and regulatory exposure, and reinstatement cost, then comparing that score against the support saving for that system alone. A system near end of life, stable, and low risk is a strong candidate. A system under active development with security obligations is not. The estate wide answer is usually a mix: some systems move to unsupported or third party support, others stay on Oracle support because the risk justifies the cost.

This per system discipline also avoids the common mistake of treating support as an all or nothing estate decision, which is one of the habits examined in the support mistakes that lock in cost. The calculation is granular by design, because that is where the real savings, and the real risks, are found.

Your next step

The unsupported estate risk calculation turns a fraught decision into a system by system trade off you can defend, and it routinely finds savings on stable systems while protecting the ones that need cover. An independent buyer side review scores your estate, models the saving against the risk for each system, and maps the reinstatement and repricing exposure before you act. Book a strategy call to run the calculation across your estate and identify which systems are genuine candidates to go unsupported.

Next step

Book a strategy call to run the unsupported estate risk calculation system by system. Start at the contact page, or read the full Oracle negotiation guide.

FAQ

Unsupported estate questions buyers ask first.

It is the comparison of the roughly 22 percent annual support saving from dropping Oracle support against the cost of lost patches, no version upgrades, and the risk of needing to reinstate support later at a higher reset price.
Yes. A perpetual license lets you keep running the software without support, but you lose access to patches, security updates and new versions, so the running estate is frozen at its current release.
The main risks are unpatched vulnerabilities, no upgrade path, the cost of reinstating support at a repriced rate if you return, and the loss of Oracle's compliance cover, so the saving must be weighed against these.
The License Position

Read Oracle's next move before they make it.

A short weekly note on Oracle audits, Java, ULAs and negotiation. One development, why it matters, and one move you can make this week.

No spam. Unsubscribe anytime.