Third-Party Support Transition Advisory
We help organisations evaluate, plan, and execute the transition from Oracle support to third-party alternatives — including hybrid models that optimise cost without sacrificing critical coverage.
1. The Third-Party Support Landscape in 2026
The market for third-party Oracle support has evolved from a fringe alternative into a mature, well-established industry serving a significant and growing share of the global Oracle customer base. The fundamental proposition is unchanged from a decade ago: provide the same or better support services as Oracle Premier Support at 50% or less of Oracle's price. What has changed is the depth of the provider ecosystem, the sophistication of their service delivery, and the legal certainty surrounding their right to operate.
In 2026, the market is dominated by two established providers — Rimini Street and Spinnaker Support — with a growing number of specialist and regional players offering targeted services for specific Oracle product families. The competitive dynamics between these providers work in the customer's favour: pricing is aggressive, service commitments are strong, and contractual flexibility has improved significantly as providers compete for enterprise clients. For a broad overview of the provider ecosystem, see our Oracle Third-Party Support Providers guide. See our Oracle vs Rimini analysis.
The legal landscape is also settled. Oracle's protracted litigation against Rimini Street — which spanned over a decade and reached the US Supreme Court — has definitively established that third-party Oracle support is legal. The rulings clarified boundaries around how providers can deliver support (specifically regarding software copying for patch development), but the fundamental right of customers to choose their support provider is beyond dispute. Any Oracle sales representative suggesting that third-party support is legally questionable is either misinformed or deliberately misleading you.
2. Rimini Street: The Market Leader
Rimini Street is the largest and most established third-party Oracle support provider, publicly traded (NASDAQ: RMNI) with approximately $400+ million in annual revenue and a global client base spanning thousands of organisations. They have been providing Oracle support since 2005 — nearly two decades of operational history — and have built the deepest bench of Oracle product expertise outside of Oracle itself.
Service Model
Rimini Street's core offering is a full replacement for Oracle Premier Support at 50% of the Oracle fee (their standard pricing commitment). The service includes a Primary Support Engineer (PSE) — a named, dedicated engineer assigned to your account with deep expertise in your specific Oracle products. This is a fundamental difference from Oracle's support model, where tickets enter an anonymous queue and are routed through multiple tiers before reaching an engineer with relevant expertise. The PSE model means your initial contact is an engineer who knows your environment, your configuration, and your history — response quality is dramatically higher from the first interaction.
Rimini provides 24/7/365 support coverage, with guaranteed response times (15 minutes for Priority 1 issues). They deliver security advisories and tax, legal, and regulatory (TLR) updates for applicable products. For security, Rimini offers their Advanced Database Security and Advanced Application and Middleware Security solutions — protection layers applied around Oracle software that address vulnerabilities without modifying Oracle's code.
Product Coverage
Rimini Street covers the full Oracle product portfolio: Oracle Database (all editions and versions including those on Sustaining Support from Oracle), Oracle E-Business Suite, PeopleSoft, JD Edwards, Siebel, Hyperion, Oracle Middleware (WebLogic, SOA Suite, Forms, Reports), and Oracle Technology products. Their coverage extends to versions that Oracle has moved to Sustaining Support — meaning you get active support (including security guidance) for products that Oracle would only maintain with existing fixes. For PeopleSoft specifically, see our guide on PeopleSoft third-party support.
Strengths
Scale and track record (20 years of operational history), deepest Oracle product expertise outside of Oracle, publicly traded with financial transparency, global delivery capability (offices in 20+ countries), and the most comprehensive product coverage across Oracle's portfolio.
Considerations
Premium pricing relative to smaller competitors (though still 50%+ below Oracle), the ongoing Oracle litigation history creates headline risk that some risk-averse organisations find uncomfortable (despite clear legal victory), and Rimini's size means some clients report a less personalised experience than smaller providers once the initial onboarding is complete.
3. Spinnaker Support: The Challenger
Spinnaker Support is the second-largest Oracle third-party support provider and positions itself as a more agile, customer-focused alternative to Rimini Street. Founded in 2008 and privately held, Spinnaker has grown steadily to serve hundreds of enterprise clients globally, with a particular strength in mid-market and upper-mid-market organisations.
Service Model
Spinnaker mirrors Rimini's core service model — named support engineers, 24/7 coverage, guaranteed response times, security advisory services, and TLR updates — at comparable or slightly lower pricing (typically 50–60% below Oracle). Where Spinnaker differentiates is in its emphasis on flexibility and personalisation. Their Account Support Lead (ASL) model provides a single point of contact who coordinates all support activity across your Oracle estate, and Spinnaker consistently markets their willingness to customise service agreements, SLAs, and delivery models to individual client requirements.
Spinnaker also provides a security offering — Spinnaker Shield — that provides virtual patching and vulnerability protection for Oracle products, addressing the security gap that is the primary concern for organisations leaving Oracle support.
Product Coverage
Spinnaker covers Oracle Database, E-Business Suite, PeopleSoft, JD Edwards, Siebel, Hyperion, and Oracle Middleware — substantially the same portfolio as Rimini Street. They also support SAP products, which makes Spinnaker a potential single-provider solution for organisations running both Oracle and SAP. Coverage for older Oracle versions on Sustaining Support is available, matching Rimini's position.
Strengths
Reported higher client satisfaction scores compared to Rimini (per analyst surveys), greater contractual flexibility and willingness to customise terms, competitive or lower pricing, multi-vendor support capability (Oracle + SAP + IBM), and a leaner organisation that can be more responsive to individual client needs.
Considerations
Smaller scale means fewer engineers overall (though those assigned to your account are typically highly experienced), less public financial transparency (privately held), and a shorter track record than Rimini Street (though 17 years is substantial). Some organisations in heavily regulated industries prefer Rimini's larger, publicly traded profile for vendor risk management purposes.
4. The Rest of the Field: Specialist and Regional Providers
Beyond the two market leaders, a growing ecosystem of specialist and regional third-party support providers has emerged — particularly since 2020 — to serve specific niches within the Oracle customer base.
US Providers
Origina focuses specifically on Oracle technology products (Database, Middleware, Java) with a distinctive approach centred on independent security patching. Unlike Rimini and Spinnaker, which typically provide security advisories and virtual patching, Origina develops actual binary patches that can be applied directly to Oracle software. This is the closest analogue to Oracle's own CPU process and appeals to organisations with strict patch-application requirements from their security or compliance teams.
Support Revolution provides Oracle support with a focus on mid-market organisations and a lean, engineer-led service model. Their pricing is typically below Rimini and Spinnaker (60–70% below Oracle), making them attractive for cost-sensitive clients with straightforward Oracle estates.
European and Regional Providers
Several European providers offer Oracle third-party support with specific strengths in data sovereignty, regional language support, and EU regulatory expertise. These include providers in Germany, the UK, and the Nordics that serve regional enterprises requiring local-language support engineers and data residency guarantees. For organisations with strict data processing requirements under GDPR, a European-headquartered provider can simplify compliance.
Specialist Providers
A growing number of firms specialise in specific Oracle product families — particularly Oracle Database and Oracle Middleware. These specialists typically employ former Oracle product engineers and offer deep expertise in a narrow product range. They may lack the breadth of Rimini or Spinnaker, but for organisations whose Oracle estate is concentrated in one or two product families, the depth of expertise can be superior.
5. Head-to-Head Comparison: Every Factor That Matters
The following comparison evaluates the providers across the dimensions that matter most to enterprise Oracle customers making a support transition decision. This assessment is based on publicly available information, provider disclosures, analyst research, and our direct advisory experience working with clients across all providers.
| Factor | Oracle Premier | Rimini Street | Spinnaker Support | Specialist Providers |
|---|---|---|---|---|
| Annual cost (vs Oracle) | 100% (baseline) | ~50% | ~40–50% | ~30–50% |
| Annual uplifts | 3–8% contractual | Typically 0–3% | Typically 0–3% | Often 0% |
| Named support engineer | No — tiered queue | Yes (PSE model) | Yes (ASL model) | Yes (small teams) |
| P1 response time | Varies (hours typical) | 15 minutes | 15 minutes | 15–30 minutes |
| Security patches (CPUs) | Quarterly Oracle CPUs | Security advisories + virtual patching | Security advisories + Spinnaker Shield | Varies — some provide binary patches |
| Version upgrades | Yes — included | No | No | No |
| Oracle product breadth | Full portfolio | Full portfolio | Full portfolio | Typically 1–3 product families |
| Multi-vendor support | Oracle only | Oracle + SAP | Oracle + SAP + IBM | Usually single-vendor |
| Sustaining Support products | No new patches | Active support continues | Active support continues | Active support continues |
| Financial transparency | Public company | Public (NASDAQ) | Private | Varies |
| Global coverage | Yes | Yes (20+ countries) | Yes (multiple regions) | Typically regional |
| Contractual flexibility | Low — standard terms | Moderate | High | High |
| Track record | N/A (the vendor) | 20 years | 17 years | 5–15 years |
The Pricing Reality
The headline "50% savings" is real but requires context. Third-party support pricing is based on 50% (or less) of your current Oracle support fee — which means the savings compound on top of whatever optimisation you've already achieved on the Oracle side. For an organisation paying $4 million in annual Oracle support, the third-party price is approximately $2 million — an immediate $2 million annual saving. Over five years, accounting for Oracle's compounding uplifts that you would have paid (but won't), the cumulative saving exceeds $12 million.
However, third-party pricing is negotiable, particularly for large estates. Rimini Street and Spinnaker both offer volume pricing, multi-year discounts, and customised pricing structures for clients with $2M+ in annual Oracle support. In competitive bids (where both providers are quoting), pricing can drop to 35–45% of the Oracle rate. Always obtain quotes from at least two providers before making a commitment.
6. What You Genuinely Lose When You Leave Oracle Support
Intellectual honesty requires acknowledging what third-party support cannot replace. Oracle maintains certain capabilities that no third-party provider can replicate, and understanding these losses is essential for making an informed decision. For the full comparative analysis, see our third-party vs. Oracle Premier Support guide.
Oracle's Official Patches
Third-party providers cannot distribute Oracle's proprietary patches — the quarterly Critical Patch Updates (CPUs) that address known vulnerabilities in Oracle software. This is the single most significant trade-off. Third-party providers address this gap through security advisory services (notifying you of relevant vulnerabilities), virtual patching (applying protection at the network or application layer without modifying Oracle's code), and, in some cases, independently developed binary patches (Origina's approach). These alternatives are effective for most environments, but they are not identical to Oracle's CPUs. Organisations with compliance requirements that specifically mandate vendor-issued patches (rare, but they exist) may be unable to leave Oracle support without a waiver.
Version Upgrade Access
Leaving Oracle support forfeits your right to download and install new Oracle versions. If you're planning to upgrade from Oracle Database 19c to 23ai, you need Oracle support to access the new version. Once you've left, you're locked into your current version. For organisations on stable, mature versions with no upgrade plans, this is irrelevant. For organisations with active upgrade roadmaps, it's a dealbreaker for the products being upgraded. This is why the decision must be made product by product — not as a blanket policy.
Oracle Software Download Access
Oracle restricts software download access from its delivery infrastructure to customers with active support contracts. While you retain your perpetual licence to use the software (dropping support does not revoke your licence), you lose the ability to download installation media, patches, and utilities from Oracle's technology network. Ensure you have local copies of all required installation media, current patches, and diagnostic tools before terminating Oracle support.
Platform Certification
Oracle certifies compatibility between its software and specific hardware/OS platforms. When Oracle certifies Oracle Database 19c on RHEL 9, that certification is backed by Oracle's testing and support commitment. Third-party providers cannot provide this certification. For most production environments running established platforms, this is a non-issue — the certification already exists for your current configuration. The risk materialises only when you need to migrate to a new platform (new OS version, new hardware generation) that requires updated certification.
7. The Hybrid Model: Keeping Oracle Where It Matters
The highest-value approach for most enterprise Oracle customers in 2026 is not a binary choice between Oracle support and third-party support — it's a hybrid model that assigns each Oracle product to the support provider best suited for its lifecycle stage, criticality, and evolution trajectory.
How the Hybrid Model Works
Segment your Oracle estate into three tiers based on the support value equation for each product:
Tier 1 — Retain Oracle Support: Products where Oracle's support delivers irreplaceable value. Typically: Oracle Database Enterprise Edition instances that are actively patched and planned for version upgrades, Oracle Cloud applications and services (which require Oracle support by contract), and any product where compliance mandates vendor-issued patches. This tier typically represents 20–40% of total Oracle support spend.
Tier 2 — Move to Third-Party: Products that are stable, mature, and not planned for upgrade. Typically: PeopleSoft, Siebel, JD Edwards (stable ERP/CRM applications running mature versions), Oracle Middleware (WebLogic, SOA Suite, Forms), Hyperion and other analytics products, and older Oracle Database instances on versions that Oracle has moved to Sustaining Support. This tier typically represents 40–60% of total Oracle support spend — and it's where the savings are concentrated.
Tier 3 — Terminate Support Entirely: Products that are shelfware, deprecated, or so infrequently used that no support (Oracle or third-party) is justified. Typically: unused database options, deprecated tools, over-provisioned application licences, and post-ULA surplus products. This tier represents 10–25% of total support spend and reduces to zero cost.
Scenario: The Three-Tier Strategy in Action
A North American financial services firm with $7.8 million in annual Oracle support engaged our transition advisory service. The analysis segmented their estate as follows. Tier 1 (retain Oracle): Oracle Database Enterprise Edition — actively patched, 23ai upgrade planned — $2.9M annual support retained at Oracle. Tier 2 (move to third-party): PeopleSoft HCM, Siebel CRM, WebLogic Middleware, Hyperion — all stable, no upgrades planned — $3.4M Oracle support replaced by Spinnaker at $1.5M. Tier 3 (terminate): Unused database options (Partitioning, OLAP), deprecated middleware, shelfware — $1.5M Oracle support terminated entirely. Result: annual support spend dropped from $7.8M to $4.4M — a $3.4M annual saving (44%) — with zero degradation in support quality for mission-critical systems. Over five years (accounting for eliminated Oracle uplifts), cumulative savings: approximately $19 million.
For real-world examples of the hybrid model at scale, see our case studies on Adecco (€12M saved over 3 years), Avis Car Rental ($8M saved on WebLogic), Technip Energies (€12M saved), and Telefónica (€40M saved).
8. Oracle's Exit Barriers and How to Navigate Them
Oracle has constructed a multi-layered system of disincentives designed to prevent customers from leaving Oracle support. Understanding each barrier — and the specific counter-strategy for each — is essential for executing a successful transition.
Barrier 1: The Reinstatement Penalty
If you terminate Oracle support and later need to reinstate, Oracle charges all back support fees for the lapsed period plus a reinstatement penalty of up to 50%. For a product with $500,000 in annual support dropped for three years, the reinstatement cost is: ($500K × 3) + ($1.5M × 50%) = $2.25 million. The penalty is explicitly designed to make leaving Oracle more expensive than staying.
Counter-strategy: The reinstatement penalty only matters if you reinstate. Make definitive product-by-product decisions rather than "try and see" migrations. For products you're genuinely uncertain about, retain Oracle support — the cost of keeping Oracle on a product you might need is lower than the reinstatement penalty if you guess wrong. For products you're confidently retiring, the reinstatement penalty is irrelevant. If reinstatement becomes necessary, it is negotiable — particularly when packaged with new purchases or cloud commitments.
Barrier 2: Oracle Sales Pressure
When Oracle learns you're evaluating third-party support, expect an escalated response from your account team: a dedicated "save" campaign that includes alarming (often exaggerated) claims about security risk, legal risk, and loss of functionality; competitive counter-offers (temporary discounts, support credits, free cloud migration assessments); and, in some cases, an audit notification timed to create compliance anxiety that discourages the transition. For tactics to manage this pressure, see our guide on dealing with Oracle sales tactics.
Counter-strategy: Complete your compliance assessment and remediate any gaps before notifying Oracle of your third-party evaluation. A clean compliance position neutralises the audit threat. Evaluate Oracle's counter-offers on their merits (temporary discounts expire; third-party savings are permanent), and maintain competitive pressure by having signed third-party provider agreements ready to execute.
Barrier 3: FUD (Fear, Uncertainty, Doubt)
Oracle's most effective exit barrier is not financial — it's psychological. The fear that something will go wrong without Oracle's support, the uncertainty about whether third-party patches are sufficient, the doubt about whether the provider will survive. Oracle's sales messaging amplifies these anxieties with anecdotes about third-party customers who "came back" and with legal narratives that overstate the risks.
Counter-strategy: Replace FUD with data. Request reference clients from your shortlisted third-party providers — specifically, clients in your industry, of similar scale, running similar Oracle products. Talk to them directly. Ask about security incident response, patch delivery timelines, support quality, and any challenges during the transition. The operational reality of third-party support, as reported by actual clients, consistently contradicts Oracle's narrative.
Barrier 4: Cloud Bundling
Oracle increasingly offers support discounts bundled with cloud migration commitments — Support Rewards, cloud credits, and migration assistance tied to maintaining on-premise support. These offers create financial entanglement that makes it harder to evaluate third-party support in isolation.
Counter-strategy: Unbundle the economics. Calculate the value of Support Rewards credits separately from the support cost. Determine whether the cloud credits are genuinely useful (do you actually consume enough OCI?) or whether they're effectively a retention mechanism with limited practical value. Often, the net savings from third-party support exceed the value of Oracle's cloud incentives — but you can only know this by modelling both scenarios explicitly.
9. Making the Decision: The Product-by-Product Framework
The decision to move to third-party support should never be made in aggregate. It should be made product by product, using a structured evaluation framework that balances cost savings against operational risk. Here is the methodology we use in our Oracle advisory engagements.
Step 1: Inventory and Categorise
List every Oracle product on support. For each, document: annual support cost, current version, planned version upgrades (if any), patching frequency (how often you actually apply Oracle patches), criticality to business operations, and regulatory/compliance requirements for vendor-issued patches. Use our Oracle Assessment Tools to accelerate this inventory.
Step 2: Apply the Decision Criteria
For each product, evaluate against four criteria. Upgrade trajectory: Is this product planned for a version upgrade within 36 months? If yes, retain Oracle support (you need upgrade access). If no, third-party is viable. Patch dependency: How frequently do you apply Oracle patches to this product? If quarterly or more, retain Oracle (the patching cadence has real value). If annually or less, third-party is viable. Compliance mandate: Does a specific regulatory requirement mandate vendor-issued patches? If yes, retain Oracle (or evaluate providers like Origina that deliver binary patches). If no, third-party is viable. Cost-to-value ratio: What percentage of the product's total value does annual support represent? If the support cost exceeds 50% of the product's operational value to the business, the support is overpriced regardless of provider.
Step 3: Model the Hybrid Financial Outcome
Assign each product to Tier 1 (retain Oracle), Tier 2 (move to third-party), or Tier 3 (terminate). Calculate the total annual cost under the hybrid model. Calculate the five-year cumulative savings including eliminated Oracle uplifts. Factor in transition costs (typically 1–3 months of consulting support plus internal effort for data migration, process documentation, and third-party provider onboarding). Our Oracle Support Cost Optimisation Assessment provides this complete financial model.
Step 4: Negotiate and Execute
Obtain competitive quotes from at least two third-party providers. Negotiate aggressively — use competitive bids between providers to drive pricing down. Negotiate contractual protections: guaranteed pricing for 3–5 years (with caps on any uplifts), exit provisions if service quality deteriorates, and service level agreements with financial penalties for missed response times. Execute the Oracle support termination within the contractual notice window — typically 30 days before the renewal date. Use our Oracle Support Renewal Contract Checklist to manage the administrative execution. For broader negotiation support, see our Oracle Contract Negotiation Service.
Step 5: Manage the Ongoing Relationship
Post-transition, maintain governance over both your Oracle and third-party support relationships. Monitor third-party support quality against SLAs. Track Oracle's response to your support reduction (including any audit or commercial escalation). Reassess the hybrid model annually — products that were correctly placed on Oracle support this year may become candidates for third-party migration next year as they mature and stabilise. For the ongoing relationship with Oracle, see our Oracle Renewal Negotiation Checklist.
| Decision Criterion | Retain Oracle | Move to Third-Party | Terminate Support |
|---|---|---|---|
| Version upgrade planned (≤36 months) | ✓ | ||
| Frequent patching (quarterly+) | ✓ | ||
| Compliance mandates vendor patches | ✓ | ||
| Stable version, no upgrade planned | ✓ | ||
| Mature product, infrequent patching | ✓ | ||
| Product not deployed (shelfware) | ✓ | ||
| Product being decommissioned | ✓ |
10. Frequently Asked Questions
No. Your Oracle licences are perpetual — they do not expire and they are not conditional on maintaining Oracle support. Terminating Oracle support ends your access to Oracle's patches, updates, and technical support services, but your licence to use the software continues indefinitely. This is explicitly stated in Oracle's standard Master Agreement and has been confirmed through litigation. Oracle cannot revoke your licence because you chose a different support provider.
When a zero-day vulnerability affecting Oracle software is disclosed, third-party providers typically respond within 24–72 hours with a security advisory detailing the vulnerability, its severity, and affected products. They then provide one or more of: virtual patching (protection applied at the network or application layer without modifying Oracle code), configuration guidance (hardening measures that mitigate the vulnerability), and, from providers like Origina, independently developed binary patches. The response is typically faster than Oracle's quarterly CPU cycle — Oracle patches known vulnerabilities on a quarterly schedule, meaning a vulnerability disclosed the day after a CPU release may remain unpatched by Oracle for nearly three months. Third-party providers address critical vulnerabilities on an ad hoc basis as they emerge.
Yes — and this is the approach we recommend for most organisations. You can retain Oracle support on specific products (typically mission-critical databases and applications with active upgrade plans) while moving other products (stable applications, mature middleware, products on Sustaining Support) to a third-party provider, and terminating support entirely on shelfware and deprecated products. Oracle's support is managed at the product level through individual support identifiers (CSIs), and you can terminate or retain support on each product independently. The only restriction is Oracle's "all or nothing" rule for support within a single Ordering Document — if an Ordering Document covers multiple products, you may need to terminate support on all products in that document or none. Review your Ordering Documents to understand the grouping.
This is a legitimate risk that must be addressed contractually. Negotiation essentials include: escrow provisions that guarantee access to the provider's proprietary tools and security patches in the event of insolvency, termination-for-convenience clauses that allow you to exit the third-party contract and return to Oracle if needed, and transition assistance obligations that require the provider to support a return to Oracle or migration to another provider. Financially, evaluate the provider's stability: Rimini Street's public filings provide transparency, while privately held providers should be willing to share audited financials under NDA. The risk of provider failure is real but manageable — and must be weighed against the certainty of paying double for Oracle support every year.
Possibly. Significant support reductions frequently trigger increased commercial attention from Oracle, which can include audit activity. Oracle's audit right exists in your contract regardless of your support status, and an audit notification is not conditional on maintaining support. The best defence: ensure your licence compliance position is clean before initiating any support transition. Conduct an internal compliance assessment as the first step. If your compliance position is strong, an audit produces minimal findings and Oracle's leverage is limited. If your compliance position has gaps, address them before Oracle discovers them — the cost of proactive remediation is always lower than the cost of audit-driven remediation. See our Oracle Audit Defence Services for support.
For any organisation with annual Oracle support exceeding $1M, independent advisory support adds significant value — and for organisations over $3M, it's essentially mandatory for optimal outcomes. An independent advisor provides: pricing benchmarks across all major third-party providers (ensuring you're getting competitive rates), product-by-product risk assessments (identifying which products are safe to move and which should stay), compliance preparation (ensuring Oracle has no audit leverage to use against you during the transition), and negotiation support (both with third-party providers and with Oracle's retention team). The advisor must be genuinely independent — not affiliated with or receiving referral fees from any third-party support provider. At Redress Compliance, our third-party support transition service is vendor-neutral by design. Visit our Oracle Knowledge Hub for additional resources, or explore our Support Cost Optimisation Assessment to start the evaluation.