Short answer: Spinnaker Support for Oracle is a third-party support provider that replaces Oracle Premier Support — Oracle's annual maintenance at 22% of net license value — with equivalent break-fix support, tax/regulatory/legal updates, and security advisory at roughly 50% of Oracle's annual cost, while you keep your perpetual licenses.
Spinnaker Support for Oracle is independent, third-party maintenance for Oracle software. A third-party support provider is a firm that replaces the software vendor's own maintenance contract with equivalent functional support — break-fix engineering, tax/regulatory/legal (TRL) updates, security advisory, and interoperability guidance — delivered without the vendor's involvement. You keep your Oracle perpetual licenses; you simply stop paying Oracle the 22% annual support fee and pay Spinnaker instead.
Spinnaker entered the Oracle and SAP third-party support market over a decade ago and has built a reputation as the more consultative alternative to the market leader, Rimini Street. Where Rimini Street competes primarily on scale and price, Spinnaker positions itself on senior engineering depth and named-engineer relationships — a model that suits enterprises running heavily customized Oracle E-Business Suite, PeopleSoft, JD Edwards, Siebel, and Oracle Database estates that have drifted far from Oracle's standard configurations.
The core proposition is simple and, from a buyer-side view, structurally sound: Oracle's annual maintenance is one of the most profitable, least contestable line items in enterprise IT. Your perpetual license does not expire when you drop Oracle support, so the only question is whether an independent provider can keep your stable Oracle systems running safely for half the cost. For a large class of legacy, non-evolving Oracle products, the answer is yes — and Spinnaker is one of two credible names in that market.
Independent does not mean identical. Spinnaker's support is functionally equivalent to Oracle's, not the same thing. The defining difference is that no third-party provider distributes Oracle's official Critical Patch Updates. You must evidence-test Spinnaker's security model against your own compliance obligations before you switch — not after.
Spinnaker assigns named senior support engineers to an account rather than routing tickets through an anonymous tiered queue. For complex Oracle environments this is the single biggest practical differentiator: the engineer who picks up a production-down EBS incident already knows your customizations, your integrations, and your version history. That continuity is what enterprises with deeply modified Oracle stacks are buying.
The scope of a Spinnaker Oracle contract typically covers technical break-fix support with contractual response SLAs, tax/regulatory/legal updates for products like E-Business Suite Payroll and Financials where statutory changes drive ongoing patch needs, performance and configuration tuning, interoperability advice for new operating systems and browsers, and a defined security program (covered below). Contracts run multi-year with annual increase caps that are materially lower than Oracle's uncapped uplifts.
What Spinnaker cannot do is exactly what the law and Oracle's copyright forbid: it cannot hand you Oracle's proprietary patches or log into My Oracle Support on your behalf. A disciplined provider works strictly inside that boundary, and a buyer-side advisor's job is to confirm in the contract that it does. We treat that contractual confirmation as non-negotiable when we run a third-party support evaluation.
Spinnaker Support typically prices at approximately 50% of your current Oracle annual support fee in year one, with annual increases capped well below Oracle's standard uplift. On a $4M Oracle support portfolio, that is roughly $2M of recurring annual saving — before counting the compounding effect of capped increases over a five-year horizon.
The headline 50% understates the real gap in two situations. First, where Oracle is charging Extended Support premiums on an older release, third-party support removes that premium entirely. Second, where Oracle has already de-supported a version, the comparison is no longer "Oracle vs Spinnaker" but "no support vs Spinnaker." In our engagement data the blended first-year reduction lands between 50% and 62% once Oracle's de-support and reinstatement penalties are stripped out of the baseline (Oracle Licensing Experts, 2026).
| Year | Oracle (≈4% uplift) | Spinnaker (≈50% start) | Annual saving |
|---|---|---|---|
| Year 1 | $4.00M | $2.00M | $2.00M |
| Year 2 | $4.16M | $2.06M | $2.10M |
| Year 3 | $4.33M | $2.12M | $2.21M |
| Year 4 | $4.50M | $2.18M | $2.32M |
| Year 5 | $4.68M | $2.25M | $2.43M |
| 5-yr total | $21.67M | $10.61M | $11.06M |
Figures are illustrative and assume a 3% Spinnaker increase cap versus Oracle's 4% standard uplift; your numbers depend on your support base and contract terms. The point is structural: the saving is recurring and it compounds, which is why a third-party support decision is best modelled over a full contract horizon rather than as a single-year comparison.
We build the five-year financial case, pressure-test the security fit, and prepare your compliance position — independent of Spinnaker, Rimini Street, and Oracle. You see the real number, not a sales number.
No third-party provider — Spinnaker included — distributes Oracle's official quarterly Critical Patch Updates (CPUs). This is the most important fact in any third-party support decision, and any honest assessment leads with it rather than burying it. Oracle's CPUs are copyrighted and tied to an active support contract; handing them to a customer who has dropped Oracle support is the exact conduct Oracle litigates.
Instead, Spinnaker runs an independent security program: continuous vulnerability monitoring against your specific Oracle versions, "virtual patching" and configuration hardening that mitigate a vulnerability at the network or configuration layer rather than in Oracle's binaries, and prioritized advisory guidance when a relevant CVE lands. For a stable Oracle Database behind a firewall serving an internal workload, this model is frequently adequate. For an internet-facing system under PCI-DSS, HIPAA, or FedRAMP obligations that specifically reference vendor-supplied patches, it may not be — and that is a control-framework question you must answer with your security and compliance teams, not a question a provider can answer for you.
The buyer-side discipline here is to forensically map every product you are considering for Spinnaker against its exposure profile and regulatory drivers, and to retain Oracle Premier Support on anything where vendor-supplied patches are a hard control requirement. Third-party support is a portfolio decision, not an all-or-nothing switch.
Third-party support is legal. Your Oracle license grants perpetual use rights that survive the end of Oracle support, and U.S. courts have repeatedly affirmed that customers may obtain maintenance from an independent provider. The long-running Oracle v Rimini Street litigation did not outlaw third-party support — it policed how a provider may build and deliver fixes, drawing a line at copying Oracle's copyrighted software and patches.
Spinnaker's relevance to that litigation is that, unlike Rimini Street, it has not been the defendant in a landmark Oracle copyright case. That is not a guarantee of immunity, but for risk-averse buyers it is a meaningful data point: Spinnaker's model has operated for over a decade without producing the kind of precedent-setting dispute that has shadowed its larger competitor. We still advise clients to read the indemnification and IP-compliance clauses in any third-party support contract closely, because the buyer's protection lives in those clauses.
For the full legal picture — including what the Rimini case established and how to read indemnities — see our deep dive on third-party support legal risk and our broader Oracle third-party support guide.
Rimini Street is the larger, publicly traded market leader with the biggest Oracle support customer base; Spinnaker Support is the smaller, privately held, more consultative provider. Both deliver roughly 50% savings versus Oracle. The decision between them turns on environment complexity and risk posture rather than on price, which is broadly comparable.
| Factor | Spinnaker Support | Rimini Street |
|---|---|---|
| Market position | Smaller, quality-focused | Largest provider, publicly traded |
| Saving vs Oracle | ~50% | ~50% |
| Service model | Named senior engineers | Scale-optimized, tiered |
| Engineer-to-client ratio | Higher (more personal) | Lower (volume model) |
| Oracle litigation history | No major Oracle case | Landmark Oracle litigation, settled |
| Security approach | Vulnerability mgmt + virtual patching | Vulnerability mgmt + virtual patching |
| Best fit | Complex, customized estates | Standardized estates, pure cost focus |
Neither provider is universally "better." A heavily customized PeopleSoft and EBS estate with statutory payroll requirements often gets more value from Spinnaker's named-engineer continuity; a large, standardized Oracle Database fleet where the objective is purely to halve the bill is well served by either. The right answer comes from a structured RFP with reference checks against enterprises that look like you — which is the process we run on the buyer's behalf. For a head-to-head with Oracle's own support, see our Oracle support vs Rimini Street comparison.
The product-selection decision determines whether a third-party support move creates value or risk. The strongest Spinnaker candidates are stable products where you are not consuming Oracle's roadmap: Oracle Database 11g, 12c and 19c on settled workloads; E-Business Suite 12.1 and 12.2 with no active functional upgrade planned; PeopleSoft and JD Edwards in steady-state; and Siebel CRM, which most enterprises already run in maintenance mode.
Poor candidates are Oracle Database 23ai, where Oracle's current roadmap genuinely adds value; Oracle Fusion Cloud and other SaaS subscriptions, which are not perpetual licenses and sit outside the third-party support model; Oracle Java SE, where licensing is shifting fast and Oracle's own options can be strategically important; and any product with an active upgrade or OCI migration scheduled inside 24 months, because reinstating Oracle support to enable an upgrade triggers back-support fees that erode the savings. We quantify that reinstatement exposure in our analysis of Oracle support reinstatement fees.
Before any switch, a forensic Oracle compliance review is non-negotiable. Moving to third-party support with an unresolved compliance gap is the worst possible time to discover it, because once Oracle support is terminated your relationship with Oracle's LMS team is adversarial and your back-licence exposure is at its most expensive. A clean position, confirmed before you give notice, is what removes Oracle's leverage. One global insurer we advised cut $2.8M a year this way — the full numbers are in our insurance third-party support case study.
Yes. Your Oracle perpetual licenses grant indefinite use rights that are not contingent on Oracle support, so you can drop Oracle Premier Support and contract Spinnaker to maintain those products. The lawful boundary is technical: a third-party provider cannot distribute Oracle's copyrighted patches or access Oracle's support portal. Spinnaker operates within that boundary using its own break-fix engineering and security advisory.
Spinnaker typically prices at about 50% of your current Oracle annual support fee, with smaller annual increase caps than Oracle's uncapped uplifts. On a $4M Oracle support base that is roughly $2M saved in year one. Across our engagements the blended first-year reduction lands between 50% and 62% once Oracle's de-support and reinstatement penalties are removed from the baseline (Oracle Licensing Experts, 2026).
No third-party provider distributes Oracle's official Critical Patch Updates. Spinnaker delivers its own security model: vulnerability monitoring, virtual patching and configuration hardening, and workaround guidance developed without Oracle source code. For internet-facing or PCI-DSS, HIPAA, or FedRAMP-regulated systems, confirm this satisfies your control framework before switching.
Rimini Street is larger, publicly traded, and competes on scale and price; Spinnaker is smaller, more consultative, with higher senior-engineer ratios and no major Oracle litigation history. For complex, heavily customized Oracle environments Spinnaker's named-engineer model often wins; for standardized estates focused purely on cost, both deliver similar savings.
The strongest candidates are stable, non-evolving products: Oracle Database 11g/12c/19c, E-Business Suite 12.1/12.2, PeopleSoft, JD Edwards, and Siebel where you are not consuming Oracle's roadmap. Poor candidates are Oracle Database 23ai, Fusion Cloud SaaS, and any product with an active upgrade or OCI migration planned in the next 24 months.
Oracle follows a standard playbook: an executive escalation call, a discounted support counter-offer tied to a multi-year commitment, and sometimes increased audit attention from Oracle LMS. None of this is a legal barrier. A clean license position confirmed by a pre-transition compliance review removes Oracle's leverage and lets you use the counter-offer as negotiation evidence.
We evaluate Spinnaker, Rimini Street, and an Oracle-discount counter-strategy side by side, prepare your compliance position, and negotiate on your behalf. No provider commissions. No Oracle agenda.
Weekly briefing on Oracle support trends, third-party support developments, and cost reduction tactics — read by 2,000+ Oracle stakeholders at Fortune 500 enterprises.
Independent. Buyer-side. Not affiliated with Oracle Corporation.
We analyse your full Oracle portfolio, model Spinnaker against Rimini Street and an Oracle-discount counter-strategy, prepare your compliance position, and manage the negotiation. No Oracle agenda. Pure buyer-side analysis.
Not affiliated with Oracle Corporation. 100% independent, buyer-side advisory.