Breaking Free From Oracle Support

Oracle's support renewal model is designed to extract maximum value from customers who do not actively manage the relationship. The default 8% annual increase compounds silently in multi-year contracts, and Oracle's account teams are skilled at presenting renewals as straightforward administrative events that simply require a signature. For many organisations, Oracle support has become one of the largest line items in the IT budget — despite the fact that the organisation has not upgraded its Oracle software in years and derives diminishing value from Oracle's support organisation.

Breaking free from Oracle support is not simply about cost reduction. Organisations working with Oracle licensing advisory specialists typically achieve 20–40% better outcomes than those negotiating unilaterally. It is about recovering commercial agency in a vendor relationship that Oracle has structured to be as passive and automatic as possible for the customer. Whether your goal is to move off Oracle support entirely, negotiate a materially better renewal, or simply understand your options before your next renewal conversation, this guide covers every available path.

Why Oracle Support Costs Are Out of Control

The mechanics of Oracle support cost escalation are worth understanding in detail before evaluating alternatives. Oracle's standard perpetual licence contract permits annual support fee increases of up to 8% per year. Unlike many enterprise software vendors that have moved to CPI-linked or fixed increases, Oracle has maintained its right to increase support fees by up to 8% annually regardless of inflation, regardless of whether the software has been updated, and regardless of the customer's actual usage of Oracle's support services.

For a large enterprise paying £5 million per year in Oracle support, an uncapped 8% annual increase produces support costs of £7.35 million in year five — a 47% increase over five years on an estate that has not grown. Over ten years, the same £5 million starting point reaches £10.8 million annually. This compounding trajectory, multiplied across large Oracle estates with database, middleware, application, and Java licences, represents one of the most significant structural cost problems in enterprise IT today.

The additional dimension is Oracle's use of support renewal pressure as an audit and compliance lever. Customers who have allowed their Oracle estate to drift out of licence compliance are in a weaker position to negotiate support reductions. Proactive Oracle ULA advisory and compliance remediation before renewal negotiations materially improves the outcome., because Oracle can introduce compliance findings as a counter to any support cost reduction discussion. Our Oracle audit defence specialists regularly identify and correct compliance gaps before negotiations begin. This makes proactive licence compliance management — a prerequisite for any effective Oracle support cost strategy — especially important to establish before beginning any negotiation.

Third-Party Oracle Support: The Primary Alternative

How Third-Party Support Works

Third-party Oracle support providers — principally Rimini Street and Spinnaker Support, with Support Revolution as an additional option — provide maintenance and support services for Oracle products at fees typically 30 to 50 percent below Oracle's annual support rate. These providers support the Oracle versions you are currently running without requiring upgrades. They deliver tax and regulatory updates, custom code support, interoperability support, and issue resolution — services that comparable to Oracle's own support for organisations that are not actively upgrading their Oracle products.

Third-party support is legally available to Oracle customers. Oracle's licence agreements permit customers to use third-party support providers, provided that the underlying software licences remain valid and the customer continues to comply with Oracle licence terms. The legal basis for third-party support has been tested in multiple jurisdictions through Oracle's litigation against Rimini Street; the outcome has consistently been that third-party support itself is legal, though specific practices of individual providers have been subject to scrutiny.

Rimini Street: Market Leader, Higher Risk Profile

Rimini Street is the largest and most widely known third-party Oracle support provider, having founded the Oracle third-party support category in 2005. Rimini Street claims immediate savings of up to 50% on annual Oracle maintenance fees. The organisation supports Oracle Database, E-Business Suite, PeopleSoft, JD Edwards, Siebel, and other Oracle products. Its service model is comprehensive and its support organisation is significantly larger than most competitors.

However, Rimini Street carries an elevated legal risk profile due to its extended litigation history with Oracle. Oracle sued Rimini Street for intellectual property infringement, and while Rimini Street has operated continuously throughout this litigation, organisations considering Rimini Street should understand the legal history and the ongoing nature of the Oracle-Rimini relationship. This does not make Rimini Street an invalid choice, but it does make due diligence on the specific support practices and contractual protections important before commitment.

Spinnaker Support: Lower Risk, Smaller Scale

Spinnaker Support is the second major global third-party Oracle support provider, offering support for Oracle Database, Oracle E-Business Suite, JD Edwards, Siebel, and Oracle Middleware products. Spinnaker typically offers savings of 50 to 62 percent compared to Oracle's annual support rates and positions itself on a lower-risk legal profile than Rimini Street. For organisations where the legal risk dimension of the Rimini Street relationship is a primary concern, Spinnaker provides a viable and credible alternative with a strong service track record.

What Third-Party Support Does Not Provide

Third-party support is not an appropriate choice for all organisations. It is specifically unsuitable for organisations that plan to upgrade their Oracle products in the near term: once a customer moves to a third-party support provider, returning to Oracle support for a new version upgrade requires re-engagement with Oracle at potentially unfavourable terms, as Oracle may classify the period off support as a lapse. Third-party support also does not provide access to Oracle's online support portal, new product patches (beyond the version in service at the time of transition), or new feature updates. For organisations actively evolving their Oracle technology stack, Oracle support remains the appropriate choice.

Using the Exit Threat as Oracle Negotiation Leverage

Even for organisations that ultimately choose to remain on Oracle support, the credible preparation of a third-party support migration is one of the most powerful Oracle negotiation tools available. Oracle account teams are instructed to retain customers on Oracle support, and the economic value of retaining a large Oracle support contract consistently motivates concessions that cannot be achieved through price negotiation alone.

Effective use of the exit threat requires genuine preparation. An Oracle account team that hears a customer mention third-party support in passing during a renewal conversation will treat it as a positional tactic. An Oracle account team that receives a written notification that the organisation has engaged Rimini Street or Spinnaker for a detailed proposal, received board approval to proceed with transition if Oracle does not cap its uplift, and has a migration timeline responds fundamentally differently. The preparation cost is modest; the resulting concessions — on uplift caps, on multi-year pricing, on payment terms — are consistently material.

The negotiation framework for using the exit threat effectively involves: completing a genuine third-party support evaluation and obtaining a detailed proposal; presenting that proposal internally to gain board-level approval to proceed if Oracle does not respond; and then informing Oracle of the approved alternative in a commercial conversation timed to Oracle's fiscal Q4 window, when Oracle account teams face maximum pressure to retain existing support revenue. Oracle's fiscal year ends May 31, making March through May the most effective window for support cost negotiations.

Self-Support: The Alternative for Technically Capable Organisations

For organisations running Oracle products on stable configurations where external patch delivery is the primary support requirement, self-support is a viable cost reduction strategy. Self-support involves withdrawing from Oracle's annual support contract while maintaining internal expertise for the Oracle products in use. The organisation retains access to patches and security updates accumulated prior to the support withdrawal date, but does not receive new Oracle patches going forward.

Self-support is most appropriate for Oracle products where the security and regulatory update requirement is low, the product is scheduled for decommission within a defined timeframe, or the organisation has sufficient internal expertise to manage the product without external support. It is not appropriate for Oracle products running mission-critical functions where regulatory compliance updates are mandatory, or where Oracle-specific technical issues are likely to require active vendor engagement.

The primary risk of self-support is re-engagement cost. If the organisation subsequently needs to return to Oracle support — due to a product issue that exceeds internal capability, a mandatory security patch requirement, or a regulatory update — Oracle will typically require payment of backdated support fees for the unsupported period plus reinstatement fees. These reinstatement costs must be factored into any self-support cost-benefit analysis.

Cloud Migration as an Oracle Support Exit Path

Migration to cloud-native alternatives — Oracle Cloud SaaS, competitive SaaS applications, or cloud-native open-source replacements — eliminates Oracle on-premises licence and support obligations entirely over time. For organisations running Oracle E-Business Suite, PeopleSoft, or JD Edwards on ageing on-premises infrastructure, migration to Oracle Fusion Applications SaaS or a competitive SaaS alternative (Workday for HR, SAP S/4HANA Cloud for ERP) replaces the perpetual licence and annual support model with a subscription that includes all support, updates, and new feature access.

Cloud migration as an Oracle support exit strategy requires a multi-year programme and significant organisational investment. It is not a quick fix for the next support renewal cycle. However, it is the only path that permanently eliminates Oracle's annual support uplift mechanism from a significant portion of the portfolio, and the long-term financial trajectory of Oracle SaaS or competitive SaaS consistently beats the compounding Oracle support cost trajectory over a five-to-seven-year horizon.

For Oracle Database specifically, migration to Oracle Database@Azure, Oracle Database@AWS (with appropriate BYOL licences), or Aurora PostgreSQL for compatible workloads can significantly reduce or eliminate traditional on-premises Oracle support obligations over time. See the Oracle licensing knowledge hub for related guides, or our guide to BYOL vs licence-included on Azure for a detailed analysis of Oracle Database cloud economics.

The Oracle Support Reduction Playbook

For organisations that are not ready for a full third-party support transition but want to materially reduce Oracle support costs at renewal, the following sequenced approach consistently produces results:

• Identify unused licences before the renewal: products that are installed but not actively used, or environments (development, test, legacy) where support obligations can be reduced
• Obtain third-party support proposals from at least two providers, covering the products and versions you are currently running
• Secure internal board approval to proceed with third-party support if Oracle does not agree to a support uplift cap at renewal
• Time the renewal conversation to Oracle's fiscal Q4 (March to May) for maximum leverage
• Present the prepared alternative to Oracle in writing, stating clearly that the board has approved third-party support if Oracle's renewal terms include an uncapped 8% annual increase
• Negotiate contractual protections: a multi-year uplift cap of no more than 3% per year, specified as a contract term — not a verbal commitment

Organisations that follow this approach consistently achieve Oracle support cost reductions of 15 to 35 percent versus Oracle's opening renewal position, while remaining on Oracle support with improved contractual protections against future uplift escalation. The total advisory and preparation cost of this approach is a small fraction of the resulting savings on a typical large Oracle support contract.

Deciding Which Path Is Right for Your Organisation

The right Oracle support strategy depends on three factors: your Oracle product upgrade roadmap, your internal Oracle technical capability, and the financial trajectory of your Oracle support obligation relative to the value the support delivers. Organisations that are actively upgrading Oracle products in the next 18 months should remain on Oracle support and focus on negotiating the next renewal. Organisations with stable Oracle estates, no near-term upgrade plans, and strong internal technical capability are the best candidates for third-party support. Organisations planning Oracle-to-SaaS migrations over a three-to-five-year horizon should evaluate a combination of third-party support to bridge the migration period and a negotiated Oracle support phase-down plan for the products that are migrating last.

Every Oracle support decision should be made with independent advisory support that has no financial interest in the outcome — not through Oracle's account team, not through a third-party support provider seeking to win your business, and not through a system integrator whose revenues depend on Oracle's continued investment in your environment.

For independent Oracle support strategy advice — whether you are evaluating third-party maintenance, preparing a negotiation, or planning a long-term exit programme — engage our Oracle support reduction advisory team or contact Redress Compliance directly. Our advisors have 20+ years of Oracle licensing experience and no affiliation with any Oracle support provider.