Independent third-party support for products such as Oracle, SAP, and VMware by Broadcom typically costs about 50 percent of the vendor's annual maintenance fee, extends support on stable releases for ten years or more, and removes the mandatory upgrade treadmill that drives much of the vendor's recurring revenue. The savings are real and large, but the decision is not only financial. Moving to independent support changes what you can call the vendor for, alters your upgrade path, and carries legal questions that depend heavily on which products you move and how the provider delivers fixes.
What third-party support is
Third-party support is maintenance for licensed software delivered by an independent provider rather than the software publisher. You keep your perpetual licenses and the right to run the software, but instead of paying the vendor's annual maintenance, you pay an independent firm to handle break-fix support, tax and regulatory updates, performance tuning, and security guidance. The model exists because vendor maintenance on mature, stable products is priced as if you were still receiving heavy ongoing development, when in reality a stable release needs far less. For a system that works and that you do not intend to upgrade, the vendor's maintenance fee buys access to updates you will never install and a support line you rarely call, which is exactly the spend an independent provider undercuts.
The providers and what they cover
The independent support market is led by a small number of established firms that support the major enterprise vendors, alongside specialists focused on particular products. Coverage generally includes incident support with response-time commitments, fixes for issues the vendor would address, tax, legal, and regulatory updates for applications such as payroll and finance, interoperability and security advisory, and in many cases more personalized service than the vendor's tiered support delivers. What the providers cannot give you is new vendor releases, new features, or vendor-issued patches, because those remain the publisher's intellectual property. For a buyer running a stable version with no roadmap need, that exclusion costs nothing. For a buyer who wants the next release, it is the whole point of staying on vendor support.
| Dimension | Vendor maintenance | Third-party support |
|---|---|---|
| Annual cost | Full list maintenance | Roughly 50% of vendor fee |
| New releases and features | Included | Not available |
| Break-fix and tuning | Tiered, often slow | Personalized, response-time backed |
| Tax and regulatory updates | Included | Provided independently |
| Upgrade pressure | Built into the model | Removed |
The savings and where they come from
The headline saving is the roughly halved annual fee, but the larger figure is the avoided cost of the upgrade cycle that vendor support is designed to drive. A vendor that ends support for your version on a fixed date forces an upgrade you may not need, and the project cost of that upgrade often dwarfs the maintenance fee itself. Independent support breaks that cycle by maintaining your current version for as long as you choose to run it, which converts a forced multi-year upgrade program into an optional one timed to your own business case. On a large estate, the combined saving from the halved fee and the deferred upgrade can fund a significant part of a transformation budget, which is why finance teams increasingly raise the option even when IT is cautious about it.
The lever even if you never switch: A credible quote from an independent provider is the strongest single input to a vendor maintenance negotiation. The vendor would rather discount your renewal than lose the maintenance stream entirely, so a documented third-party alternative at half the price resets the conversation even when you intend to stay. The option has value whether or not you exercise it, and getting the quote costs nothing but the request.
What you keep and what you give up
You keep your licenses, your right to run the software, your data, and continuity of support, often at a higher service level than the vendor provided. You give up access to new releases, vendor patches, and the ability to open a ticket with the publisher, and you accept that returning to vendor support later will trigger a reinstatement cost. That return cost is the factor most buyers underweight, because the vendor reconstructs the maintenance you skipped and adds a penalty, which our guide to back maintenance charges covers in detail. The practical risk is therefore not that independent support fails to maintain the product, which it generally does well, but that you later decide you need vendor releases and face an expensive path back. That is why the switch suits products you are confident you will run unchanged, and fits poorly with products on an active roadmap you intend to follow.
The legal questions to weigh
Independent support has been the subject of significant litigation between providers and vendors, centered on how fixes are developed and whether the provider's processes infringe the vendor's intellectual property. The settled position is that running your own licensed software with independent help is lawful, but the way a provider creates and delivers fixes matters, and reputable firms have adjusted their processes in response to court rulings. The practical implications for you are to choose an established provider with a defensible delivery model, to keep your own license documentation in order so your right to run the software is never in question, and to understand that dropping vendor support can itself attract attention, which is why the move should be paired with a clean compliance position. Stepping off the vendor's stream is also a moment to confirm your software escrow or source-access protections where the product is critical.
When the switch makes sense
Third-party support fits a clear profile: a stable, mature product, a version you intend to keep running, no near-term need for vendor releases, and a maintenance fee large enough that halving it matters. It fits poorly where you plan to upgrade soon, where you depend on a steady stream of vendor patches, or where the product is small enough that the saving does not justify the transition effort. The decision should be modeled, not assumed, weighing the annual saving and avoided upgrade cost against the reinstatement exposure and the loss of new releases, much as our guide to the broader risks of dropping vendor support sets out. The same negotiation discipline in our software contract negotiation guide applies whether you switch or use the option as leverage, and a structured analysis through our software licensing advisory service will price the move product by product and manage the transition so you do not break compliance on the way out. For the right products, independent support is one of the largest and most durable cost reductions available in enterprise software, and for the wrong ones it trades a manageable fee for a costly return path. Knowing which you are looking at is the entire decision.