A stable Siebel estate can shed roughly half its annual support bill with no license loss, but the reinstatement math turns the exit into a near one-way door. This is the buyer-side framework for deciding whether the savings justify the risk you are permanently accepting.
A stable Siebel estate can shed roughly half its annual support bill with no license loss, but the reinstatement math turns the exit into a near one-way door. This is the buyer-side framework for deciding whether the savings justify the risk you are permanently accepting.
Let us start with the number that drives every one of these conversations. Oracle charges annual technical support at 22% of the original license fee, and that fee climbs 8% per year under a standard contract. On a $1 million Siebel support line, a third-party provider typically quotes around $500,000, a direct annual saving of roughly 50%. Spinnaker Support markets an average 60% reduction for Siebel customers, and Rimini Street markets up to 50% off annual fees and up to 90% of total support cost once you factor in avoided upgrades and headcount. Those figures are provider marketing, so treat the top-end 90% claim with the skepticism it deserves. In 25 years of negotiating this vendor, the reliable, repeatable number is 50% off the current Oracle line, holding flat while Oracle's own line would compound.
The reason it works is contractual, not clever. Siebel licenses are perpetual. You bought the right to run the software indefinitely, and that right does not depend on paying Oracle support. Support is a separate, cancelable recurring contract. Oracle's agreements do not forbid third-party support, and the practice is legal as long as you stay compliant with your license terms. We cover the boundaries in detail in our guide to whether Oracle third-party support is legal.
The catch sits on re-entry. Oracle's published reinstatement formula, from the Software Technical Support Policies dated July 10, 2026, is 150% of the last annual support fee you paid, applied across every lapsed year, plus the current year's fee. On a $500,000 line reinstated after three years, that is (3 × $500,000 × 150%) + $500,000, which equals $2,750,000. That is not a penalty you pay once; it is the price of admission if you ever want Oracle patches back. Treat the decision to leave as permanent for the products covered.
The exit saves you 50% a year. The return can cost 5.5 times a single year's fee. Decide as if there is no going back, because economically there almost never is.
Third-party support for Siebel covers break-fix, performance tuning, security guidance, and tax, legal, and regulatory updates. You keep all your perpetual licenses and your customizations. You drop only the Oracle support contract and, with it, access to Oracle's official patches and My Oracle Support downloads.
The single most important technical risk to weigh is the security-patch gap. Siebel is an actively patched product. Oracle's Critical Patch Updates in 2026 carried 12 to 14 new Siebel security fixes per quarter, and the majority were remotely exploitable without authentication (13 of 14 in April 2026, 11 of 14 in January 2026, 7 of 12 in June 2026). When you leave, you no longer receive those official fixes. A third-party provider must instead develop its own fixes and, more realistically for critical vulnerabilities, deploy compensating controls such as virtual patching, WAF rules, and network segmentation.
This is the honest limitation of the model. A third-party provider cannot ship a binary patch to Oracle's proprietary code without stepping into the intellectual-property boundary that the Rimini litigation was fought over. What they can do is mitigate the exposure at the perimeter and configuration layer. For an internet-facing Siebel CRM handling regulated customer data, that gap deserves a formal risk assessment signed off by your CISO before you sign anything. For an internal, heavily firewalled estate, the same gap is far more manageable.
| Support element | Oracle Premier Support | Third-party support |
|---|---|---|
| Annual cost (on a $1M line) | $1M, rising 8%/yr | ~$500K, typically flat |
| Perpetual license retained | Yes | Yes |
| Break-fix and performance | Yes | Yes |
| Tax, legal, regulatory updates | Yes | Yes |
| Official Oracle security patches | Yes (12-14 CVE fixes/quarter) | No; provider fixes plus compensating controls |
| New versions and Release Updates | Yes, if entitled | No; you stay on current release |
| Re-entry cost after 3 years | N/A | $2.75M reinstatement to return to Oracle |
The fear that pushes buyers back toward Oracle is that Siebel is a dead product and leaving support accelerates the risk. The facts do not support that fear. Oracle's own Siebel CRM blog, in January 2025, stated there are no plans to end support or innovation and announced extended support through at least 2036. Since April 2018, Oracle replaced the annual Innovation Packs with a continuous Monthly Release Update model. Siebel is a maintained, long-life product, not a sunset one.
That cuts both ways for your decision. Because Oracle will support Siebel through 2036, staying on Oracle premier support keeps a live upgrade path if you genuinely intend to consume new features. But if your estate is stable and you have not applied a meaningful functional Release Update in two or three years, you are paying a rising 22% fee for a roadmap you are not consuming. That is precisely the profile that third-party support is built for. The counterpoint from modernization advisors is fair: Siebel can be extended for years through Open UI and selective integration at a fraction of the cost of a full CRM replacement. Doing that extension on a flat third-party fee rather than a compounding Oracle fee is often the cheaper path, provided your integration work does not require Oracle's newest code.
If your real trajectory is off Siebel entirely, the calculus changes again. A move to Oracle Fusion CX carries its own licensing shift that we break down in migrating from Siebel to Fusion CX. Third-party support can be an excellent bridge during a multi-year migration, funding the transition out of the savings, but only if you sequence the reinstatement risk correctly.
Any Siebel third-party decision made in 2026 has to account for the Oracle versus Rimini Street settlement. Following a June 2025 mediation, a settlement agreement took effect July 7, 2025, and a July 2025 court order stayed the case. Three things matter to buyers.
On the law itself, the direction favors buyers. The Ninth Circuit vacated nearly every material copyright ruling against Rimini, reversed the Lanham Act judgment, set aside the injunction, and called the district court's reading of "derivative work" hopelessly overbroad, holding that mere interoperability is not enough. That precedent narrows Oracle's ability to characterize legitimate third-party fixes as infringing.
The PeopleSoft wind-down is not a Siebel wind-down. Do not let a vendor rep conflate the two to keep you on premier support.
The nuance you must respect: both the 2018 Rimini I Injunction and the April 2025 Rimini II Injunction remain in effect, and the District Court retains jurisdiction to enforce them. Those injunctions govern how a specific provider may build and deliver fixes. They do not make third-party support for Siebel illegal or unavailable. For the full picture across the industry, see our Oracle third-party support comparison for 2026 and the broader Rimini Street and alternatives guide.
For a Siebel estate, we weigh provider selection on legal posture as much as on price, because the two providers with real Siebel practices carry different risk profiles. Spinnaker Support has avoided the litigation that shaped the industry, adhering to stricter protocols on Oracle's support materials and maintaining a more cooperative posture around Oracle's intellectual property. Rimini Street has the largest customer base and deepest Siebel bench, but carries the litigation history and the active injunctions described above.
For a risk-averse organization, particularly in regulated sectors, the marginal price difference between providers matters less than the IP-handling model behind the security fixes. Ask each bidder, in writing, exactly how they source and validate Siebel security fixes, what compensating controls they deploy for the network-exploitable CVEs in Oracle's quarterly CPUs, and what their response SLA is on a critical vulnerability. Get the answer in the contract, not the sales deck.
After 25 years on the buyer side of this vendor, the qualification test is not complicated. Leaving Oracle support for Siebel tends to pay when the estate is functionally stable, when you are not consuming Monthly Release Updates, when your Siebel version is not internet-facing without strong perimeter controls, and when your strategic horizon on Siebel is either "run it as-is for years" or "migrate off entirely." Staying tends to be correct when you are actively consuming new functionality, when unpatched network-exploitable vulnerabilities are an unacceptable compliance risk you cannot mitigate at the perimeter, or when a return to Oracle within two to three years is a live possibility.
Read this decision alongside our estate-agnostic Oracle third-party support decision framework and our support cost reduction strategies that survive renewal, because the strongest position is often not "leave immediately" but "be genuinely ready to leave" as leverage at the next renewal. Oracle discounts move fastest when the exit is credible and the reinstatement math is already on the table.
The bottom line: for a stable Siebel estate not consuming new releases, third-party support is a legitimate way to hold your support cost flat at roughly half of Oracle's compounding line for years. The savings are real. Just make the call knowing the door closes behind you, and size the reinstatement number before, not after, you walk through it.
Expect roughly 50% off your current Oracle support line, which is 22% of license and rising 8% per year. On a $1 million Oracle line, a third-party quote is typically around $500,000 and usually held flat. Provider claims of up to 90% total savings depend on avoided upgrades and headcount, so treat that top figure cautiously.
Yes. Siebel licenses are perpetual, and Oracle's contracts do not forbid third-party support as long as you stay compliant with your license terms. The Ninth Circuit's 2025 rulings narrowed Oracle's copyright theories, though provider-specific injunctions from the Rimini litigation remain in effect and govern how fixes may be built.
Oracle's published formula is 150% of the last annual support fee applied across every lapsed year, plus the current year's fee. Reinstating a $500,000 line after three years costs $2.75 million. The 150% portion is negotiable in practice for large accounts, but you should plan the exit as permanent.
You lose Oracle's official patches, which run 12 to 14 Siebel CVE fixes per quarter, mostly network-exploitable without credentials. Third-party providers cover the gap with their own fixes and compensating controls such as virtual patching and network segmentation. For internet-facing estates, get a CISO-signed risk assessment before committing.
No. Oracle announced extended support for Siebel CRM through at least 2036 and continues Monthly Release Updates. That makes staying viable if you consume new features, and makes leaving safe if your estate is stable and you are not consuming those updates.
Weigh legal posture over sticker price. Spinnaker has avoided the litigation and Oracle IP conflicts; Rimini has the largest Siebel bench but carries active injunctions from the litigation. Either way, put security-fix sourcing and critical-vulnerability SLAs into the contract.
When third party support is the right call for Oracle Database, Apps, and Middleware. Rimini Street, Spinnaker, the savings math, and the leverage even non sw
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
