An independent advisory analysis of Spinnaker Support as a third-party Oracle support provider. Covers cost comparisons, service capabilities, risks, licence compliance, reinstatement costs, security considerations, and a step-by-step transition framework for enterprise IT leaders.
Part of the Oracle Third-Party Support content series. See also: Is Third-Party Support Legal? | CIO Transition Guide | Major Provider Comparison.
Oracle third-party support refers to maintenance and support services for Oracle software provided by an independent company rather than Oracle itself. Enterprises with valid Oracle licences can receive troubleshooting, bug fixes, and technical guidance from these independent providers without maintaining an active Oracle support contract.
Third-party support emerged as a direct response to the high fees and rigidity of Oracle's standard support model. Oracle typically charges approximately 22% of the licence price annually for maintenance, often with mandatory upgrades attached. Independent providers promise responsive, same-day issue resolution at a significantly lower cost. They frequently deliver a more tailored, customer-centric experience.
Over the past decade, this model has matured from a niche offering into a mainstream cost-optimisation strategy. The average client saves approximately 50% on annual support costs by switching. Even public-sector organisations, including universities and government agencies, have saved millions while maintaining full system stability.
It is a proven, widely adopted strategy used by thousands of enterprises globally. The key success factor is selecting the right provider and ensuring your Oracle systems are stable, well-documented, and fully licence-compliant before making the transition.
| Motivation | Detail |
|---|---|
| Significant cost savings | Third-party providers typically charge around half of Oracle's support fees. For large enterprises, this translates to millions freed up for innovation and strategic priorities. Independent contracts also typically eliminate automatic annual fee increases that Oracle imposes, keeping IT budgets predictable |
| No forced upgrades | Oracle ties support eligibility to product versions, pushing customers toward disruptive and costly upgrades on Oracle's timeline. Third-party support imposes no such requirement. You can continue running a stable Oracle version for as long as it meets your business needs |
| Extended support for legacy systems | Independent providers will continue supporting older Oracle products or versions that Oracle has phased out. If you rely on a legacy Oracle application past its official end-of-support date, a provider like Spinnaker can maintain it for years without Oracle's premium extended-support fees |
| Personalised, responsive service | Third-party firms assign dedicated senior engineers, frequently former Oracle staff, who become deeply familiar with your specific environment. Issues are resolved more quickly and with greater context. Support extends to customisations and unique configurations that Oracle typically declares out of scope |
| Budget for innovation | By reducing "run" costs, third-party support enables CIOs to reallocate funds to cloud migrations, AI and analytics projects, or other strategic initiatives that drive competitive advantage |
When evaluating Oracle third-party support providers, Spinnaker Support consistently emerges as one of the leading options. Founded in 2008 and headquartered in the United States, Spinnaker has grown to serve over 1,000 global clients and is widely considered a principal competitor to Rimini Street, the largest provider in this market.
Spinnaker's coverage spans Oracle databases and applications, including E-Business Suite, JD Edwards, PeopleSoft, and Siebel, as well as other enterprise platforms such as SAP and Salesforce.
| Attribute | Detail |
|---|---|
| Founded | 2008, US-based |
| Global clients | 1,000+ |
| Coverage | Oracle DB, EBS, JD Edwards, PeopleSoft, Siebel, SAP, Salesforce |
| Support model | Dedicated senior engineers, 24/7 direct access |
| Legal history | No IP disputes with Oracle |
| Industry recognition | Gartner Market Guide representative vendor |
Spinnaker Support is known for a high-touch service model that emphasises quality and flexibility. Their staff includes many former Oracle engineers and developers, bringing deep product expertise to every client engagement. Contracts and support scope are tailored to each organisation rather than the one-size-fits-all approach characteristic of Oracle's standard support.
A notable distinction: Spinnaker has avoided the legal conflicts that have characterised the broader third-party support industry. Oracle pursued lengthy litigation against Rimini Street over IP misuse of Oracle support materials. Spinnaker, by contrast, adheres to stricter protocols and has maintained a cooperative posture. This positions Spinnaker as a lower-risk choice for organisations sensitive to legal exposure.
Spinnaker's clean legal record is a meaningful differentiator, particularly for risk-averse enterprises in regulated industries. When evaluating providers, always ask about their support delivery methodology and how they ensure compliance with Oracle's intellectual property rights. A provider's legal posture directly affects your organisation's risk profile.
| Aspect | Oracle Premier Support | Third-Party Support (Spinnaker) |
|---|---|---|
| Annual cost | Approximately 22% of licence price, with approximately 4% yearly uplift built into the contract | Approximately 50% lower than Oracle's fee. Often fixed year-to-year with no automatic increases |
| Included upgrades | New version upgrades and patches included while support is active | No vendor upgrades provided. System stays on current version with provider-developed workarounds |
| Security patches | Regular Oracle security patches, including quarterly Critical Patch Updates (CPUs) | No Oracle-issued patches after contract ends. Provider delivers custom fixes and security workarounds |
| Support scope | Standard break/fix for vanilla software. Limited or no help with customisations | Broad scope covers customisations, performance tuning, and older versions Oracle no longer supports |
| Support model | Global Oracle support centre, ticket-based, with varying response times | Dedicated engineer model, often 24/7 direct access, faster response with deep product expertise |
| Contract flexibility | Rigid terms. All related licences must stay on Oracle support ("all or nothing" matching policy) | Flexible terms. Support specific products or modules. Customisable SLAs and contract lengths |
| Reinstatement penalty | N/A (already on Oracle support) | If returning to Oracle, must pay back fees plus penalty to reinstate. Plan ahead for this cost |
| Vendor relationship | Maintains relationship and influence with Oracle (roadmaps, customer programmes) | May reduce Oracle influence. Potential pushback from Oracle sales and support teams |
Oracle Premier Support is strongest when you require continuous Oracle patches and CPUs, major version upgrades are planned in the near term, Oracle cloud migration is actively underway, or strict regulatory requirements mandate vendor-issued patches. Spinnaker/third-party support is strongest when Oracle systems are stable with no imminent upgrade plans, support costs are disproportionate to value received, you need support for customisations Oracle will not cover, or systems are at or past Oracle's official end-of-life dates.
| Risk | Detail | Mitigation |
|---|---|---|
| Loss of official Oracle updates | Once you leave Oracle support, you permanently lose access to Oracle's official patches, security updates, and new releases. In highly regulated industries, auditors may flag the absence of vendor-issued patches | Top third-party providers develop their own fixes for critical vulnerabilities and guide clients on system hardening. Bolster your environment with strong perimeter defences, effective monitoring, and a robust security response process |
| Licence compliance and audit exposure | Third-party support is legal, but you must remain in full compliance with Oracle's licence terms. Some organisations perceive Oracle becomes more audit-active toward customers who leave support | Track deployments and usage meticulously. Conduct an internal licence audit before and after switching. Continuing to track usage removes one of Oracle's main audit leverage points |
| Oracle reinstatement costs | If you return to Oracle support, Oracle charges back-support fees for lapsed years plus a reinstatement penalty, often 50% of accumulated back fees. Costs can approach the price of purchasing entirely new licences | Budget for reinstatement as a contingency. Ensure you have a clear multi-year technology roadmap. Be confident the systems being transitioned will remain on current versions for a meaningful period before committing |
| No new features or enhancements | Third-party support keeps existing software running reliably but does not deliver new product features or enhancements from Oracle. If you need a new module or major upgrade, you must resubscribe or purchase new licences | Align IT roadmap with support strategy. Identify which systems are candidates for long-term stable operation versus those requiring future Oracle involvement |
| Vendor relationship management | Choosing third-party support can strain your Oracle relationship. You may lose soft benefits: influence in customer programmes, special discounts, Oracle flexibility in other negotiations. Oracle sales may employ fear, uncertainty, and doubt (FUD) tactics | Prepare a fact-based business case. Remain professional in all communications. Document everything. Oracle cannot cancel a perpetual licence for leaving support |
Be mindful of Oracle's "Matching Service Levels" policy. You generally cannot drop support on a subset of licences in a product family while keeping others on Oracle support. Violating this policy could result in Oracle refusing to provide support on the remaining products. Moving to third-party support is typically an all-or-nothing decision for a given product line. Review your Oracle contracts carefully before making any partial transition.
| Planning Factor | Detail |
|---|---|
| Identify ideal candidates | Perform an application portfolio review to pinpoint Oracle systems that are stable, well-understood, and not earmarked for imminent upgrades. These are prime candidates. Systems undergoing transformation or requiring quarterly updates may be better left with Oracle |
| Timing and transition plan | Schedule the switch around critical business cycles and coordinate with your Oracle support renewal date. Before expiry, download all relevant patches, documentation, and knowledge base articles. You will lose access to Oracle's support portal once the contract ends |
| Stakeholder buy-in | Communicate financial benefits and service-quality expectations to the CFO, business unit leaders, and application owners. Set expectations clearly: new Oracle features will not be introduced, but the system will continue running reliably on its current version |
| Monitor and adjust | After transitioning, closely track support performance: response times, resolution quality, and SLA adherence. Establish quarterly service reviews with the provider. Stay independently informed about Oracle product announcements and security advisories |
| Long-term roadmap alignment | Incorporate third-party support into your multi-year IT roadmap. If you plan to decommission an on-premises Oracle system in three years for a cloud migration, third-party support during the interim can yield significant savings. If you foresee needing Oracle's involvement for a future upgrade, plan your re-entry strategy and budget accordingly |
Some organisations allocate a portion of their third-party support savings as a contingency fund in case a return to Oracle support becomes necessary. This approach provides financial resilience and makes the business case even stronger. You capture real savings while maintaining a safety net against future Oracle reinstatement costs.
| # | Recommendation | Priority |
|---|---|---|
| 1 | Vet providers thoroughly. Compare experience, expertise with your specific Oracle products, client references, and legal track record. Ensure the provider has no history of IP misuse or ongoing disputes with Oracle | Critical |
| 2 | Review your Oracle contracts. Check for the "matching service levels" clause and understand which licences must be maintained together. Provide Oracle with required termination notice. Ensure no accidental contract breaches | Critical |
| 3 | Secure systems before switching. Apply all available Oracle patches and back up software installers, documentation, and knowledge articles. This gives your team and the new provider the strongest possible baseline | Critical |
| 4 | Plan for security updates. Ask detailed questions about how the provider handles security alerts and critical bug fixes. Internally, strengthen your security monitoring since Oracle's patch stream will stop | High |
| 5 | Maintain licence compliance. Conduct an internal licence audit to confirm full compliance before and after the switch. Continuing to track usage removes one of Oracle's main audit leverage points | Critical |
| 6 | Align with IT roadmap. Only transition systems that make strategic sense. If a product is slated for imminent replacement or major upgrade, consider timing the support switch accordingly | High |
| 7 | Negotiate flexible terms. Negotiate for 24/7 support, specific SLAs, multi-year discounts, and opt-out clauses. Good providers like Spinnaker are often willing to craft custom contract terms | High |
| 8 | Prepare for Oracle's response. Educate procurement and IT teams about potential Oracle pushback. Maintain a documented business case and remain firm but cordial in communications | Moderate |
| 9 | Build an exit strategy. Even as you enter a third-party agreement, plan for how you would revert to Oracle if needed. Budget for potential back-support fees and ensure integrated vendor support remains intact | High |
| Step | Action | Detail |
|---|---|---|
| 1 | Assess your Oracle portfolio | List all Oracle systems and their current support status. Identify candidates for third-party support (stable, over-budget, or near end-of-life systems) and those that should remain with Oracle (critical systems requiring upcoming upgrades). Build a clear picture of where the switch delivers maximum value |
| 2 | Review contracts and policies | Dive into your Oracle support agreements. Note cancellation windows, restriction periods, and the matching service levels policy. Engage your legal or contract team to confirm compliance with all terms when making the transition |
| 3 | Evaluate third-party providers | Research and compare at least two vendors (for example, Spinnaker Support and Rimini Street). Issue an RFP or conduct interviews focusing on Oracle expertise, support model, security approach, and pricing. Verify cost-saving claims and request relevant client success stories |
| 4 | Plan the transition | Work jointly with the selected provider to create a detailed transition plan: final Oracle support end date, last patch downloads, knowledge transfer sessions, and definition of support processes (ticket submission, severity levels, escalation paths). Communicate the plan to your internal IT team |
| 5 | Execute and monitor | End Oracle support contracts for designated systems and formally cut over. Monitor the initial months closely. Track response times, resolution quality, and emerging issues. Hold a post-transition review to capture lessons learned, then set up regular operational reviews with the provider |
Yes. It is completely legal for Oracle licence holders to use third-party support. Your Oracle software licences are perpetual, granting you the right to run the software even if you stop paying Oracle for maintenance. Oracle's contracts do not forbid obtaining support from an independent provider. Oracle will discontinue its support services and updates once you leave, and you must continue abiding by your licence terms, but Oracle cannot cancel your licences simply because you switched support providers.
Typically, enterprises save approximately 50% of their Oracle support fees annually. For example, if you were paying $2 million per year to Oracle, you could expect to pay roughly $1 million per year to an independent provider for equivalent support. Additional indirect savings come from avoiding forced upgrades (eliminating capital spend on new licences and hardware) and improved negotiating leverage if you ever consider returning to Oracle.
Once off Oracle support, you will no longer receive Oracle's official patches or updates. Instead, your third-party provider monitors Oracle's security bulletins and known vulnerabilities. For critical threats, they develop proprietary patches, scripts, or workarounds to protect your systems. While these are not Oracle-issued fixes, they can effectively secure your environment. Providers also guide you in hardening your system configuration. Apply the same testing and change management rigour to provider-issued patches as you would to Oracle's official updates.
You retain the right to upgrade your Oracle software, but without an active support contract you lack access to Oracle's upgrade media and official assistance. Many organisations either time the move (performing the upgrade while still on Oracle support, then switching) or plan to pay Oracle's reinstatement fee to temporarily resubscribe. Returning to Oracle support is possible, but Oracle charges back-support fees for lapsed years plus a reinstatement penalty, often 50% of those accumulated back fees. This cost can be substantial. It is financially prudent to remain on third-party support until you truly need Oracle's involvement again.
Oracle's reaction is primarily commercial pressure rather than formal retaliation. Expect Oracle's account team to increase outreach, offer special deals to entice you back, or issue compliance warnings. Some organisations perceive that Oracle's audit activity intensifies for customers who leave support, so being fully licence-compliant and audit-ready is essential. You will lose access to Oracle's support portal and entitlements tied to active support. However, many enterprises successfully continue doing business with Oracle in other areas after transitioning. Remain compliant, professional, and data-driven in all interactions.
Redress Compliance provides fully independent advisory with no commercial relationships with any software vendor or third-party support provider. We deliver objective guidance on third-party support evaluations, transitions, licence compliance reviews, and Oracle contract negotiations. 100% vendor-independent. Fixed-fee engagement.
Third-Party Support AdvisoryIndependent advisory on third-party support transition, Oracle licence compliance, audit defence, and contract negotiation. 100% vendor-independent, fixed-fee engagement.