The decision rule: third-party support fits a stable estate that plans no version upgrades, no new Oracle purchases and no OCI Bring Your Own License footprint — there, roughly halving the support line outweighs losing Oracle’s patch stream. The moment any of those plans exist, the exit forfeits more than it saves, because BYOL eligibility, Support Rewards and the path back are all priced against the leaver.
Published 8 January 2026 · Last reviewed 8 January 2026
Oracle technical support is an annual stream priced as a fixed share of the net license fee, renewing with periodic uplifts, and it buys four things at once: new patches and critical patch updates, version upgrades under the lifetime support policy, service requests against My Oracle Support, and — less visibly — eligibility for programs that assume an active support relationship, OCI Bring Your Own License and Support Rewards chief among them. Oracle’s lifetime support policy stages what that stream delivers over a product’s life: Premier support for the first years, Extended support for a further period at an uplift, then Sustaining support indefinitely — which keeps the invoice arriving but stops new patches, new certifications and new fixes.
Third-party support replaces that stream with a contract from an independent provider — a category with several established firms serving thousands of Oracle customers between them — typically at around half the annual cost, often with longer coverage commitments on versions Oracle has moved to Sustaining. What it cannot include is anything copyrighted that Oracle ships after you leave: no new Oracle patches, no upgrades, no My Oracle Support. Providers substitute their own engineering — custom fixes, configuration-level security measures sometimes described as virtual patching, and support for customizations Oracle’s own policies exclude.
The comparison is therefore not like-for-like on any single axis. One side sells the vendor’s future output; the other sells cheaper, often more personal, maintenance of the present. Which of those an estate actually needs is the whole question.
This comparison touches a commercial dispute in which Oracle and third-party providers make opposing claims. Both positions are stated here factually; nothing on this page is legal advice, and the right answer depends on your contracts and your roadmap. The page names no advisory firms; the firm directory lists Oracle-capable advisors with balanced pros and cons, listed, not ranked.
| MECHANIC | ORACLE SUPPORT | THIRD-PARTY SUPPORT |
|---|---|---|
| What you pay | Fixed share of net license fee, annually, with periodic uplifts | Indicatively around half the Oracle stream for the same scope |
| Patches & upgrades | New patches, CPUs and version upgrades while in Premier/Extended; Sustaining stops new fixes | No Oracle-shipped patches or upgrades; provider-built fixes and configuration-level security measures |
| Coverage horizon | Staged by lifetime support policy per version | Multi-year commitments on the version you run, including versions Oracle has aged out |
| Customizations | Outside standard support scope | Commonly included in scope |
| Cloud interplay | Preserves OCI BYOL eligibility; consumption earns Support Rewards against the support bill | Ends BYOL eligibility for the affected licenses; no Support Rewards to earn or offset |
| Granularity | Matching Service Levels: one support level per license set | All-or-nothing per license set, for the same reason |
| Exit / return | Leaving is immediate; returning prices in the lapsed years plus a reinstatement uplift | Returning to Oracle later is the priced-in risk of the whole move |
| Where it fits | Estates that upgrade, buy, or run Oracle cloud; regulated stacks wanting vendor patches | Stable, mature or sunsetting estates with no Oracle roadmap |
The row that decides most cases is the cloud one. Since OCI BYOL requires active Oracle support on the brought licenses and Universal Credits consumption earns rewards only against an Oracle support bill, a third-party move and an Oracle cloud strategy cannot coexist on the same entitlements. Estates run the comparison license set by license set for exactly this reason.
Three of Oracle’s published policies shape every exit. Matching Service Levels requires all licenses in a license set to carry the same support level, which converts “drop support on the shelfware” into “drop support on the whole set or none of it.” Repricing means that terminating part of an order can cause support on what remains to be recalculated at less favorable rates — the saving on the terminated slice partly reappears on the surviving one. Reinstatement prices the way back: the lapsed fees for the uncovered period, an uplift of half as much again, and the current year — arithmetic that makes a short-term exit followed by a return roughly a wash, and which is the reason exits are planned as multi-year positions or not at all.
The operational step that cannot be skipped: archive before you leave. Entitled patches, updates and installation media remain downloadable only while support is active; after the lapse date the download right is gone even though the license to run the software is not. A disciplined exit project snapshots everything the estate is entitled to — and establishes a clean license position first, because the compliance state freezes with the relationship. That pre-exit baseline is standard scope for an Oracle compliance assessment, and the contractual fine print around license sets and repricing is exactly the terrain an Oracle licensing advisory engagement covers.
One structural exclusion: a live Unlimited License Agreement keeps support inseparable from the deal — support on ULA programs cannot be shed mid-term, so the third-party question only opens at certification or renewal.
Oracle’s position, stated in its policies and its public messaging, is that a customer who terminates support is choosing not to receive Oracle’s security patches and updates — that nobody else can ship Oracle’s code, so leaving means running on the fixes you have. Oracle also points to what only the vendor can provide: new certifications, new versions, and the program eligibility described above.
Providers’ position, equally factual, is that customers are not choosing to go unpatched but choosing differently engineered protection — provider-built fixes and configuration-level hardening — for systems that are often so stable, customized or near end-of-life that Oracle’s own lifetime policy has already stopped shipping them new fixes. On Sustaining-support versions, they note, the patch-stream argument largely falls away, since Oracle support at full price no longer delivers new patches for that version either.
What the courts have established is narrower than either marketing position. The model itself — supporting software someone else licensed — is lawful. The long-running litigation between Oracle and the largest provider in the category turned on how support was delivered (copying, cross-use and process questions), produced injunctions that remain in force, and was settled in 2025, with that provider winding down support for one Oracle product line by mid-2028. The practical consequence for buyers is a diligence question, not a verdict: providers differ in process, and the established ones document how their methods differ from those the courts examined. This is information, not legal advice.
The third-party case is strongest where the estate is stable and the roadmap is flat: mature E-Business Suite, Siebel or database versions running well, no upgrade planned, no new Oracle purchases coming, versions already in or near Sustaining support, sunsetting applications being run out over a known horizon, and heavy customizations Oracle would not support anyway. There the move converts a large fixed line into a smaller one without changing what the estate actually receives day to day.
Staying with Oracle is the structural answer wherever the future involves the vendor: an OCI migration on BYOL terms, Support Rewards offsetting the support bill, a planned upgrade or new version dependency, a live ULA, regulated workloads whose auditors expect vendor-issued patches, or ISV stacks certified only against supported configurations. In those estates the support stream is not really a maintenance fee — it is the admission ticket to the rest of the relationship, which is why Oracle prices exit and re-entry the way it does.
The traps repeat across cases. Modelling the saving on the shelfware slice and discovering Matching Service Levels mid-project. Forgetting repricing on the surviving support. Leaving without archiving entitled patches. Exiting licenses a cloud business case needs for BYOL two years later. Treating the move as reversible when reinstatement arithmetic says otherwise. And signing with a provider without the process diligence the litigation history makes prudent. Every one of these is visible in advance to anyone who reads the policies — which is the argument for running the numbers with an independent advisor before, not after, the renewal notice date.
The cloud program that depends on active support →
Where Support Rewards are earned →
The moment the support question opens →
How to pick the firm for this work →
Firms that model support-exit decisions →
Every field guide on the site →
Access to My Oracle Support ends: no new patches, critical patch updates, security alerts, version upgrades or service requests from Oracle. The perpetual license itself survives — the right to run what you own is not support-dependent — but the right to download anything new stops the day coverage lapses, which is why estates archive every entitled patch and version before the exit date. Leaving also ends OCI BYOL eligibility for the affected licenses and forfeits Support Rewards accrual.
Oracle’s technical support policies require all licenses within a license set to carry the same support level — an estate generally cannot drop support on a subset of licenses in a product family while keeping the rest on Oracle support. In practice this makes the third-party decision all-or-nothing per license set, and it is the single most common surprise in exit planning: the saving has to be modelled on the whole set, not the shelfware slice.
Yes, but the path back is priced to deter. Oracle’s published reinstatement mechanics charge the lapsed support fees for the uncovered period plus a reinstatement uplift of half as much again, with the current year added — so the longer the absence, the more the return costs. Estates that anticipate needing Oracle support again within a few years usually find the round trip consumes much of what the exit saved. Negotiated re-entry as part of a new purchase or cloud commitment is sometimes available, but it is a negotiation, not an entitlement.
Directly. Bring Your Own License on OCI is conditional on the brought entitlements carrying active Oracle support for the whole period of cloud use, so an estate on third-party support is outside the BYOL program for those licenses. Support Rewards — the credit OCI consumption earns against the on-premise support bill — likewise requires a support stream to offset. An Oracle cloud roadmap and a third-party support move are, for the same licenses, mutually exclusive.
The model itself is lawful — a licensee may engage a third party to support software it is licensed to run. The boundaries are about how that support is delivered: the long-running litigation between Oracle and the largest provider in the category turned on copying and process questions, produced injunctions that remain in force, and was settled in 2025 with a wind-down of that provider’s support for one Oracle product line by mid-2028. Buyers evaluating providers ask how their processes differ from those the courts examined. This is information, not legal advice.
There is no published Oracle policy of auditing customers who leave support, and Oracle does not describe support status as an audit criterion. Practitioners and providers report, factually, that customers weigh audit exposure when planning an exit, and that a clean compliance position established before the move removes most of the leverage either way. Treating a pre-exit compliance assessment as part of the project cost is the standard mitigation.
Deciding whether the support stream should live or die — against your real roadmap, your license sets and your cloud plans — is exactly what an Oracle licensing advisor is for. The directory lists the firms that do this work, with balanced pros and cons, listed, not ranked.
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.