A comprehensive guide for CIOs and IT leaders evaluating third-party Oracle support — covering cost savings of 50%+, security and compliance strategies, vendor selection, licensing considerations, and a step-by-step transition framework.
Third-party support for Oracle software refers to maintenance and support services provided by independent vendors — rather than Oracle itself. Instead of renewing support with Oracle, a customer contracts a certified third-party provider (such as Rimini Street, Spinnaker Support, or Support Revolution) to receive help desk support, bug fixes, patches, and regulatory/tax updates for their Oracle products.
These third-party firms employ teams of Oracle experts who take over the support role at significantly lower cost. Importantly, they operate without Oracle's direct involvement — they cannot access Oracle's proprietary source code or official patch releases. This difference underpins both the advantages and trade-offs of the model.
Research indicates that third-party support deals have seen rapid adoption, with nearly 4,000 enterprises now using independent support for Oracle and SAP products. The model has evolved from a niche alternative into a viable, mainstream strategy endorsed by major industry analysts.
CIOs typically consider third-party support for five reasons: cost savings (Oracle's annual support fees are ~22% of licence costs with yearly uplifts — third-party providers charge about 50% less), extended product life (continuing support for legacy versions beyond Oracle's support window), flexibility and control (upgrading on your own timeline), better service quality (direct access to senior engineers vs. Oracle's tiered ticket system), and support for customisations (Oracle declines to troubleshoot custom code; third-party vendors will).
Once you leave Oracle support, you lose the right to download official updates and fixes. Third-party providers compensate with their own custom fixes, virtual patching, and security monitoring — but you will not receive Oracle-issued patches or version upgrades. Customers must accept that they will remain on their current version. For organisations running mature, stable Oracle systems, this is typically an acceptable trade-off. For organisations planning major Oracle upgrades in the near term, it is not.
The most common concern CIOs raise: without Oracle's security patches, how do you keep systems secure and compliant? Third-party support vendors have developed robust multi-layered security strategies that go beyond patching alone.
| Security Layer | How Third-Party Providers Address It |
|---|---|
| Virtual Patching | Analyse vulnerabilities and create tailored code fixes or configuration changes that close security gaps without altering Oracle source code |
| Compensating Controls | Implement triggers, constraints, firewall rules, and intrusion detection rules to prevent exploitation of known flaws |
| Proactive Monitoring | Continuous 24/7 monitoring for unusual activity or known attack patterns, with immediate response capabilities |
| Security Advisories | Issue vendor-neutral security bulletins alerting clients to new threats with recommended mitigation steps |
| Regulatory Updates | Deliver tax, legal, and regulatory updates (payroll tables, VAT changes, financial reporting) to keep Oracle ERP systems compliant |
| Zero-Day Protection | Leading providers deploy virtual patches immediately when new threats emerge, without waiting for quarterly patch cycles |
To date, there have been no widespread security incidents attributed to organisations using third-party Oracle support. Thousands of enterprises — including banks and government agencies — operate Oracle systems successfully without Oracle's direct patches by utilising third-party security measures. However, CIOs should thoroughly vet any provider's security capabilities, certifications (ISO 27001, SOC audits), and zero-day response processes before committing.
Review all Oracle support agreements, renewal dates (many align with Oracle's 31 May fiscal year-end), and the "matching service levels" policy — which requires you to drop support for an entire licence set, not just a subset. Inventory your full Oracle footprint: products, versions, customisations, and pending patches. Assess how reliant your team is on My Oracle Support — download any critical documentation or patches while still entitled.
Evaluate vendors on Oracle product expertise, breadth of services (break/fix, tax updates, security monitoring, advisory), SLA terms (response times, dedicated engineers), security protocols and compliance certifications, contract flexibility, and financial stability. The three leading providers are Rimini Street, Spinnaker Support, and Support Revolution. Request case studies in your industry, speak with references, and consider a phased pilot engagement.
Coordinate the cutover to avoid gaps — end Oracle support and start third-party support the next day. Transfer system knowledge (architectures, customisations, open issues) via onboarding workshops. Conduct a final licensing review and archive all Oracle patches and documentation you're entitled to. Inform stakeholders and establish clear internal communication about new support contacts and procedures.
Formally notify Oracle of non-renewal. Log a test ticket within the first week to validate processes. Monitor service quality closely for the first 3–6 months: are SLAs being met? How is turnaround on fixes? Schedule regular check-ins with the vendor. Document improvements and savings for stakeholder reporting. Close Oracle MOS access to prevent accidental post-support downloads.
Be prepared for Oracle pushback. Oracle sales reps may warn of dire consequences, cite contractual clauses, or offer last-minute discounts (typically 10–15%, which won't match the 50%+ savings of third-party support). Do not let fear, uncertainty, and doubt derail a well-researched plan. Rely on what your contracts actually say — third-party support is legal and well-established.
Switching support providers does not change your underlying Oracle licence agreements. You must adhere to all licence terms even without Oracle-provided support. This is the area that demands the most rigour.
Oracle may initiate a licence audit after a customer leaves support. While this is not significantly more likely just because you switched, it is a possibility. The best defence: conduct a comprehensive self-audit or engage an independent Oracle licensing consultant before the transition. Discover and address compliance issues proactively — a "true-up then exit" approach is far less expensive than being found non-compliant during an Oracle audit.
| Vendor | Notable Strengths | Considerations |
|---|---|---|
| Rimini Street | Largest provider globally; 2,800+ clients; broadest Oracle product coverage; proactive support model; global 24/7 operations; ~50% cost reduction | Ongoing legal history with Oracle (operations continue unaffected); may be less flexible on pricing |
| Spinnaker Support | Highly skilled team including former Oracle developers and DBAs; flexible contracts and pricing; high-touch personalised service; growing client base | Smaller scale than Rimini Street; some customers prefer the larger provider's breadth of resources |
| Support Revolution | Aggressively competitive pricing; UK-based with strong EMEA/public sector presence; cost-effective delivery model using offshore engineers | Smaller teams with heavy contractor use — scrutinise support depth for complex issues; fewer Fortune 500 references |
Leverage competition between vendors. Invite Rimini Street and Spinnaker Support to both conduct assessments and provide quotes — then use the competitive dynamic to negotiate better pricing, SLAs, or service inclusions. Since third-party support is a long-term partnership, choose a vendor you're confident in for the full remaining life of your Oracle systems.
Need help comparing third-party support providers? We provide independent vendor assessments.
Third-Party Advisory Service →For most CIOs, the primary appeal is dramatic cost reduction. Oracle's maintenance fees — typically 22% of licence cost annually, compounding with 3–8% yearly increases — often exceed the original licence cost within a decade. Third-party support cuts those fees roughly in half, yielding immediate budget relief that compounds over time.
| Benefit Category | Detail | Typical Impact |
|---|---|---|
| Immediate cost reduction | Annual support fees drop ~50% from day one | Millions freed for innovation budgets |
| Elimination of annual uplifts | Flat, predictable pricing vs. Oracle's 3–8% yearly increases | 60–70% cumulative savings over 5 years |
| Shelfware elimination | Third-party contracts exclude unused licences Oracle still charges for | Further cost reduction beyond the headline 50% |
| Avoided upgrade costs | Defer or skip multi-million-pound upgrade projects | Capital avoidance of $5M+ per deferred upgrade |
| Improved support quality | Direct-to-engineer model with faster resolution times | Reduced downtime, higher user satisfaction |
| Vendor independence | Freedom from Oracle's upgrade cycle and lock-in | Stronger negotiating leverage for remaining Oracle products |
"We treated the licensing review as part of the project — after that, we were confident and moved forward. The savings were immediate, the service quality improved, and we finally had control over our own upgrade timeline."— CIO, enterprise third-party support client
| # | Business Case Element | What to Present |
|---|---|---|
| 1 | Hard financial savings | "By switching support for X, Y, and Z Oracle systems, we will save $N million over 3 years — enough to fund [specific initiative]" |
| 2 | Risk mitigation | Explain the provider's security approach, note that thousands of enterprises (including banks) use this model successfully |
| 3 | Peer validation | Reference similar organisations in your industry that have switched and thrived — cite Gartner endorsement |
| 4 | Service improvement | Describe the dedicated engineer model, faster SLAs, and support for customisations Oracle doesn't cover |
| 5 | Compliance assurance | Confirm pre-switch licence review, legal due diligence, and ongoing self-audit processes are in place |
| 6 | Opportunity cost | "Staying on Oracle support costs $X/year for declining value on stable systems — that money funds innovation elsewhere" |
See how Redress Compliance helps enterprises transition to third-party Oracle support
Download our independent research on Oracle licensing, audit defence, ULA strategies, and third-party support
Share your Oracle environment details and we'll provide a scoping proposal — including a compliance risk assessment, vendor comparison, and projected savings — typically within 48 hours.