The IBM unlimited license agreement explained. A bet on deployment growth, not audit insurance.

An IBM IULA pays off only when your deployment of the named products grows during the term. Without a growth plan and a written cap on support uplift, the recurring support bill outruns the discount that sold it.

How does an IBM unlimited license agreement work?

An IBM unlimited license agreement (IULA) allows you to deploy a named list of IBM products without limit for a fixed term, usually three years. At the end of the term you certify what you deployed, and that certified count becomes your perpetual entitlement.

From then on you pay annual support on that base, under the IBM Passport Advantage terms. The certification is a point in time count, so the shape of your deployment curve during the term decides what the agreement was worth.

What does the certification fix for good?

Three things are settled on certification day, and none of them can be reopened once the count is signed:

• Deployed quantity. The measured install base of each named product at term end.
• Named products only. Parts outside the list are not covered, however widely they are deployed.
• Metric basis. The count uses each product's own metric, often processor value units (PVUs). Our PVU table guide shows how IBM rates each processor type.

How is it different from an IBM ELA?

An enterprise license agreement buys fixed quantities with support bundled in, and growth beyond them is trued up. An IULA removes the quantity cap during the term and settles the quantity at the end.

• Other IBM vehicles. Our enterprise agreement guide and Passport Advantage guide cover where each one fits.
• Oracle comparison. If you also hold Oracle, the Oracle ULA comparison follows the same certification logic.
• Video briefing. Negotiating IBM: Five Things (6:48) covers the five positions that decide an IBM agreement: the ELA scope, the sub capacity evidence, the ULA certification path, metric drift, and the renewal that reprices all of it.

Which terms decide whether an IULA pays off?

Four terms decide the value: the certification base, the cap on support uplift, the named product scope and the upfront discount. The discount headline is the weakest of the four, yet it is where most buyers spend their negotiating time. The other three are written into the agreement and keep working long after the term fee is paid.

Why does the discount matter least?

The discount is applied once, to the term fee. The certified base sets how much software you own for the rest of its life, and the support cap sets what that software costs every year after. A few extra points of discount rarely survive three or four years of uncapped uplift, as the worked example below shows.

Scope sits alongside the base and the cap. Write the named product list from what you run and plan to run, because a product left off the list gets no unlimited rights at all.

Why we do not recommend an IULA as audit insurance

IBM, and many advisors, present unlimited deployment as a way to remove audit risk and sign for peace of mind. We disagree with that reason for signing. The relief covers only the named parts, while the cost is a support bill that compounds for years after the term.

If audit exposure is the worry, an ILMT cleanup and a fixed quantity purchase usually cost less. Sign an IULA only with a growth plan that lifts the certified count well above today's.

What have we seen in recent IBM unlimited agreements?

Across roughly 15 to 25 IBM agreements that Fredrik Filipsson and I reviewed between 2024 and 2025, the unlimited agreement paid off only where the customer had a real deployment growth case. The same three patterns came up again and again:

• No plan, little gain. Customers who certified without a deployment plan locked in a base barely above their pre agreement count, so the term fee bought very little.
• Support outran the discount. Support uplift compounded at 3 to 8 percent a year on the certified base and often outran the upfront discount that justified the agreement.
• Scope gaps at the next audit. Products outside the named list created surprise exposure in 1 of 3 of the environments we reviewed, because only the listed parts are unlimited.

On the positive side, a disciplined deploy and certify plan was worth 15 to 30 percent against a renewal that assumes flat deployment, where the certification was timed to the real deployment peak.

It is sold as insurance against an audit, but it behaves as a bet on deployment, and a flat deployment loses that bet over the support tail.

Why does the support line dominate the total cost?

The term fee is paid once, while support recurs every year on the certified base under the IBM support agreements. Each year's uplift is applied to a bill that already includes last year's, so the increases compound for as long as you keep the software.

A base set at the deployment peak is an asset when the uplift is capped and a liability when it is not. The cap decides which of the two you signed, and it has to be drafted before you commit. Our note on uplift cap clause language gives sample wording.

Worked example: five years of support after certification

Say your certified base carries $400,000 of support in the first year after the term ends. The table compares a flat bill, a 3 percent cap and an uncapped 8 percent uplift over five years.

Now set that against the discount. A 12 percent discount on a $2,000,000 term fee saves $240,000 once. Holding the uplift to 3 percent instead of 8 percent saves $222,986 over the same five years, close to the whole discount. By year 5 the gap is $93,992 a year, and it keeps widening.

Three extra points of discount on that fee are worth $60,000. The cap has saved $62,200 by the end of year 3, and $346,641 separates the uncapped bill from a flat one over five years.

Is support priced per certified unit or as a fixed fee?

IBM publishes no standard IULA contract, so ask before you sign. If support is charged per certified unit at the then current rate, every extra PVU you certify raises the bill. If the agreement fixes the annual support amount, a higher count costs nothing more. The answer tells you how hard to push the count.

When should the certification happen?

Certify at the real deployment peak, after every planned rollout has landed. The count you certify is permanent, so an early snapshot leaves entitlement on the table for good.

Build a deployment calendar at signature and set the certification date at the end of the largest rollout. The contract anniversary rarely falls on the same day.

What if deployment is still rising at term end?

Negotiate the certification window so it captures the peak. A short extension to certify after a major rollout can be worth more in entitlement than the rollout itself cost.

Say you ran 20,000 PVUs of the named products before signing, and a data platform rollout will take you to 32,000 PVUs three months after the term ends. Certify on the anniversary with the rollout two thirds done and you lock in 28,000. A three month extension puts the other 4,000 PVUs into your perpetual entitlement.

How do you prove the count?

The count rests on sub capacity evidence, and IBM will test it. Prepare these before the certification date:

• ILMT audit snapshots. The IBM License Metric Tool reports the peak PVU and RVU consumption over each reporting period, which is the figure you want certified.
• ILMT coverage. IBM requires sub capacity customers to implement ILMT within 90 days of their first eligible deployment. A host ILMT does not scan has no accepted evidence behind it, so expect IBM to leave it out of the certified count.
• Part number mapping. Match every deployed component to a named part in the agreement, so nothing counts toward a product you did not buy.
• A signed baseline. Keep the pre agreement count IBM accepted at signature, so the growth you certify is measured against an agreed start.

Our sub capacity guide covers the evidence the count rests on and the scanner gaps that most often break it.

A timeline for the term

What will the IBM account team say, and how should you answer?

Expect the account team to sell audit relief and a deadline, and to leave support pricing vague. These are the lines we hear most often in unlimited agreement talks, with the replies we give.

"Unlimited means you never have to worry about an audit again."

Reply that the agreement covers only the named parts, and ask IBM to confirm the list against your current inventory in writing. Anything you run outside that list stays exposed, and the verification clause in Passport Advantage still applies to it.

"The discount is only available if you sign this quarter."

Reply that you will discuss the discount once the support cap, the certification window and the scope list are drafted. Quarter end pressure works on the headline number, which is the term that matters least. Our note on IBM deal timing covers which quarter deadlines are worth taking seriously.

"Support will follow standard renewal pricing."

Ask for a named ceiling on the annual uplift for a set number of years after certification. The standard Passport Advantage terms allow IBM to set then current support charges at each renewal, which is no cap at all.

What should the agreement say before you sign?

Every term that decides value belongs in the agreement rather than in a call, because only the agreement survives the term. Ask for these:

1. A support uplift ceiling. A fixed maximum annual increase on the certified base for at least five years after certification, since that is where the cost compounds.
2. A certification window. A date tied to your rollout plan, with the right to extend by a set period if a named rollout slips.
3. A certification method. The report, the metric and the peak value rule that will be used, agreed now so the count is not argued later.
4. A precise named part list. Every product and part number you need, plus a rule that renamed or successor products stay in scope.
5. Merger and divestiture rights. What happens to unlimited rights if you acquire or sell a business during the term. Our assignment and divestiture clause note covers the wording.
6. Audit limits. Notice, scope and frequency limits for the products outside the agreement, set out in our audit clause redlines.

The 2026 renewal paper sets out the support sequence that follows certification and how to open the first renewal.

What to do next

1. Test the growth case. Model deployment of each named product over the term. A flat line certifies barely above today's count, and the term fee buys little.
2. Cap the support uplift before you commit. Put the ceiling in the agreement and check it against the full five year tail.
3. Match the named part list to real need. Treat anything outside it as exposure, and reconcile it against your inventory before signing.
4. Build the deployment calendar at signature. Tie the certification date to the end of the largest rollout.
5. Secure the certification window. Agree the extension right and the report format so the count captures the peak.
6. Get the evidence ready. Run ILMT across every host that will carry a named product, starting now.
7. Get a second view. Our IBM practice models the deploy and certify curve before signature and drafts the cap and window terms with you.

Frequently asked questions