① Publisher guide · Syncsort (Precisely)
Syncsort MFX is among the most widely installed third party products on IBM mainframes, and it is licensed on capacity, which means your hardware decisions move the bill. Here is how the Precisely portfolio is priced, how renewals typically behave, and where buyers hold leverage.
Syncsort built its franchise on one product: high performance sort for z/OS. The company merged with Vision Solutions and rebranded as Precisely in 2020, and has been owned by Clearlake Capital and TA Associates since their $3.5 billion acquisition in 2021. The mainframe line continues under the Syncsort product name inside Precisely's broader data integrity portfolio.
If you run a mainframe, you probably run Syncsort MFX as your sort engine, often with the ZPSaver feature offloading sort, copy, and SMS compression workload to zIIP engines. The Ironstream family streams z/OS and IBM i logs and metrics into platforms like Splunk and ServiceNow. PROCSort serves environments standardizing sort calls across platforms.
What this means for spend
Syncsort (Precisely) mainframe products are typically licensed against machine capacity, with pricing tiered to the MIPS or MSU rating of the CPCs where the software runs. Agreements commonly combine a license fee with annual maintenance, or run as term licenses. Crucially, Precisely controls usage through license keys tied to machine serial numbers and capacity: keys are not self service and must be requested through the support portal.
That key mechanism is the quiet enforcement layer. A hardware upgrade or DR change requires new keys, which means Precisely typically learns about your capacity increases the moment they happen, and repricing conversations commonly follow.
The metrics that matter
Under private equity ownership, Precisely renewals commonly arrive with uplift, and capacity growth since the last term is typically the stated justification. Because the key process gives the vendor visibility into hardware changes, capacity reconciliation tends to be accurate from their side; the buyer question is whether the contract terms around that capacity were ever negotiated.
Formal audits are less frequent than with the largest publishers, in the patterns we observe, because key control reduces the need for them. The exposure that does surface typically involves keys running on machines outside contracted scope, DR configurations, or divested entities still running licensed code. For the response sequence, see Precisely Audit and Compliance Response.
The sort market has a structural feature most mainframe categories lack: IBM ships a competing product, DFSORT, with z/OS. Migration is real work, JCL and exit dependencies make it nontrivial, but it is a credible, well trodden path in both directions, and Precisely prices against that reality when buyers demonstrate it seriously.
Where we find leverage
Audit notice or renewal under 18 months out? We mobilize within 48 hours. Related reading: MIPS explained and zIIP engines and software cost offload.