Oracle Third-Party Support Comparison 2026: Rimini Street vs Spinnaker vs Oracle Premier

What Is Oracle Third-Party Support?

Oracle third-party support (TPS) allows organisations to cancel their Oracle Premier Support contract and instead engage an independent provider who delivers break-fix services, security patches, regulatory updates, and interoperability support — all without Oracle's involvement. The two dominant providers in 2026 are Rimini Street and Spinnaker Support, both of which have served thousands of enterprise clients across Oracle's on-premises technology and applications stack.

Third-party support applies exclusively to on-premises, perpetual licence products. It does not apply to Oracle SaaS subscriptions, Oracle Cloud Infrastructure (OCI) services, or any consumption-based Oracle Cloud contracts. If your Oracle footprint includes a mix of on-premises and cloud products, you can selectively apply TPS to the on-premises stack while retaining Oracle support on cloud services — subject to Oracle's matching service level policies for the same product family.

The core value proposition is straightforward: Oracle Premier Support costs 22% of your net licence fee per year and rises 8% annually regardless of usage. A typical Rimini Street or Spinnaker engagement prices at approximately 50% of your current Oracle support bill and locks that rate flat for the contract term — typically two to three years. On a $500,000 Oracle support bill, that means saving roughly $250,000 in year one alone, compounding upward as Oracle's uplift accumulates.

Oracle Premier Support: What You Pay and What You Get

Oracle Premier Support is the baseline commercial support offering for on-premises software. The annual fee is calculated as 22% of the net licence fee — the discounted purchase price, not the list price. For organisations that purchased licences at heavy discount, the net fee may be materially lower than list, which reduces the support base. However, Oracle applies an 8% annual uplift to the support fee, meaning the cost increases year-on-year without any corresponding increase in your licence entitlement or software version.

Premier Support covers new product versions and patches, critical patch updates (CPUs), regulatory and tax updates for applicable modules, access to My Oracle Support (MOS), and Oracle's internal engineering escalation path. For organisations actively upgrading platforms or planning to migrate to Oracle Cloud, that upgrade entitlement has genuine value: it provides a legal pathway to move to newer releases without purchasing new licences.

For organisations running stable, mature on-premises systems with no near-term upgrade plans, however, the upgrade entitlement goes unused — and the 8% annual fee uplift creates a compounding cost burden with no corresponding benefit. This is precisely the scenario where third-party support becomes most compelling.

Rimini Street: The Market Leader

Rimini Street, founded in 2005, is the largest independent enterprise software support provider globally. It effectively created the Oracle third-party support market and has served thousands of clients across Oracle Database, Oracle E-Business Suite, PeopleSoft, JD Edwards, Siebel, and related middleware products. Rimini Street typically saves clients 50% on their Oracle support costs and provides each customer with a primary support engineer — a named, senior technical contact who understands the client's specific environment.

Rimini Street's model centres on custom-engineered fixes developed within the client's own environment. When a bug or security vulnerability is identified, Rimini engineers analyse the issue and develop a targeted patch or workaround specific to the client's configuration — rather than applying generic Oracle patches that may conflict with customisations or require extensive regression testing. This approach can significantly reduce the internal testing burden that typically accompanies Oracle's quarterly CPU releases.

The Oracle vs. Rimini Street Legal History

Rimini Street's history includes a long-running and consequential legal dispute with Oracle. Oracle filed suit in 2010 alleging copyright infringement, and won a trial verdict in 2015 resulting in substantial damages. The case continued through multiple appeals and retrials over the following decade. In December 2024, the Ninth Circuit Court of Appeals vacated all material copyright rulings and reversed the district court's prior judgements — a significant legal outcome that substantially validated Rimini Street's operating model. In July 2025, Oracle and Rimini Street reached a confidential settlement, ending the fifteen-year legal saga. Oracle also completed payment of approximately $37.8 million back to Rimini Street out of previously awarded legal fees.

The settlement includes a requirement for Rimini Street to wind down PeopleSoft support by July 2028, but the broader Oracle Database and applications support business continues. The legal resolution substantially reduces the perceived risk of engaging Rimini Street compared to the uncertainty that existed during the litigation period. That said, organisations considering Rimini Street should still conduct legal due diligence regarding IP compliance protocols and confirm the scope of available product coverage given the PeopleSoft wind-down.

Spinnaker Support: The Conservative Alternative

Spinnaker Support, founded in 2008, is the second major TPS provider and is widely regarded as taking a more conservative approach to intellectual property compliance than Rimini Street's historical methodology. Spinnaker has consistently positioned itself as the safer option for risk-averse organisations concerned about Oracle's legal stance, and it has maintained a cooperative posture designed to avoid the type of IP disputes that characterised Rimini Street's history.

Spinnaker's savings are broadly comparable to Rimini Street — typically 50% or more off Oracle's Premier Support fee — and the company commits to multi-year price stability, eliminating Oracle's 8% annual uplift from the equation. Spinnaker supports Oracle Database, Oracle E-Business Suite, JD Edwards, PeopleSoft, Siebel, and Hyperion, as well as SAP products. Clients receive dedicated support engineers and direct access to senior technical staff without the ticket-routing delays common in Oracle's large-scale support model.

Spinnaker's stricter IP compliance posture comes at a cost: some clients report that its workaround and patch development timelines can be slower than Rimini Street's, particularly for complex customised environments. For organisations where support responsiveness is the primary concern, Rimini Street's deep Oracle expertise and larger engineering bench may tip the balance. For those where legal risk tolerance is paramount, Spinnaker's model offers a defensible and conservative path.

Head-to-Head Comparison: Oracle Premier vs Rimini Street vs Spinnaker

The table below compares the three support options across the dimensions that matter most to enterprise IT and procurement teams:

What Third-Party Support Does Not Cover

Understanding the boundaries of TPS coverage is essential to a sound decision. Third-party support providers cannot deliver Oracle's proprietary software patches, new product versions, or major release upgrades. When you leave Oracle Premier Support, you lose access to Oracle's patch delivery infrastructure entirely — including Critical Patch Updates and Security Alert packages distributed via My Oracle Support.

TPS providers address the security patch gap by developing their own custom fixes and workarounds for known vulnerabilities. These may be delivered as configuration changes, code-level patches developed within the client environment, or recommended compensating controls. Whether this approach provides equivalent security coverage to Oracle's CPU programme is a matter of ongoing debate, and organisations in heavily regulated sectors — banking, healthcare, critical infrastructure — should conduct a formal risk assessment before proceeding.

The other material exclusion is Oracle's engineering escalation path. If a critical incident requires Oracle's internal product engineering to develop a fix — a defect in Oracle's own core code, for example — that channel is closed once you leave Premier Support. TPS providers can escalate to Oracle on your behalf only if Oracle permits it under the terms of your licence agreement, which it typically does not for clients who have cancelled support. In practice, TPS engineers often resolve critical issues through environment-level workarounds rather than source code fixes, but this distinction matters for organisations with zero-downtime availability requirements on core transactional systems.

The Support Rewards Trade-Off

One factor that is frequently overlooked in TPS analyses is the permanent loss of Oracle Support Rewards eligibility. Support Rewards accrues at 25% of Oracle support spend on standard Oracle Universal Credits contracts, and at 33% for ULA customers, generating credits that offset future Oracle technology support invoices. These credits have a twelve-month expiry and apply only to Oracle Cloud Infrastructure and technology support billing — not to SaaS applications.

For organisations with significant OCI spend or plans to deploy OCI, Support Rewards can generate material reductions on the Oracle support bill. If your $500,000 Oracle support bill is already generating $125,000 in annual Support Rewards credits and you are actively consuming them against OCI invoices, then the net cost of Oracle Premier Support is effectively $375,000 — not $500,000. The TPS saving calculation changes materially when Support Rewards credits are factored in. Switching to TPS eliminates Support Rewards eligibility permanently and immediately, with no grandfather period or transition arrangement.

Organisations currently enrolled in Oracle Support Rewards, or planning significant OCI investment, should model the net TPS saving after accounting for forfeited credits before making a decision.

Oracle's Matching Service Level Policy

Oracle's commercial support contracts include a "matching service level" requirement — commonly known as the licence set rule — which prevents organisations from dropping support on a subset of licences for the same product. If you run Oracle Database Enterprise Edition across your estate, you cannot cancel support on half those licences while retaining it on the other half. The rule requires a consistent support level across all licences in the same product family.

This policy does not prevent you from switching one product entirely to TPS while keeping Oracle support on a different product. For example, you can cancel Oracle E-Business Suite support and engage Rimini Street while retaining Oracle Premier Support on Oracle Database — provided the two products are distinct enough in Oracle's product hierarchy to qualify as separate licence sets. Understanding the precise product family boundaries requires careful review of your Oracle licence agreements and Order Documents, as Oracle's definitions are not always intuitive.

Returning to Oracle Premier Support

The reversibility question is important. If you switch to TPS and subsequently need to return to Oracle Premier Support — to access a new Oracle version, to restore the Oracle escalation path, or to maintain OCI migration eligibility — Oracle will require payment of backdated support fees plus a reinstatement penalty for the lapsed period. The reinstatement cost is negotiable, particularly if Oracle is motivated to win back your business, but it can be substantial. Organisations should model the cost of a two-to-three year TPS engagement followed by return to Oracle as a realistic scenario, not an unlikely edge case.

The re-onboarding requirement is also operational, not merely financial. Oracle will require you to certify the current state of your software environment, confirm the versions running, and potentially apply accumulated patches before reinstating support. For organisations that have operated without Oracle patches for several years, this can represent a significant remediation effort prior to re-onboarding.

Decision Framework: When to Switch, When to Stay

Third-party support is the right decision for some organisations and the wrong decision for others. The following criteria help separate the two cases.

Strong candidates for third-party support

• Stable, mature on-premises systems with no planned upgrades in the next three to five years. The value of the Oracle Premier upgrade entitlement only exists if you intend to use it.
• Organisations with significant customisations on Oracle applications. TPS providers cover custom code; Oracle support does not.
• Version-obsolete environments where Oracle has moved products to Sustaining Support status. TPS providers will continue full-service support on versions Oracle no longer actively patches.
• Organisations with no OCI deployment or Support Rewards eligibility, where the programme's credits are not being generated or consumed.
• IT teams with mature licence governance capable of managing audit risk independently, without reliance on Oracle's support relationship as an informal audit deterrent.

Organisations that should stay with Oracle Premier

• Active OCI users with material Support Rewards accrual, where the net effective cost of Oracle Premier Support is substantially below the 22% headline rate after credits.
• ULA customers approaching certification. Staying on Oracle Premier Support maximises Support Rewards accrual at the 33% ULA rate before certification, and maintains deployment flexibility through the ULA term.
• Organisations planning Oracle Cloud migration within the next two years, where the upgrade entitlement and Oracle's technical facilitation retain genuine value.
• Highly regulated environments requiring Oracle's official CPUs for compliance, where TPS custom fixes may not satisfy audit or regulatory requirements.
• Core transactional systems with strict SLA requirements and zero tolerance for the reduced Oracle escalation access that TPS entails.

Negotiation Leverage: Using TPS to Reduce Oracle's Price

Even organisations that ultimately intend to stay with Oracle Premier Support should evaluate third-party support actively — because the credible threat of switching is one of the most effective tools available for negotiating Oracle support reductions. Oracle's sales team is highly motivated to retain support revenue, particularly at renewal. Presenting a documented TPS proposal from Rimini Street or Spinnaker at renewal negotiations creates genuine pricing pressure that Oracle would not face from a passive renewal.

In practice, Oracle will often offer support discounts, credit packages, or contractual commitments on future uplift rates to retain accounts that are seriously evaluating TPS. These concessions can be worth capturing even without executing the TPS switch — though they must be documented in the licence agreement to be binding. A one-time "goodwill" discount that disappears at the next renewal cycle creates no lasting value.

The most effective negotiating position combines a credible TPS evaluation — ideally with a formal proposal from at least one provider — alongside a clear articulation of your Oracle road map. If Oracle understands that your on-premises estate is stable for four years with no cloud migration planned, the calculus for offering a discount changes significantly compared to a client with an active OCI migration underway.

Key Takeaways

Oracle third-party support delivers a genuine 50% cost saving for most organisations and has a proven, legally validated track record following the resolution of the Oracle vs. Rimini Street litigation in 2025. The decision is not binary and should be assessed product by product, with careful modelling of Support Rewards impacts, reinstatement costs, and the value of the Oracle upgrade entitlement. Rimini Street remains the market leader with unmatched Oracle depth; Spinnaker Support offers a more conservative IP posture for risk-averse organisations. Neither provider replaces Oracle Premier Support for organisations in active cloud migration or ULA certification cycles — but for stable on-premises estates, the savings case is difficult to ignore.