Editorial photograph of a CIO and procurement lead reviewing Oracle third party support contracts at a long boardroom table
Guide · Oracle · Third Party Support

Oracle Third Party Support. Rimini Street and the Alternatives.

Half of the Oracle support invoice never funds a patch the customer uses. Rimini Street, Spinnaker, and the smaller bench all sit at roughly fifty percent of Oracle list. The cut releases capital but only when the contract clauses and the audit posture line up first.

Read the Framework Oracle Hub
50%Typical support saving
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Oracle support runs at twenty two percent of net license value. Half of that figure funds patches, half funds the right to call Oracle Support. Most enterprises read fewer than five tickets a year. The economics favor third party support for any product that has reached steady state.

Rimini Street is the largest provider. Spinnaker, Support Revolution, and a smaller bench round out the field. All three sit at roughly half of Oracle list. The cut releases between three and ten million dollars a year on a typical large enterprise account.

Read this guide alongside the Oracle knowledge hub, the Oracle advisory practice, the third party support comparison reference, the Oracle ULA Decision Framework, and the Vendor Shield subscription.

Key Takeaways

What a CIO and head of procurement need to know in 90 seconds

  • The headline saving is fifty percent. Rimini Street, Spinnaker, and the smaller bench sit at roughly half of Oracle list.
  • The saving is recurring. Every year of third party support is another fifty percent off the Oracle baseline.
  • Patch policy differs by provider. Rimini Street writes custom fixes. Oracle critical patch updates do not flow through.
  • Reinstatement is the lock in. Returning to Oracle support means paying the back maintenance plus a penalty.
  • The audit risk rises. Oracle audits third party support customers at a higher rate than the general estate.
  • The contract clauses decide the outcome. Read seven specific clauses before the cut, not after.
  • Independent advisory pays for itself. The buyer side audit defense is structurally different from the standard Oracle posture.

Provider landscape

Three providers carry the majority of the market. Rimini Street is publicly listed and the largest by revenue. Spinnaker Support sits second. Support Revolution serves the European market.

Third party support providers at a glance

ProviderFoundedHeadquartersStrengthList discount
Rimini Street2005Las VegasLargest, public, broad coverage50%
Spinnaker Support2008DenverManaged services breadth50%
Support Revolution2012Reading, United KingdomEuropean focus, JD Edwards depth50%
Origina2012DublinIBM mainframe plus Oracle bench50%
Oracle Premier Support1977AustinPatches, certification, escalationList

The buyer side fix on provider selection

Score each provider on five dimensions. Patch policy, coverage breadth, escalation depth, geographic reach, and reference base. Rimini Street wins on coverage and references. Spinnaker wins on managed services. Support Revolution wins on European JD Edwards estates.

Five savings drivers

The fifty percent headline is one of five drivers. The full saving compounds when the four secondary drivers stack on top.

Five drivers that build the third party support saving

  • The headline list discount. Fifty percent off Oracle support net license value. The recurring base saving.
  • The compounding uplift avoidance. Oracle adds eight percent every year. The third party contract caps the uplift at two to three percent.
  • The shelfware reset. The cut is the moment to drop unused products. Oracle support charges on the full estate. Third party charges on the in use estate.
  • The version freeze release. Oracle premier support ends at a defined date. Third party support extends indefinitely on the frozen version.
  • The license optimization release. The contract review at the cut is the moment to fix the partition policy, the named user count, and the option deployment.

Five savings drivers across a 10 million dollar Oracle support baseline

DriverYear one savingYear three savingYear five saving
Headline discount$5.0M$5.0M$5.0M
Uplift avoidance$0$1.7M$3.6M
Shelfware reset$1.0M$1.0M$1.0M
Version freeze$0.5M$0.5M$0.5M
Optimization release$0.8M$0.8M$0.8M
Total annual saving$7.3M$9.0M$10.9M

Reinstatement is the structural lock in

The reinstatement clause is the single most important number in any third party support contract. Oracle policy requires payment of the back maintenance for every month the customer was off Oracle support. A penalty of one hundred and fifty percent sits on top.

A five year third party support stay creates a reinstatement bill of fifteen to twenty million dollars on a typical large enterprise account. The buyer side response is to plan the third party support stay as a permanent decision. The reinstatement bill is the moat that protects the saving.

Seven contract clauses

Seven specific clauses decide whether the third party support contract holds under audit pressure. Read each clause in writing before the cut.

Seven clauses to read before the cut

  • Scope of products covered. The exact product list, the version, and the patch set. Anything outside the list reverts to Oracle.
  • Patch development policy. Custom fixes versus regulatory updates. Tax and finance updates run on a different cadence than security patches.
  • Audit cooperation clause. The provider will or will not represent the customer under an Oracle audit. Rimini Street holds an active legal posture.
  • Indemnification language. The provider stands behind the legality of the support work. The customer carries the license compliance separately.
  • Termination and exit terms. Notice period, data return, and the post exit transition. Plan the next move at signing, not at exit.
  • Reinstatement assistance. Some providers help with Oracle reinstatement at end of term. The clause is rarely commercial.
  • Geographic coverage. Follow the sun support, regional escalation, and language coverage. European and APAC estates need explicit language.

The buyer side fix on the seven clauses

Build a clause grid before signing. Each clause sits with a named owner. Each clause maps to a contractual risk. The grid reads back at every annual review of the third party support contract.

Audit posture after the cut

Oracle audits third party support customers at a higher rate. The buyer side posture changes structurally. The license position must hold without the Oracle support backstop.

Three audit posture changes after the cut

  1. The license compliance becomes independent of support. Oracle no longer sees the deployment through the support portal.
  2. The partition policy review becomes binding. VMware, KVM, and Hyper V interpretations must be defensible without Oracle's verbal comfort.
  3. The audit response runs without Oracle's escalation path. An independent audit defense partner is the structural replacement.

Audit posture before and after the third party support cut

DimensionUnder Oracle supportUnder third party support
Audit frequencyEvery three to five yearsEvery two to three years
Support portal dataVisible to OracleCut from the audit data set
Partition policyVerbal Oracle comfortContract clause only
Escalation pathOracle account teamIndependent audit defense
License positionReconciled at renewalHeld permanently in the SAM tool

The third party support cut is a permanent decision. The reinstatement clause makes the return prohibitively expensive. The buyer side response is to plan the cut as a ten year stay, with the audit defense and the license position in place from day one.

Migration calendar

The cut runs cleaner on a twelve month calendar. Notice, vendor selection, contract negotiation, and transition all sit inside one window.

Twelve month migration calendar

  • Months one to three. Build the business case. Score providers. Read the seven clauses. Decide the in scope product list.
  • Months four to six. Negotiate the third party support contract. Lock the audit defense partner. Refresh the SAM tool data.
  • Months seven to nine. Give Oracle notice of non renewal. Run the parallel support overlap. Train the internal team.
  • Months ten to twelve. Cut over to third party support. Document the version freeze. Close the open Oracle tickets.

What to do next

The eight step checklist below is the buyer side starting position to plan the Oracle third party support cut.

  1. Build the business case. Run the five savings drivers across the next five years. Pair with the reinstatement risk.
  2. Score the providers. Rimini Street, Spinnaker, Support Revolution. Score on five dimensions.
  3. Read the seven clauses. Scope, patch policy, audit cooperation, indemnification, termination, reinstatement assistance, geographic coverage.
  4. Refresh the SAM tool. Hold the license position independently of Oracle support data.
  5. Lock the audit defense partner. The buyer side response replaces the Oracle escalation path.
  6. Give Oracle notice of non renewal. Inside the contractual notice window. In writing. With escalation paths defined.
  7. Run the parallel support overlap. Three months of overlap closes the open Oracle tickets cleanly.
  8. Document the version freeze. The frozen version is the support baseline for the duration of the stay.

Frequently asked questions

How much does third party support save versus Oracle?

The headline saving is fifty percent of the Oracle support invoice. The compounding uplift avoidance, the shelfware reset, the version freeze release, and the optimization release add another twenty to forty percent over five years. A 10 million dollar Oracle support baseline drops to roughly 3 million per year by year five.

What is the reinstatement clause and why does it matter?

Oracle policy requires payment of the back maintenance for every month the customer was off Oracle support, plus a penalty of one hundred and fifty percent. A five year stay creates a reinstatement bill of fifteen to twenty million dollars on a typical large enterprise account. The buyer side response is to plan the stay as a permanent decision.

Does Rimini Street write custom fixes?

Rimini Street writes custom fixes and regulatory updates. The provider does not flow Oracle critical patch updates. The buyer side response is to assess the security exposure of the frozen Oracle version and plan compensating controls for the years the customer stays on third party support.

What happens during an Oracle audit on third party support?

Oracle audits third party support customers at a higher rate. The audit defense runs without Oracle's escalation path. An independent audit defense partner is the structural replacement. The contract clauses must hold without the Oracle support backstop.

How long should the parallel support overlap run?

Three months of parallel Oracle and third party support overlap is the typical practice. The overlap closes the open Oracle tickets cleanly, validates the third party support team, and gives the internal team time to learn the new escalation path. The overlap cost runs into the year one business case.

How does Redress engage on third party support transitions?

Redress runs Oracle third party support transitions inside Vendor Shield, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The work covers the business case, the provider score, the seven clauses, the SAM tool refresh, the audit defense partner, and the twelve month migration calendar. Always buyer side, never Oracle paid.

How Redress engages on Oracle third party support

Redress runs Oracle third party support transitions inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. Every engagement is led by a former Oracle commercial executive on the buyer side.

Read the related benchmarking, about us, locations, and contact pages.

Score your Oracle third party support readiness in under five minutes.
Open the Oracle Calculator →
White Paper · Oracle

Download the Oracle ULA Decision Framework.

A buyer side reference on Oracle support, third party support, and the renewal calendar. Includes the reinstatement math, the seven clauses, the partition policy review, the audit defense posture, and the twelve month migration calendar.

Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Oracle support estates. No Oracle influence. No sales kickback.

Oracle ULA Decision Framework

Open the white paper in your browser. Corporate email only.

Open the Paper →
50%
Headline saving
12 mo
Migration window
8%
Oracle uplift
500+
Enterprise clients
100%
Buyer side

The third party support cut is a permanent decision. The reinstatement clause makes the return prohibitively expensive. The buyer side response is to plan the cut as a ten year stay with the audit defense and the license position in place from day one.

Chief Information Officer
European industrial group
More Reading

More from this practice.

Oracle Hub →
Third Party Support Comparison
Oracle · Article
Third Party Support Comparison
Provider score across five dimensions.
16 min read
Oracle ULA Framework
Oracle · White Paper
Oracle ULA Framework
Buyer side ULA framework.
18 min read
Oracle Knowledge Hub
Oracle · Hub
Oracle Knowledge Hub
Master Oracle reference.
18 min read
Oracle Advisory Services
Oracle · Service
Oracle Advisory Services
The Oracle practice.
10 min read
Common Oracle Pitfalls
Oracle · Article
Common Oracle Pitfalls
Six recurring Oracle traps.
16 min read
Editorial photograph of enterprise contract negotiation strategy

Oracle support cuts run cleaner with buyer side preparation.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

Oracle intelligence, monthly.

Third party support cuts, reinstatement math, the seven clauses, the partition policy review, and the audit defense posture across every Oracle engagement we run.