Your outsourcer runs the frame. But who controls the license?

When a provider operates your mainframe, the day to day stops being your problem. The licensing rarely follows the same path. A typical agreement leaves the underlying software licenses with the customer even though the customer no longer touches the machine, which means the customer still carries the audit exposure and still pays the renewal, but has lost the operational visibility needed to manage either. The provider runs the estate, sees the consumption, and controls the data, while the customer holds the contract risk and the invoice. That split is where the trouble starts.

Most publisher agreements restrict transfer, sublicensing, and third party access, so moving licenses into an outsourcing arrangement commonly requires the publisher's consent. That consent moment is a negotiation in itself, and it is one buyers routinely give away by treating the outsourcing deal and the licensing question as separate workstreams handled by different teams who never compare notes. The control question, who holds the paper and who carries the risk, should be answered deliberately, not inherited by accident.

Almost every mainframe outsourcing arrangement maps to one of three license models. They are not equally good for the buyer, and the right one depends on what you are trying to protect:

The model is not just an administrative choice. It decides who can negotiate the next renewal, who absorbs an audit finding, and who captures any optimization savings. A provider license that bundles cost into the fee can feel simpler while quietly removing your ability to see, challenge, or reduce the underlying spend.

The goal is not to pick one model as universally right, it is to choose deliberately and to keep the levers that matter. If you hold the license, insist on the consumption data the provider sees, because you cannot manage a baseline you cannot measure. If the provider holds it, demand cost transparency and audit indemnity in writing, and protect your ability to exit without a punitive license reset. In every model, treat the publisher's consent to the arrangement as a negotiation, not a formality, and make sure the outsourcing contract and the license contract are read together by someone who understands both. This is where buyers most often lose ground: the two deals are negotiated by different people and the gap between them becomes the provider's or the publisher's advantage. Our mainframe license negotiation work sits across both, and the structural detail is covered in the guide on mainframe software in outsourcing deals. For the regulated angle, where third party governance is now mandatory, see mainframe licensing in banking.