Third party support is maintenance and support for Oracle software provided by an independent firm rather than by Oracle itself. The best known providers, Rimini Street and Spinnaker Support among them, support Oracle Database, middleware, and applications at roughly half the annual cost of Oracle premier support, and in some cases less. For organisations running stable, mature Oracle estates that no longer need new functionality, third party support is the single most powerful cost reduction available, and it anchors the credible alternative that gives buyers leverage in every Oracle support renewal.
The decision is consequential because it is not easily reversed. Leaving Oracle support means leaving the upgrade and patch stream, and returning later triggers the reinstatement penalty analysed in the support reinstatement guide. A buyer should therefore approach third party support not as a casual cost saving but as a strategic decision about the future of the affected products, made with a clear view of both the savings and the trade offs.
What is Oracle third party support?
Third party support providers employ engineers who maintain Oracle products independently of Oracle. They provide break fix support for issues that arise, tax, legal, and regulatory updates for applications such as E Business Suite and PeopleSoft, and security advisory services, frequently including their own remediation guidance where Oracle patches are no longer available to the customer. They support the product version the customer is running at the point of transition, and they commit to supporting it for a long, defined period, often fifteen years or more, regardless of Oracle lifecycle dates.
What they cannot provide is anything that requires Oracle intellectual property the customer is not entitled to outside an active support contract. That means no Oracle produced patches or upgrades, no new product versions, and no access to My Oracle Support. The provider works with the rights the customer already holds in its perpetual licences, supporting the software as it stands rather than evolving it. For a stable estate this is sufficient; for one that needs Oracle innovation it is not.
What you save and how the economics work
The headline saving is the support fee itself. Third party providers typically charge around fifty percent of the Oracle support fee, and because Oracle support is priced at roughly twenty two percent of the net licence cost with an annual uplift, the saving compounds. The table below models a stable estate over five years, comparing Oracle premier support with an annual uplift against flat third party support at half the initial Oracle rate.
| Year | Oracle premier support (4% uplift) | Third party support (flat) | Annual saving |
|---|---|---|---|
| Year 1 | 1,000,000 | 500,000 | 500,000 |
| Year 3 | 1,082,000 | 500,000 | 582,000 |
| Year 5 | 1,170,000 | 500,000 | 670,000 |
| 5 year total | 5.42m | 2.50m | 2.92m |
The five year saving in this model is nearly three million dollars, and it widens every year because Oracle support escalates under its annual uplift while third party support is typically held flat. The economics are most compelling precisely for the estates Oracle most wants to keep on support: large, stable, fully deployed bases where the support fee is high and the need for new Oracle functionality is low.
Third party support does not make Oracle software cheaper. It makes maintaining software you already own cheaper, which is a different and often better question.
What you give up by leaving Oracle support
The trade offs are concrete. The customer loses access to Oracle patches and upgrades, so the product is frozen at its current version for as long as third party support continues. This is acceptable for a mature application the business does not intend to evolve, and unacceptable for one on an active upgrade path. The customer also loses access to My Oracle Support and Oracle produced security patches, relying instead on the provider virtual patching and remediation, which is competent but is not the vendor patch.
There is also a strategic consideration: leaving Oracle support narrows future options. Returning to Oracle support requires paying the reinstatement penalty, and a customer outside the support relationship has less standing in any future negotiation for new products. These are real costs, but they are costs of a strategic choice to stop investing in the affected products, which is frequently the correct choice for a mature estate. The interaction with Oracle lifecycle phases is examined in the premier versus sustaining support guide.
Is Oracle third party support safe?
Third party support is lawful and widely used. The customer continues to own its perpetual licences and retains the right to run the software; third party support simply changes who maintains it. The principal risk is not the support itself but the licensing position underneath it, because moving to third party support removes the customer from Oracle direct oversight and can prompt an audit, particularly around the transition. A customer that is not confident of its compliance position should resolve that position before transitioning, since an audit defended without an active support relationship is more adversarial.
The practical safeguards are to enter third party support from a clean, well documented compliance baseline, to retain all licence and support records proving entitlement, and to manage the transition so that no gap in support coverage arises. The audit risk is real but manageable, and it is the reason third party support decisions should be taken alongside an audit readiness review rather than in isolation, as set out in the firm audit defence service.
When third party support fits
Third party support fits an estate that is stable, mature, and not on an active Oracle upgrade path. The clearest candidates are applications running a version the business is satisfied with and intends to keep for years, databases supporting legacy systems, and any product Oracle has moved into a later lifecycle phase where new Oracle development has effectively ceased. For these, the customer gains nothing from Oracle upgrades it will never apply, and third party support converts that unused entitlement into a halved bill.
It does not fit products on an active roadmap, where the customer genuinely needs new Oracle releases, nor estates with unresolved compliance exposure that an audit could crystallise. For these the right path is usually to resolve the position and stay on Oracle support, or to migrate, rather than to leave support with risk unaddressed. The decision belongs within the broader support cost reduction strategy rather than as a standalone tactic.
Executing the exit without losing leverage
Even where a customer intends to stay on Oracle support, a credible, documented third party support option is the strongest single lever in the renewal negotiation. Oracle responds to the genuine prospect of losing the support revenue altogether in a way it does not respond to a request for a discount. The exit option, whether exercised or held in reserve, should therefore be developed as part of every significant renewal, a point developed in the renewal licensing white paper.
Where the exit is to be executed, timing matters. The transition should be planned so that the move to third party support occurs cleanly at the support period boundary, with no lapse, and with the compliance baseline documented in advance. Reinstatement should be treated as effectively permanent, so the decision should be made only when the organisation is confident the affected products will not need to return to Oracle support, a calculation the reinstatement guide sets out in full.
The buyer side view
The buyer side view of Oracle third party support is that it is the most powerful cost lever available for a mature Oracle estate, and simultaneously the most powerful negotiating lever for one that intends to stay. Its value is highest exactly where Oracle support is most expensive and least useful: large, stable, fully deployed bases that need no new Oracle functionality. The trade offs, the loss of patches and upgrades and the cost of return, are real but are the natural consequences of deciding to stop investing in the affected products.
The disciplined response is to identify the stable, upgrade complete portions of the estate, model the multi year saving against the Oracle uplift, resolve any compliance exposure before transitioning, and use the credible exit option to extract better terms even where the intention is to remain. Read the cost reduction guide and the lifecycle support guide for the surrounding analysis, weigh the engagement economics through the firm engagement model, and treat third party support as a strategic decision about the future of the estate rather than a simple invoice reduction.
Maintenance provided by an independent firm rather than Oracle, at around half the cost, covering break fix, regulatory updates, and security guidance but not Oracle upgrades or patches, as the renewal pillar describes. Around fifty percent initially, widening each year because Oracle escalates under its annual uplift while third party support is held flat. Yes; the customer keeps its perpetual licences. The main risk is the licensing position, since the move can prompt an audit, so resolve compliance first with the firm audit defence service. Oracle patches, upgrades, and My Oracle Support access, and return triggers the penalty in the reinstatement guide.Oracle third party support: frequently asked questions
What is Oracle third party support?
How much can I save?
Is it safe?
What do I lose?