Guide · Oracle · Support
Oracle Third Party Support Providers. How to choose.
Two providers of scale, a long tail of specialists, and one hard constraint: no Oracle patches after you leave. Score fit before you score price.
Two providers of scale, a long tail of specialists, and one hard constraint: no Oracle patches after you leave. Score fit before you score price.
Oracle third party support is supplied by two publicly reported scale providers and a long tail of specialists. The right one is decided by your module and version list, not by brand.
The saving is real and large. So is the constraint: the day you leave, Oracle patches, upgrades and new regulatory updates stop arriving.
This page is the selection framework we use on the buyer side. Read it with the third party support guide and the legal position.
Two providers operate at scale across database, middleware and applications, and a set of specialists cover narrower product lines. Rimini Street is publicly listed and files audited results and litigation disclosure with the United States Securities and Exchange Commission.
Spinnaker Support is the other broad provider. Below them sit firms that specialize by product line, by region, or by regulatory jurisdiction. Provider scope changes, so read the current disclosures rather than a two year old comparison.
A listed provider publishes audited financials, customer concentration and litigation status. You can read the risk factors instead of asking for them. That is a genuine diligence advantage on a contract you intend to run for five years or longer.
It is not a quality signal by itself. A specialist with 40 engineers who have shipped PeopleSoft tax updates for a decade can serve a PeopleSoft estate better than a larger firm with two people on that product.
You are buying incident response, break fix engineering, and, where offered, tax, legal and regulatory updates written by the provider. You are not buying Oracle intellectual property, and no provider can give you it.
Providers price against your current Oracle bill, and the usual anchor is a cut of about 50 percent to the annual fee. Oracle's Premier Support for technology programs runs at 22 percent of net license fees per year, so the arithmetic starts from a number you already know.
Oracle's Software Technical Support Policies also reserve the right to apply renewal adjustments each year. In the renewals we reviewed in 2024 and 2025, uplift landed between 0 and 4 percent depending on whether a cap had been negotiated into the original order.
Five year cost picture on a 5 million dollar net license estate
| Line | Stay on Oracle | Move to third party |
|---|---|---|
| Year 1 support fee | 1,100,000 at 22 percent | 550,000 at the usual anchor |
| Annual uplift assumption | 0 to 4 percent | Often fixed for the term |
| Five year gross fees | 5.5 to 6.0 million | 2.7 to 2.9 million |
| New Oracle patches | Included while in Premier | None after termination |
| Upgrade rights | Included | Lost from the termination date |
| Cost to return in year 3 | Not applicable | 150 percent reinstatement plus back fees |
Four costs sit outside the support line and are routinely missed. Each one has moved a decision we worked on.
Check fit and contract language, in that order, before you look at price. The provider must name every module and version you run, state which jurisdictions it writes regulatory updates for, and stand behind its own method in writing.
A sales answer of yes we support PeopleSoft is not coverage. Coverage is a named schedule listing product, version, PeopleTools release, localization and interface, attached to the agreement and updated when your estate changes.
Every gap we have seen turn into an incident was visible in the schedule before signature. Nobody read it against the actual estate inventory.
Tax, payroll and statutory reporting updates are the highest risk area in an applications move. They are time bound, legally mandated, and they do not tolerate a late delivery.
Ask for the last two years of delivery dates by jurisdiction against the statutory deadline. A provider that tracks this will have the table ready. One that does not is telling you something.
Provider evaluation matrix
| Criterion | What good looks like | What it costs you to get it wrong |
|---|---|---|
| Module coverage | Named schedule, every version | An unsupported module found during an incident |
| Regulatory updates | Jurisdiction list plus delivery history | A late payroll filing and a regulator letter |
| Security model | Documented controls your CISO signs off | An unpatched exposure with no vendor fix |
| Indemnity | Defense and settlement, no method carve out | You fund your own defense |
| Service levels | Severity based, with a credit remedy | Best efforts on a production outage |
| References | Same product line, similar scale | You are the reference customer |
| Exit terms | Notice, handover, artifact return | A blocked or expensive move back |
They do not patch the code. They reduce and watch the attack surface instead, because Oracle's Critical Patch Updates are Oracle intellectual property and cannot lawfully be redistributed by a third party.
Oracle publishes its patch cadence and advisories on its Critical Patch Update and Security Alerts pages. Read the last eight quarters for your products before you decide. That is the stream you are giving up.
Take these to the provider before you take the proposal to the board. In our experience they decide whether security signs the paper.
Sustaining Support and third party support are not the same thing, and the difference is expensive. Sustaining Support is still an Oracle contract at the same 22 percent fee.
Under Oracle's policy, Sustaining Support gives you access to updates, fixes and patches created during Premier and Extended Support, but no new ones, no new tax or regulatory updates, and no 24 hour Severity 1 commitment.
Sustaining Support is the worst of both worlds at full price. If the estate is stable enough for Sustaining Support, it is stable enough to price the alternative properly.
Oracle prices reinstatement at 150 percent of your last annual support fee, and its published policies say so plainly. That number, plus the fees for the lapsed period, is the price of changing your mind.
The Oracle Software Technical Support Policies state that where support lapsed, the reinstatement fee is 150 percent of the last annual technical support fee paid for the relevant program. Where support was never bought, it is 150 percent of the fee that would have applied at the time of reinstatement.
Oracle's policies require all licenses in a license set to sit at the same support level. You cannot quietly move half the estate and keep the rest supported.
The practical consequence is that partial moves force license terminations, and Oracle then reprices the survivors at current list less your standard discount. Model that before you scope a partial move, not after.
While you still hold a support contract you still hold access to My Oracle Support. That access ends when the contract ends, and with it your ability to pull anything down.
The standard advice is to pick the largest provider because scale means safety. We disagree. In roughly 18 of the 30 selections reviewed across 2024 and 2025, the deciding factor was whether the provider covered the exact module and version set with an indemnity that survived termination, not how big it was. A large provider that supports your product line thinly is weaker than a specialist that lives in it. Score every provider against your estate schedule and your indemnity requirements first, then use scale as a tiebreaker rather than as the headline criterion.
Run it as a structured procurement over about ten weeks, with the estate inventory finished before any provider sees a requirement. A single quote against an unverified estate is how bad selections happen.
Termination has to land cleanly against the Oracle support anniversary. Notice periods on Oracle support renewals are unforgiving, and a missed date buys another full year at 22 percent.
Work backwards from the anniversary: notice date, archive window, provider onboarding, and knowledge transfer. Give the archive window more time than feels necessary.
Source: Redress Compliance advisory engagement file, 2024 to 2025, and Oracle published support policies.
Stable estates on mature releases suit it. Estates in motion do not, because you cannot take an Oracle upgrade after you leave.
That single constraint decides most cases. Ask how long you intend to run the current release, then answer honestly rather than optimistically.
Work the sequence below. It takes about ten weeks and it removes almost all of the risk people associate with this decision.
Rimini Street, which is publicly listed, and Spinnaker Support are the two providers of scale, alongside product and regional specialists. Which one is right depends on coverage of your exact modules and versions rather than provider size. Read the current filings and scope statements, because provider coverage changes year to year.
Providers usually anchor at about half of your current Oracle support fee, which itself runs at 22 percent of net license fees per year. The real comparison is over five years and must include repricing of any licenses you keep with Oracle, forfeited Support Rewards, and the internal engineering you take on.
Yes. From the termination date you receive no new Oracle Critical Patch Updates for the affected programs, because those patches are Oracle intellectual property. Providers substitute virtual patching, hardening, segmentation and monitoring, which your security team has to accept in writing before you sign.
Oracle's published technical support policies price reinstatement at 150 percent of the last annual technical support fee you paid for the relevant programs. You should also expect to pay for the lapsed period, so a return in year three is materially more expensive than most business cases assume.
Rarely, and not quietly. Oracle's matching service levels rule requires every license in a license set to sit at the same support level, so a partial move usually forces termination of the rest of that set. Oracle then reprices the surviving licenses at current list less your standard discount.
Independent support of software you already licensed is lawful as a business model, and United States courts have never held otherwise. What the Oracle and Rimini Street litigation tested was how a provider may build and deliver updates, which is exactly why indemnity language matters. The detail is set out on our page on the legal position.
No. In the selections we reviewed, coverage of the exact module and version set predicted satisfaction far better than provider revenue. A specialist whose engineers have shipped fixes on your release will usually outperform a larger firm with a thin bench on that product.
About ten weeks for a structured selection, and the estate inventory is the long pole. Baseline and inventory take four weeks, the requirement and scoring another four, and contract negotiation two, assuming your security review runs in parallel rather than at the end.
Redress runs Oracle support provider selection inside the Vendor Shield subscription, the Renewal Program, and the Benchmark Program, led on the buyer side by a former Oracle licensing executive. We do not resell support and we take no fee from any provider.
Read the related Oracle services page, the Oracle knowledge hub, the Oracle support costs analysis, the support options comparison, and the contact page.
The buyer side moves that keep your Oracle estate honest at renewal.
Independent. Buyer side. Built for Oracle customers running the next renewal cycle.
Open the white paper in your browser. Corporate email only.
Open the Paper →
Renewal in twelve months. Audit notice in the inbox. RFP on the desk. We start where you are.
Provider scope changes, security models, indemnification terms, selection benchmarks, and support market intelligence from every Oracle engagement we run on the buyer side.
