A complete guide for CIOs evaluating independent Oracle support — covering 50%+ cost savings, security strategy, vendor selection, licensing compliance, and a step-by-step transition framework.
Third-party support for Oracle software means independent vendors — not Oracle — provide maintenance and support for your Oracle products. Instead of renewing directly with Oracle, you contract a provider such as Rimini Street, Spinnaker Support, or Support Revolution to deliver help desk support, bug fixes, custom patches, and regulatory updates.
These firms employ Oracle-certified engineers who handle your support needs at significantly lower cost. They operate without Oracle’s direct involvement and cannot access Oracle’s proprietary source code or official patch releases. That distinction shapes both the advantages and the trade-offs.
Adoption has accelerated sharply. Nearly 4,000 enterprises now use independent support for Oracle and SAP products. The model has evolved from niche alternative into a mainstream strategy endorsed by major industry analysts.
💡 Why CIOs Make the Switch
Cost savings. Oracle annual support runs ~22% of licence value with 3–8% yearly uplifts. Third-party providers charge roughly half — immediate, compounding savings with no escalation.
Extended product life. Support your current Oracle versions indefinitely. No forced upgrades when Oracle ends a version’s support window.
Upgrade on your timeline. Control your own roadmap instead of Oracle’s commercial calendar.
Better service quality. Direct access to senior engineers vs Oracle’s tiered ticket system with standardised, slow responses.
Custom code support. Oracle will not troubleshoot customisations. Independent providers will.
This decision is not purely about price. It covers service model, security approach, and how much control you retain over your technology roadmap.
| Dimension | Oracle Premier Support | Third-Party Support |
|---|---|---|
| Annual cost | ~22% of licence value + 3–8% yearly increases | ~50% less than Oracle with flat, predictable pricing |
| Patches & updates | Official patches, Critical Patch Updates, version upgrades | Custom fixes, virtual patching, compensating security controls |
| Support model | Tiered ticket system — often slow, standardised responses | Direct-to-engineer model — faster resolution and accountability |
| Custom code | No support for custom code or tailored integrations | Full support for customisations and bespoke solutions |
| Version control | Forces upgrade when a version reaches end-of-support | Supports legacy versions indefinitely — no forced upgrades |
| Security patching | Quarterly CPU release cycle from Oracle | Proactive monitoring; zero-day response without quarterly wait |
| MOS access | Full My Oracle Support portal access retained | MOS access terminates — archive all patches before switching |
Critical trade-off — understand this before committing. Once you leave Oracle support, you lose the right to download official patches or access My Oracle Support. Third-party providers compensate with custom fixes and virtual patching, but you will not receive Oracle-issued patches or version upgrades. You remain on your current version. For organisations running stable, mature Oracle systems this is typically acceptable. For those planning near-term Oracle upgrades, it is not. This is the single most important factor in the decision.
The most common CIO concern: without Oracle’s security patches, how do you keep systems secure and remain compliant? Reputable third-party providers have built multi-layered security strategies that address this systematically.
| Security Layer | How Third-Party Providers Address It |
|---|---|
| Virtual Patching | Analyse CVEs and develop tailored code fixes that close security gaps without altering Oracle source code |
| Compensating Controls | Implement triggers, constraints, firewall rules, and intrusion detection to prevent exploitation of known vulnerabilities |
| Proactive Monitoring | 24/7 monitoring for unusual activity or known attack patterns with immediate response capabilities |
| Regulatory Updates | Deliver tax, legal, and regulatory updates (payroll, VAT, financial reporting) to keep Oracle ERP applications compliant |
| Zero-Day Response | Leading providers deploy virtual patches immediately on new threats — no waiting for Oracle’s quarterly CPU cycle |
💡 Security track record. To date, there have been no widespread security incidents attributed to organisations using third-party Oracle support. Thousands of enterprises — including regulated banks and government agencies — operate Oracle systems without Oracle’s direct patches. Vet any provider’s security capabilities, certifications (ISO 27001, SOC 2), and zero-day response processes before committing. Not all providers are equal in security depth.
A well-executed transition requires preparation, sequencing, and internal alignment. The organisations with the fewest post-switch issues treat this as a formal project, not a routine procurement decision.
Expect Oracle pushback. Oracle sales reps may warn of dire consequences, cite contractual clauses, or offer last-minute discounts — typically 10–15%, which will not match the 50%+ savings available through third-party support. Do not let fear, uncertainty, and doubt derail a well-researched plan. Third-party support is legal, well-established, and used by thousands of enterprises globally.
Switching support providers does not change your Oracle licence agreements. You remain bound by all licence terms without Oracle-provided support. This is where the most expensive mistakes happen. Rigour here is non-negotiable.
Conduct an independent licence review before transitioning. Resolve any gaps proactively. Discovering a compliance issue mid-transition when Oracle is already aware you are leaving is the worst possible timing.
Oracle requires you to drop support across an entire licence set, not a subset. You cannot selectively retain Oracle support for some products while moving others to a third-party provider within the same agreement. Understand this before scoping the transition.
Do not transition during an active ULA or PULA. Certify the ULA first to crystallise your licence position, then exit Oracle support. Leaving Oracle support before certification creates significant licensing risk that is difficult and expensive to resolve.
Download all patches, updates, and documentation you are entitled to before your MOS access closes. Once support lapses, you cannot retrieve these materials. Archive systematically and document what you have downloaded and when.
Compliance remains your responsibility after switching. Monitor your Oracle deployments periodically — new installations, virtualisation changes, and processor upgrades can all affect your licence position. Do not assume compliance remains static.
Oracle may audit after you leave their support. Maintain organised records of all licence entitlements, deployment logs, and MOS access history. Be prepared to respond quickly and accurately. Gaps in documentation are often more damaging than the underlying issue.
Do not access My Oracle Support or download anything after your support termination date. This creates serious legal exposure under Oracle’s licence terms. Train your IT team on this before the transition date and revoke MOS access credentials immediately.
True-up then exit. Our advisory recommendation: resolve all licence compliance issues before transitioning, not after. The “true-up then exit” approach means Oracle cannot weaponise a compliance gap during or after your departure. Engage an independent licensing consultant to review your position before serving Oracle with notice.
Three vendors dominate the independent Oracle support market. Each has distinct strengths, pricing approaches, and risk profiles. Evaluating all three competitively is the only reliable way to identify the best fit.
| Criterion | Rimini Street | Spinnaker Support | Support Revolution |
|---|---|---|---|
| Client base | 2,800+ globally (largest) | Growing mid-market base | EMEA focus, growing |
| Oracle products | Database, EBS, JDE, PeopleSoft, Siebel, Hyperion, WebLogic | Database, EBS, JDE, PeopleSoft, Siebel | Database, EBS (core products) |
| Typical savings | ~50% vs Oracle support fees | 50%+ with flexible contract terms | Aggressive pricing for qualifying scope |
| Key strength | Largest scale, broadest coverage, proactive security model | Former Oracle engineers, high-touch service, flexibility | Cost competitiveness, EMEA and public sector expertise |
| Key risk | Ongoing legal history with Oracle; less pricing flexibility | Smaller scale than Rimini; fewer Fortune 500 references | Narrower product coverage; offshore delivery model |
| Best suited for | Large enterprise, complex multi-product environments | Mid-market, complex customisations, high-touch preference | Straightforward Database or EBS environments, EMEA |
💡 Use competitive tension. Never approach a single vendor exclusively. Inviting all three creates genuine competition on price, terms, and SLAs — consistently delivering better outcomes than single-vendor negotiations. Redress provides independent assessments of all three providers without vendor partnerships or referral fees.
Third-party support delivers financial benefits across several dimensions. Understanding all of them — not just the headline support reduction — builds the strongest board-level business case.
| Savings Category | Detail | Financial Impact |
|---|---|---|
| Immediate support reduction | Third-party fees typically 50% below Oracle Premier Support fees | High (Year 1) |
| Elimination of annual uplifts | Oracle uplifts 3–8% annually; third-party fees are flat — compounding gap builds to 60–70% over 5 years | High (compound) |
| Shelfware elimination | Oracle’s matching service levels policy prevents targeted drops; third-party support allows renegotiated scope | Medium (varies) |
| Avoided upgrade costs | Oracle often forces upgrades at end-of-support. Third-party support defers these indefinitely | Very high ($5M+) |
| Improved service quality | Direct-to-engineer model reduces resolution time and internal labour cost | Medium (operational) |
| Negotiation leverage | A credible third-party option can force Oracle to offer 15–30% discounts at renewal even if you stay | High (strategic) |
For a typical organisation spending $2M annually on Oracle support, switching to third-party saves approximately $1M per year from day one. Over five years, compounding uplifts increase total savings to $6–7M on that same baseline — before counting avoided upgrade costs, which often exceed the cumulative support savings.
Yes. The legality has been confirmed by courts in multiple jurisdictions, most notably in Oracle v Rimini Street. Oracle cannot cancel your software licences for using a competing support provider. Your perpetual licence and your support contract are legally distinct agreements. What you give up is access to My Oracle Support and Oracle-issued patches — not your right to run the software.
Oracle retains audit rights regardless of your support provider. Organisations that exit Oracle support are logical audit targets. The best defence is a clean compliance position before you leave. Conduct a thorough independent licence review before transitioning, resolve any gaps proactively, and maintain well-organised records. A compliant organisation has nothing to fear from an audit.
Yes, but it is expensive. Oracle requires payment of all missed support fees (typically backdated to the date of cancellation) plus a reinstatement fee, and you must upgrade to a supported version. In practice, the reinstatement cost eliminates most or all of the savings achieved, which is why the vast majority of enterprises that switch to third-party support do not return to Oracle. Once the decision is made, plan to maintain it for at least 3–5 years to realise full financial benefit.
Yes — this is critical. Do not transition to third-party support while you have an active Unlimited Licence Agreement (ULA) or Perpetual ULA. Certify the ULA first to crystallise your licence entitlements, then exit Oracle support. Attempting to transition during an active ULA creates complex compliance risks and may undermine your certification position. Engage an experienced Oracle licensing advisor before taking any steps if you hold a ULA or PULA.
Redress provides independent advisory across all phases: pre-switch compliance audit, vendor evaluation (all three providers), contract negotiation, cutover planning, and ongoing compliance monitoring. We have no commercial relationships with Rimini Street, Spinnaker Support, or Support Revolution. Our only interest is securing the best outcome for your organisation. Fixed-fee engagements. We do not earn referral fees.
Coverage varies. Rimini Street offers the broadest scope: Oracle Database, E-Business Suite, JD Edwards, PeopleSoft, Siebel, Hyperion, and WebLogic. Spinnaker covers Oracle Database, EBS, JDE, PeopleSoft, and Siebel. Support Revolution focuses primarily on Oracle Database and EBS. Oracle Cloud applications have limited or no third-party coverage — independent support is most applicable to on-premise and perpetual-licence environments.
A full transition typically takes 3–6 months. Allow 4–8 weeks for a pre-switch compliance audit, 4–8 weeks for vendor evaluation and commercial negotiation, 2–4 weeks for internal cutover planning, and 1 day for the actual support switchover. Rushing any phase — particularly the compliance audit — creates risk. The organisations that experience the smoothest transitions are those that give the process adequate time and engage external expertise early.