IBM ULA Style Agreements and the Certification Risk

An unlimited style agreement lets you deploy a set of IBM products without counting for the term, which feels like the end of license anxiety. It is not. The risk is simply deferred to the certification at the end, where everything you deployed becomes a number you must prove and then live with. Unlimited has an expiry date, and a reckoning attached to it.

How an unlimited style agreement works

In an enterprise or unlimited style arrangement, the buyer pays a fixed amount for the right to deploy named products freely across a defined term, with no per unit counting during that window. At the end of the term, the buyer certifies the quantity actually deployed, and that certified number becomes the entitlement going forward. The model trades counting discipline now for a true up later. Whatever you certify is what you carry, so the deployment behavior during the term and the accuracy of the count at the end determine the lasting cost.

Where the certification risk lives

The danger is asymmetric. Deploy aggressively during the term and you appear to be extracting value, but every instance you stand up raises the number you must certify and then keep paying to support. Deploy carelessly, with poor records, and you reach the certification unable to prove what is real versus abandoned, and IBM has every reason to certify the higher figure. Worse, products deployed outside the agreement's named scope do not benefit from the unlimited right at all and surface as ordinary unlicensed use. The certification is effectively a self administered audit with IBM checking the arithmetic.

• The term defers, it does not erase: free deployment now becomes a certified, permanent entitlement later
• Scope is strict: only the named products enjoy the unlimited right; anything else is normal exposure
• Records decide the number: at certification you must prove what is deployed, or accept the higher count
• Forward cost follows: the certified quantity sets the support base you pay on for years afterward

How buyers control the reckoning

We treat the certification as the main event from the day the agreement starts, not a formality at the end. That means tracking deployment against the named scope throughout the term, decommissioning what is not truly needed before the count is taken, and building the evidence to certify a defensible, accurate number rather than an inflated one. As the term closes, we run our own reconciliation ahead of IBM so the certified figure reflects real use, and we position the renewal terms inside that conversation rather than after it.