Third-party Oracle support can reduce your Oracle support bill by 50–60% annually. But the decision carries legal, contractual, and strategic risks that must be fully understood before switching. This guide covers the providers, the savings, the risks, and the decision framework for enterprise organisations evaluating third-party Oracle support in 2026.
Third-party Oracle support refers to software maintenance and support services for Oracle products — principally Oracle Database, Oracle E-Business Suite, Oracle Fusion Middleware, and older Oracle technology products — provided by an independent company rather than Oracle itself. The two dominant providers in this market are Rimini Street and Spinnaker Support, though smaller regional providers also exist.
These providers offer software support that typically includes: technical support for product bugs and issues; custom security patches (developed by the third-party provider rather than Oracle); interoperability updates for new operating systems, browsers, and tax/regulatory changes; and a named support engineer model with faster response times than Oracle's tiered support queue. For a broader view of Oracle support cost reduction strategies, including options within Oracle's own support offerings, see our Oracle support cost reduction guide.
The business case for third-party support is primarily economic: Oracle charges 22% of net licence value annually for Premier Support, which escalates 4–5% per year. Third-party providers typically charge 50% of Oracle's support cost — delivering an immediate 50% saving on the Oracle support line, which for large Oracle estates can amount to millions of pounds or euros annually. This article is part of our broader Oracle license negotiation pillar guide.
Oracle pursued litigation against Rimini Street for a period of years, resulting in judgments and settlements relating to how Rimini Street developed its support materials. Rimini Street has subsequently changed its support delivery model (the "Rimini Street Process 2.0"). The legal landscape for third-party Oracle support has evolved significantly — any organisation considering this option should seek current legal advice rather than relying on older assessments.
The two major third-party Oracle support providers have different histories, product coverage, and delivery models. Understanding the differences is essential for evaluating which provider — if either — is appropriate for your Oracle environment.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
| Factor | Rimini Street | Spinnaker Support |
|---|---|---|
| Founded | 2005 (NASDAQ listed) | 2012 |
| Oracle products covered | Database, E-Business Suite, JD Edwards, PeopleSoft, Fusion Middleware, Siebel | Database, E-Business Suite, JD Edwards, PeopleSoft, Siebel, Hyperion |
| Support model | Named primary support engineers; 24×7 availability | Named primary support engineers; strong mid-market focus |
| Security patches | Custom patches for unsupported versions | Custom patches for unsupported versions |
| Regulatory updates | Tax, legal, regulatory for E-Business Suite | Tax, legal, regulatory updates covered |
| Litigation history | Significant Oracle litigation; process changes made | No significant Oracle litigation to date |
| Typical cost saving | 50% of Oracle support cost | 50–60% of Oracle support cost |
| Best suited for | Large enterprise Oracle estates; Database-heavy | Mid-market and Oracle applications customers |
The economics of third-party Oracle support are straightforward in principle. Oracle charges annual support at approximately 22% of net licence fee, with an escalation clause that typically adds 4–5% annually. On a £5m annual Oracle support bill, switching to a third-party provider at 50% of Oracle cost saves £2.5m in year one, and the saving compounds as Oracle support would have continued to escalate while third-party rates are typically fixed or lightly escalated.
The complete cost model must also account for: the back-support payment required if you ever return to Oracle (see the section on switching back below); any Oracle audit activity that results from the switch and the cost of resolving it; the cost of the legal review and advisory work required before switching; and the opportunity cost of any Oracle commercial relationships that are affected by the decision. With these factors included, the net present value of third-party support varies significantly by organisation. For large, stable Oracle estates with no near-term plans to upgrade to Oracle cloud products, the NPV is typically strongly positive. For organisations with active Oracle Cloud Fusion migration plans, the analysis is more nuanced.
The risks of third-party Oracle support fall into four categories: legal risk, contractual risk, technical risk, and strategic risk. Understanding each is essential before making the decision.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
Legal risk relates to the ongoing evolution of case law and Oracle's litigation strategy. Organisations should obtain current legal advice from a specialist in software licensing law — the legal landscape has changed since the original Rimini Street litigation, and current legal advice may differ from assessments made even two to three years ago.
Contractual risk relates to provisions in the Oracle OTLA and support agreements that may be affected by a third-party support decision. Some Oracle agreements contain provisions about maintaining Oracle support as a condition of certain entitlements; others have audit provisions that are triggered by support termination. The current OTLA and all relevant order forms should be reviewed before any third-party support decision. Our Oracle OTLA negotiation guide covers the relevant contractual provisions in detail.
Technical risk relates to the ability of the third-party provider to support complex Oracle environments — particularly highly customised Oracle E-Business Suite deployments or Oracle Database environments with unusual configurations. Third-party providers are generally effective for well-understood product configurations but may have limitations in highly customised or bleeding-edge environments.
Strategic risk relates to the impact on the Oracle commercial relationship and future upgrade paths. Moving to third-party support effectively freezes the Oracle product version — organisations on third-party support cannot receive Oracle patches, which means future upgrades to newer Oracle versions require returning to Oracle support and paying the back-support fees. This is manageable for organisations that have consciously decided to remain on current Oracle versions, but is a significant constraint for organisations that plan to continue their Oracle product roadmap.
Evaluating third-party Oracle support? Get independent advisory before you decide.
Oracle consistently uses the threat of audit activity as a deterrent against third-party support decisions. In practice, many organisations that have switched to third-party support report increased Oracle audit attention in the months following the switch — Oracle's LMS team will contact customers to conduct a licence review. This is not guaranteed, but it is common enough that organisations should have their compliance position fully verified before switching. Our Oracle audit defense playbook covers how to prepare for and manage an Oracle audit.
Oracle's commercial team will also typically attempt to retain customers considering third-party support by offering support discount deals — sometimes quite substantial ones. These Oracle counter-offers should be evaluated carefully: a temporary discount to Oracle Premier Support is not the same as a permanent cost reduction, and Oracle's commercial team may use the negotiation to extract other concessions. Oracle's willingness to discount support meaningfully is itself evidence that third-party support is an effective negotiating tool — see the next section on using third-party support as leverage.
Third-party Oracle support is most clearly appropriate when several conditions are met simultaneously: the Oracle products in scope are stable, well-understood, and not subject to active Oracle development (Oracle Database versions prior to the most recent release, mature versions of E-Business Suite or PeopleSoft); the organisation has no near-term plan to migrate to Oracle Cloud applications or OCI; the compliance position is clean and fully documented; and the annual Oracle support saving is material relative to the advisory and legal cost of making the switch.
Third-party support is less clearly appropriate when: the organisation is actively on an Oracle cloud migration path; the Oracle products are subject to significant customisation that may challenge third-party support capabilities; the organisation has a complex Oracle commercial relationship with ongoing ELA negotiations where the third-party support decision could damage negotiating position; or the legal review reveals contractual provisions that make support termination commercially risky.
The decision framework should be evaluated with specialist independent advice — not from Oracle's commercial team, and not from the third-party support providers themselves who have a commercial interest in winning the business. Independent Oracle advisory firms, including those ranked in our Oracle negotiation firm rankings, can provide an objective assessment. The software audit defense buyer's guide and Oracle license optimization guide provide additional context for the broader Oracle cost reduction picture.
One of the most effective uses of third-party Oracle support is as a negotiation lever with Oracle itself — without necessarily switching. Demonstrating credibly that the organisation has evaluated third-party support, received a proposal from Rimini Street or Spinnaker, and is prepared to make the switch creates genuine commercial urgency for Oracle to offer meaningful support discounts or commercial concessions.
This approach works because Oracle's commercial team understands that a lost support contract is very difficult to win back — once an organisation leaves Oracle support, the switching cost (back-support fees) makes return commercially painful, and the customer may never return. Oracle's desire to protect the support revenue stream means that credible third-party support leverage can unlock support discounts of 20–35% — not as deep as an actual switch, but achievable without the legal and strategic complexity.
For this approach to be effective, the threat must be credible — Oracle's commercial team is experienced at identifying customers who are merely posturing. Having a real third-party support proposal in hand, a board-level commitment to evaluate the option seriously, and a clear timeline creates the credibility required. This tactic is best executed as part of a broader Oracle ELA or renewal negotiation — see our Oracle ELA renewal guide for how to integrate third-party support leverage into a comprehensive negotiation strategy.
The prospect of returning to Oracle Premier Support after a period on third-party support is an important consideration in the initial decision. Oracle's standard position is to require back-support fees — payment of the Oracle support fees that would have been due had the customer remained on Oracle support throughout the third-party support period. This retroactive payment, combined with the catch-up to current Oracle support rates, can be substantial.
Back-support fee negotiations are possible for organisations with significant Oracle commercial relationships, and Oracle's willingness to waive or reduce back-support requirements as part of a broader commercial event (such as an OCI migration commit or a new ELA) should be factored into the financial model. However, organisations that assume they can return to Oracle support cost-free are making a significant financial error in their modelling. The full back-support cost — or a realistic estimate of a negotiated partial payment — must be included in the NPV calculation for any third-party support decision.
For organisations considering third-party support as part of a broader Oracle optimisation strategy, see our Oracle license optimization tips for the full range of Oracle cost reduction options, many of which can be pursued without the complexity of a third-party support switch. Download our free Oracle licensing guide for a comprehensive reference on Oracle commercial strategy.
Third-party support can deliver significant savings — but the decision requires careful legal, contractual, and strategic analysis. Independent Oracle advisory ensures you make the right call for your organisation.