IBM licensing guide for 2026. The four metrics and the ILMT evidence behind your bill.

IBM licensing in 2026 turns on four metrics, the sub capacity rules that cap them, and the License Metric Tool reports that prove your counts. Settle those before you negotiate, and most of the cost is already decided.

IBM licensing looks complex because the metrics behave so differently from one another. In practice the bill turns on three decisions: which metric applies to each product, whether sub capacity counting is in force, and whether the License Metric Tool proves your numbers.

When those three are settled, IBM is manageable. When they are not, an audit settles on the worst case, which for most customers means every physical core in every host. Below we cover each metric, the evidence IBM expects, and the preparation that pays before a renewal or an Enterprise License Agreement.

What are the core IBM licensing metrics in 2026?

Most IBM software sold through Passport Advantage, IBM's volume licensing program, maps to one of four metrics. The metric decides what you count, so it has to be settled product by product before any price conversation starts.

The four metrics you will meet most

• PVU. Processor value units, scaled by the type of core. Used for middleware such as WebSphere and MQ.
• RVU. Resource value units, scaled by a resource the product manages, such as devices, terabytes or managed servers.
• VPC. Virtual processor cores, the metric used across the Cloud Paks and most newer containerized offerings.
• Authorized or concurrent user. Per person metrics for user facing tools, counted either as named people or as the peak number connected at once.

The IBM Passport Advantage program publishes the agreements and metric definitions that govern each product. The License Information document for each part number is the final word, and it sometimes differs from what the sales quote implies.

How are PVUs calculated for a server?

You multiply the cores available to the program by the PVU rating IBM assigns to that processor. The ratings in IBM's current table that most customers meet are these.

• Intel Xeon. 70 PVUs per core on servers with up to 2 sockets, 100 on 4 socket servers and 120 above 4 sockets.
• AMD EPYC. 70 per core in every configuration.
• IBM Power10 and Power11. 120 per core on the E1080 and E1180, 100 on the E1050 and E1150, and 70 on the S and L series.
• Anything not listed. A processor missing from the table defaults to 100.

IBM's own example is a 2 socket server with 6 cores per socket, which needs 840 PVUs. Check the current rating in our IBM PVU table before you rely on an old spreadsheet.

Where RVU and user metrics catch customers out

RVU counts grow with the managed resource, so they drift upward as you add devices or data without buying new software. IBM converts resource counts through tiered tables, which our RVU licensing guide walks through. User metrics fail more simply. Accounts for leavers and service users stay active in the directory and get counted as licensed people.

How do sub capacity rules and ILMT change the bill?

Sub capacity counting is what makes PVU licensing affordable in a virtualized data center, and ILMT is the condition attached to it. Under full capacity, you license every activated physical core in the server the software could run on, whatever the virtual machine is actually given.

Sub capacity licensing counts only the virtual cores allocated to the workload. The catch is evidence. IBM grants sub capacity only where the License Metric Tool, or another tool IBM has approved, is deployed and producing reports. The License Metric Tool documentation sets out the deployment and reporting duties.

Why ILMT gaps are expensive

If ILMT is missing on a server, IBM can default that server to full capacity. A small coverage gap can swing a finding by hundreds of cores. We treat ILMT hygiene as the single most valuable control an IBM customer has, ahead of any pricing tactic.

The gaps we find are usually administrative. A new VMware cluster was never connected to ILMT, the VM manager connection stopped after a service account password changed, or software was discovered but never bundled to the right product, so reports show it as unassigned.

A worked example of full capacity versus sub capacity

Say you run WebSphere Application Server on 4 virtual machines with 4 virtual cores each, inside a VMware cluster of 4 hosts. Each host has 2 Intel Xeon sockets with 16 cores per socket, rated at 70 PVUs per core. The virtual machines can move to any host, so without sub capacity every core in the cluster counts.

The deployment is identical in both columns, and the evidence is the only difference. Multiply the 7,840 PVU gap by your contracted PVU price, then add backdated Subscription and Support, and you have the order of magnitude an audit finding can reach from one unmonitored cluster.

How does VPC licensing work for IBM Cloud Paks?

Cloud Paks license on virtual processor cores. Each Cloud Pak bundles a set of entitled programs, and a ratio converts each underlying program into Cloud Pak VPCs, so one pool of entitlement can be spent on different products.

The benefit is flexibility across the bundled products. The risk is assuming the bundle is cheaper by default. IBM publishes the Cloud Pak entitlements, and you should check whether you will use the bundle breadth before paying for it. Our Cloud Pak VPC overview covers each Pak in turn.

VPC counting in practice

• Count the virtual cores assigned to the workloads running Cloud Pak programs.
• Apply the published ratio for each entitled program.
• Keep ILMT, or IBM License Service on OpenShift, active as the evidence trail.

How the ratios change the cost of each program

Cloud Pak for Integration shows how wide the ratios run. In production, 1 Cloud Pak VPC covers 2 VPCs of MQ Advanced or 4 of base MQ, while 1 VPC of App Connect Enterprise consumes 3 Cloud Pak VPCs. Non production deployments get double the coverage, so the same entitlement stretches twice as far in test.

Say a team plans the following deployment. The Cloud Pak VPCs needed come straight from the ratios above.

• MQ Advanced, production. 16 VPCs at 2 to 1 need 8 Cloud Pak VPCs.
• App Connect Enterprise, production. 8 VPCs at 1 to 3 need 24 Cloud Pak VPCs.
• MQ Advanced, non production. 16 VPCs at 4 to 1 need 4 Cloud Pak VPCs.

The total is 36 Cloud Pak VPCs, and two thirds of the purchase goes to App Connect, so that is the workload to size carefully. Moving from PVU to VPC is covered in our PVU to VPC transition guide.

What have we seen in recent IBM renewals and audits?

The recurring exposure is metric and tooling hygiene rather than price. We reviewed roughly 25 to 35 IBM Passport Advantage customers between 2024 and 2025, and the same patterns came up across industries and sizes.

• ILMT coverage. In about half of them, ILMT was either not deployed or not reporting on every server, which exposed the customer to full capacity counts.
• PVU findings. PVU was the dominant metric, and sub capacity gaps produced findings 20 to 60 percent above the deployed footprint.
• Shelfware. Middleware that was owned but not in production made up 10 to 30 percent of the IBM bill.

The discount rate is rarely the biggest number in an IBM contract. The capacity you license and never use usually is.

What works at an IBM renewal or ELA?

Enter with a clean deployment baseline built from your own ILMT data, and cut what you do not use before you talk about discount. An IBM Enterprise License Agreement trades discount for commitment. It can be the right structure, but it locks scope for the term.

IBM also offers enterprise agreement structures that pool entitlements. Read the true up terms carefully, since a flexible looking ELA can carry a costly annual reconciliation. Our IBM ELA renewal white paper sets out the terms and timing in detail.

How do you find and drop IBM shelfware?

Many IBM customers carry middleware that has not run in production for years. Cutting it before renewal lowers the base the discount applies to, because a discount on shelfware is still spend on shelfware.

Compare every S&S line in Passport Advantage Online with what ILMT discovers. These are the lines to question first:

• parts with no installs anywhere in ILMT
• parts installed only on servers that are retired or scheduled for decommission
• entitlement well above the peak ILMT has recorded over the last year

For perpetual licenses, ending S&S keeps your right to use the software. You lose fixes, new versions and support, and restoring S&S later needs a reactivation quote from IBM. Confirm with the application owner before you drop a line.

Why a bigger discount is the wrong place to start

The standard advice is to chase a bigger discount and fold everything into an ELA. We disagree. In roughly 6 of 10 IBM customers we reviewed, the larger number was the shelfware and the full capacity exposure from ILMT gaps. An ELA negotiated on a bloated baseline locks in a discounted version of overspend.

Fix ILMT coverage, remove undeployed middleware and rebaseline before any discount conversation. A modest discount on a clean footprint beats a deeper discount on a number you should never have been paying.

What the IBM account team will say, and what to say back

• "An ELA gives you room to grow." Ask for the growth forecast behind the sizing and a cap on the annual true up. Headroom you never use is paid for up front, like any other shelfware.
• "Your ILMT data is incomplete, so we have to use full capacity." Ask which servers are affected and in which reporting periods. Fix the gaps, offer current reports, and push back on a blanket calculation across periods that were covered.
• "Moving to Cloud Paks will simplify your licensing." Ask for the VPC count per program and the ratios used. Compare it against what you deploy today before you agree to trade in PVU entitlements.
• "This pricing expires at quarter end." Ask for the quote validity date in writing and whether the same unit prices would hold next quarter. Our note on IBM deal timing explains when waiting pays.

Contract terms to ask for

1. A cap on Subscription and Support uplift. S&S renews for 12 months at IBM's prevailing price, so write the maximum increase into the contract. See our uplift cap clause language.
2. Price holds on multi year quotes. Fix unit prices for additional quantities during the term through a price hold clause.
3. Audit notice and scope limits. Agree the notice period, the lookback and how ILMT gaps are remedied. Our audit clause redlines give the wording.
4. Reduction rights. Keep the right to drop products you retire without losing discount on the rest, as covered in termination and reduction rights.
5. Swap rights inside Cloud Paks. Secure the right to move entitlement between programs as needs change, using a substitution clause.

How do you check your own IBM position before a renewal or audit?

Start from two sources IBM also relies on: your entitlement records in Passport Advantage Online and your ILMT reports. Reconcile them product by product, then fix what does not match before IBM sees it.

• Passport Advantage Online. Export the entitlement and S&S history for every site number, including old ones from acquisitions.
• ILMT or BigFix Inventory. Generate the audit snapshot for the last two years and confirm every period is complete, reviewed and bundled to the right product.
• VM manager connections. Check that every VM manager ILMT relies on, such as VMware vCenter and Microsoft Hyper-V, shows an active connection. A dropped connection is the most common cause of a full capacity default we see.
• IBM License Service. On OpenShift, confirm it runs on every cluster hosting Cloud Pak workloads.

Our ILMT sub capacity guide and IBM audit defense checklist go through these checks in more depth.

A renewal timeline that leaves room to act

Common mistakes that cost IBM customers money

• Treating ILMT as installed and finished. The tool needs regular updates, scans and bundling. An unmaintained ILMT can be as costly as none.
• Letting one product number cover several products. Bundling distinct products under one part number rarely helps. It hides which products are used and makes shelfware hard to drop.
• Counting non production at production rates. Where the license terms allow cheaper non production entitlement, test systems should use it.

What to do next

1. Map every product. Inventory every IBM product and map it to its actual licensing metric.
2. Confirm ILMT coverage. Check that the License Metric Tool is deployed and reporting on every in scope server, and IBM License Service on every cluster.
3. Size the exposure. Quantify full capacity exposure on any server ILMT does not cover.
4. Build the shelfware list. Identify middleware owned but not deployed and agree what to remove.
5. Rebaseline. Bring your numbers to deployed reality before opening any renewal or ELA talk.
6. Negotiate the clean footprint. Negotiate discount on it, and red line any true up terms you cannot forecast.

Frequently asked questions