① Explainer · Licensing concepts
Independent support firms maintain licensed mainframe software for less than vendor maintenance, on products you do not plan to upgrade. The saving is real and the lever it gives you at renewal is larger. Here is the trade, a decision matrix, and a worked annual comparison.
Keep the license. Change who answers the phone.
Third party support is maintenance for licensed software delivered by an independent firm rather than the publisher. On the mainframe, providers such as Origina and Spinnaker Support maintain products from IBM and other publishers, typically for stable, mature software where the customer is not consuming a stream of new releases. You keep the perpetual license you already own and replace the annual vendor maintenance contract with an independent one, commonly at a materially lower annual cost. The provider handles incidents, root cause analysis, and workarounds using its own engineering.
The trade is straightforward to state and harder to judge. You give up the publisher's new versions and proprietary code fixes in exchange for a lower bill and an independent service. For software you intend to keep stable, that can be a sound exchange. For software under active development that you plan to keep current, it usually is not. Even when you do not switch, a credible third party quote is a renewal lever, which is why this option belongs in every license negotiation.
The trade across the dimensions that decide the call
| Dimension | Vendor maintenance | Third party support |
|---|---|---|
| Annual cost | Full published maintenance | Commonly a large reduction |
| New versions | Included rights to upgrade | Not provided; you stay on the version you hold |
| Code fixes | Vendor proprietary patches | Independent engineering and workarounds |
| Best fit | Software you plan to keep current | Stable, mature products at end of their change curve |
| Renewal value | The status quo | A credible walk away alternative |
| Reinstatement | Not applicable | Returning later can carry back maintenance charges |
The saving is visible. The lever is the point.
Take a portfolio of stable mainframe products carrying an indexed annual vendor maintenance of 1,000 units. An independent provider quotes the same coverage at an indicative 50 percent reduction, a figure consistent with the order of saving these firms publish on enterprise estates. The direct saving is 500 units a year. The larger figure is often the renewal: faced with a credible costed alternative, a publisher renewal that was heading for an uplift can instead settle below the prior rate. Both effects are shown below; the units are an index, not a price.
The units are an index and the percentages are illustrative, but the structure is the one we see. The direct switch saving is the headline; the negotiated renewal, won by holding a credible alternative, is the value that accrues even when you do not move. The discipline is to qualify which products are genuinely stable before either path, because the case collapses on anything you plan to upgrade.
The case is strongest on mature products you will not upgrade and weakest on software under active development. Sort the portfolio before you cost anything; only the stable tier is a real candidate.
Third party support fits the end of the change curve.
Confirm the perpetual right to run your current version without active maintenance. Some agreements tie usage rights to a live support contract, which changes everything. The license terms decide whether the option is even open.
The right to keep running is the whole foundation.
Returning to vendor support later can carry back maintenance and penalty charges. Model the cost of going back before you leave, so the decision accounts for the round trip, not just the one way saving.
Know the cost of coming back before you go.
Even where you choose to stay, a credible costed alternative reshapes the renewal. Build the quote and the migration outline so the option is real, not rhetorical, when you sit down with the publisher.
A walk away you can prove is leverage you can use.
Maintenance for licensed software from an independent firm rather than the publisher. On the mainframe, providers such as Origina and Spinnaker Support cover IBM and other publishers, usually for stable products, at a materially lower annual cost. You keep your perpetual license.
New versions and the publisher's proprietary code fixes. Independent firms resolve issues with their own engineering and workarounds. For software you will not upgrade the trade can be sound; for software you plan to keep current it usually is not.
Yes, often most useful that way. A credible costed alternative is a walk away you can table at renewal. It changes the publisher's assumption that leaving is hard and gives you leverage on the rate even when you ultimately stay on vendor support.
The perpetual right to run your current version without maintenance, audit and reinstatement clauses, the provider's depth on your products, and which products are genuinely stable. The case is strongest on mature software you will not change.
Related: licensing concepts hub · sub-capacity vs full capacity · True Forward explained · publisher hubs · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →