Oracle Third-Party Support: Rimini Street, Spinnaker & How to Transition Safely

What Is Oracle Third-Party Support?

Third-party Oracle support replaces Oracle's Premier Support contract with an independent support provider who delivers equivalent functional support — tax, regulatory, and legal (TRL) updates; security advisory and vulnerability analysis; technical break-fix support; and interoperability guidance — at a substantially lower annual cost. The enterprise retains its Oracle perpetual licenses; it simply stops paying Oracle for support and pays a third-party provider instead.

Third-party support is entirely legal. Oracle's license agreements grant the customer perpetual use rights for the software. Those rights are not contingent on Oracle support — an enterprise can run Oracle Database, Oracle EBS, or Oracle E-Business Suite indefinitely on a perpetual license without Oracle support, just as software can be run indefinitely after a vendor discontinues it. The question is not legality but practicality: what support services will you receive, and from whom?

The two primary Oracle-focused third-party support providers are Rimini Street (the market leader, publicly traded, with the largest Oracle support customer base) and Spinnaker Support (a smaller, more consultative firm with a strong reputation for personalized service). Both companies have been operating for over a decade and have supported thousands of Oracle environments through security events, regulatory changes, and technical incidents.

Rimini Street vs Spinnaker: Provider Comparison

Rimini Street is the dominant third-party Oracle support provider with over 5,000 enterprise clients and a publicly traded company structure that provides financial transparency and accountability. Rimini Street has faced legal challenges from Oracle (primarily around the methods used to develop security fixes) and has settled those disputes while continuing to operate and grow. Their service model emphasises rapid response times, dedicated account support engineers, and a proactive stance on TRL updates.

Spinnaker Support is a private company with a more selective client base, typically focused on larger enterprises and more complex Oracle environments. Spinnaker's model emphasises dedicated senior support engineers with deep Oracle product knowledge, often with better client-to-engineer ratios than Rimini Street's scale model. For enterprises with highly customized Oracle environments, Spinnaker's consultative approach can deliver better outcomes.

There are also smaller niche providers and the option of self-support (maintaining Oracle products without any third-party support contract). Self-support is viable only for extremely stable, non-internet-facing Oracle deployments with deep in-house Oracle expertise and no active regulatory requirements driving TRL updates.

The Economics: Real Savings Analysis

The cost savings from third-party Oracle support are real and material. Third-party providers typically charge 50% of Oracle's current annual support fee for year one, with annual increases capped at a lower rate than Oracle's uncapped standard increases. For enterprises with large Oracle estates, this produces multi-million-dollar annual savings.

Our case study of an insurance company transitioning to third-party Oracle support on a $5.6M annual Oracle support portfolio delivered $2.8M per year in savings with a transition cost of under $200K — producing a first-year net saving of over $2.6M and a five-year NPV saving exceeding $12M. See our full Insurance Third-Party Support case study for the detailed analysis.

The economics are most compelling for the following situations. Oracle products that are stable (no planned upgrades, no active Oracle roadmap adoption), products that have already received all the functionality the enterprise needs, products that sit on older versions where Oracle charges Extended Support premiums on top of standard annual maintenance, and products in sunset mode (where the enterprise is planning migration in 3–5 years but needs functional support in the interim).

The economics are less compelling — and third-party support is generally not advisable — for Oracle products where the enterprise actively uses Oracle's patch and update cycle, where regulatory requirements mandate Oracle-supplied security patches specifically, or where there are active Oracle product upgrade or cloud migration programs in progress.

Real Tradeoffs: What You Give Up

Third-party Oracle support involves real tradeoffs that must be evaluated against the cost savings. Presenting third-party support as a pure cost saving without acknowledging these tradeoffs would be irresponsible — and Oracle's account teams will raise them in detail when they discover you are considering a switch.

Security patches: The most significant tradeoff is security. Oracle's quarterly CPU (Critical Patch Update) provides official, Oracle-developed patches for vulnerabilities discovered in Oracle products. Third-party support providers do not deliver these patches — instead, they provide security advisory services, workaround guidance, and in some cases independently developed fixes (which are the subject of ongoing legal scrutiny regarding the methods used to develop them). Whether this is adequate depends on your exposure profile, regulatory environment (particularly PCI-DSS, HIPAA, FedRAMP), and the specific products involved.

Oracle upgrade rights: While your perpetual license remains valid, Oracle's upgrade policy means that certain upgrade paths require current Oracle support to be active. If you move to third-party support and later want to upgrade to a newer Oracle version, you may need to reinstate Oracle support (with potential back-support fees) before the upgrade is permitted under your license terms. This creates a significant constraint on roadmap flexibility.

Oracle relationship impact: Oracle's account teams treat third-party support transitions as hostile acts. Expect reduced cooperation on commercial negotiations, potential intensification of audit activity, and loss of access to Oracle co-investment programs. The relationship impact is real but manageable — many enterprises on third-party support continue to have constructive Oracle commercial relationships, particularly if they maintain Oracle support on newer or strategic products while moving legacy products to third-party support.

Cloud migration access: Oracle's cloud migration incentive programs — including Support Rewards — require active Oracle Premier Support. If you are planning or executing an Oracle-to-OCI migration, third-party support on the migrating products removes access to Support Rewards and some migration incentives.

Oracle's Response When You Switch

Oracle's commercial response to a third-party support transition is predictable and follows a standard playbook. Understanding this playbook allows enterprises to prepare and respond effectively rather than being surprised mid-transition.

The "escalation call": When Oracle's system detects a support termination notice or when your account manager learns of the planned switch, expect an escalation call from a senior Oracle executive. The call will include: assertions about the risks of third-party support; an offer of a discounted Oracle support rate (typically 30–40% below standard, contingent on a multi-year commitment); an implicit or explicit suggestion that an audit may follow; and questions about your Oracle roadmap. This call is a negotiating tactic, not a warning. If you were planning to switch to third-party support, this conversation gives you leverage to negotiate a multi-year Oracle support discount — potentially achieving 30–40% savings while retaining Oracle support and avoiding the tradeoffs of third-party providers.

Audit activity: Some enterprises experience LMS audit letters following a third-party support transition notification. Oracle's LMS team operates independently of account teams and targets clients based on risk factors rather than commercial decisions — but enterprises that have recently terminated Oracle support are in a higher-risk category because Oracle has less commercial incentive to treat the compliance conversation cooperatively. Ensuring your Oracle license position is clean before transitioning is essential. Our compliance review service is often used as a pre-transition health check.

Technical access restrictions: Terminating Oracle support may restrict access to Oracle support portals (My Oracle Support), Oracle product downloads, and software updates for the products on third-party support. This is a practical operational consideration — ensure you have downloaded all necessary Oracle software versions, patches applicable to your current version, and documentation before terminating Oracle support access.

Which Oracle Products Are Best Candidates for Third-Party Support?

The product-selection decision is critical. Not all Oracle products should move to third-party support simultaneously or at all. The following criteria define the strongest third-party support candidates.

Highest-value candidates: Oracle Database versions 11g and 12c running stable, non-evolving workloads with no planned migration in the near term; Oracle E-Business Suite 12.1 and 12.2 on stable releases where the enterprise has no active functional upgrade plans; Oracle PeopleSoft and Oracle JD Edwards in similar stable, non-upgrading states; Oracle Siebel CRM (widely considered in maintenance/sunset mode by most enterprises). These represent the core "legacy stable" portfolio where third-party support delivers maximum value.

Moderate candidates: Oracle Database 19c on environments where Oracle's roadmap is not being actively consumed; Oracle WebLogic in stable middleware environments; Oracle Forms and Reports on legacy application tiers. These require more careful evaluation of security requirements and regulatory obligations.

Poor candidates: Oracle Database 23ai (Oracle's current version, where Oracle's roadmap is actively valuable); Oracle Fusion Cloud / SaaS products (which are subscription-based and not covered by third-party support in the same model); Oracle Java SE (where Java licensing is changing rapidly and Oracle's own options may be strategically important); any Oracle product where an active upgrade or OCI migration is planned in the next 24 months.

How to Transition to Third-Party Oracle Support Safely

A well-managed third-party support transition follows a defined process that protects the enterprise operationally and commercially. The key steps are:

1. Pre-transition compliance review: Before notifying Oracle or third-party providers, conduct a forensic Oracle compliance review to identify and close any license gaps. An outstanding compliance issue is far more expensive to resolve after Oracle support has been terminated and your relationship is adversarial.
2. Product and version documentation: Create a complete inventory of every Oracle product and version in scope for third-party support. Document the exact version strings, patch levels, and customization levels for each product. Third-party providers price and scope their contracts based on this documentation.
3. Software and documentation archiving: Download all Oracle software, patches, and documentation you will need from My Oracle Support before terminating Oracle support. Once support is terminated, access to MOS and Oracle downloads for supported products ends.
4. Third-party provider evaluation and contracting: Evaluate both Rimini Street and Spinnaker with detailed RFP processes. Reference-check with existing customers in similar industries and with similar Oracle environments. Negotiate contract terms including price, annual increase caps, escalation SLAs, security response commitments, and exit terms.
5. Oracle notification and negotiation: Notify Oracle of the planned support termination according to your contract's notice period (typically 30–90 days). Use the Oracle escalation call as a negotiation opportunity — Oracle will typically offer discounts that you can document and compare against third-party provider pricing before making the final decision.
6. Transition period overlap: Plan for a 60–90 day period where both Oracle support and third-party support are active simultaneously, allowing your team to build confidence in the third-party provider's response capabilities before fully terminating Oracle support.

The Return Path: Reinstating Oracle Support

Third-party support is not necessarily a permanent decision. Enterprises that move certain products to third-party support while preserving Oracle's roadmap on strategic products may later find reasons to reinstate Oracle support — most commonly because they have decided to migrate to Oracle Fusion Cloud, because a product upgrade requires active Oracle support, or because regulatory requirements have changed.

Reinstating Oracle support after termination is possible but carries a cost: Oracle typically requires payment of "back support" fees covering the period when Oracle support was not active, at the standard annual support rate. This back-support requirement can be significant if third-party support has been active for multiple years. The back-support fee can sometimes be negotiated down in the context of a cloud migration commitment or Oracle agreement renewal — but this requires active negotiation with leverage. Our contract negotiation team has managed multiple support reinstatement negotiations.

The back-support cost is a factor that should be modelled into the original third-party support decision. If there is a significant probability of needing to reinstate Oracle support within 3–5 years (for example, if an EBS-to-Fusion Cloud migration is likely within that window), the expected back-support cost should be weighted against the savings from third-party support to determine the true net financial benefit.