IBM rarely publishes a sticker price, so buyers are left to reverse-engineer the cost from the metric. The metric is the whole game: get the PVU count, the sub-capacity position and the Subscription & Support uplift right and the number is defensible. Get them wrong and IBM charges full capacity. This is the buyer-side breakdown.
The short answer: IBM software is sold through Passport Advantage and priced per Processor Value Unit (PVU) or Virtual Processor Core (VPC). On common x86 chips IBM counts 70 PVUs per core; at a typical list near $200 per PVU that is roughly $14,000 per core for middleware before discount and before sub-capacity reduction. Cloud Pak products price per VPC. Sub-capacity licensing — which can cut the bill substantially — is only available where the IBM License Metric Tool (ILMT) is deployed and reporting.
There is no public price book that turns "I need MQ" into a number, so the only way to forecast IBM cost is to model the metric. In our work across 340+ enterprise engagements, the avoidable IBM spend almost never sits in the per-unit list rate — it sits in over-counted cores, lapsed ILMT that voids sub-capacity, and compounding Subscription & Support. This article walks each layer with the benchmarks we see on real renewals and audits. For the full mechanics, pair it with our IBM licensing guide.
Because the rate is per metric, the headline cost is a multiplication, not a quote. Below are the metric anchors we use to sanity-check an IBM proposal. Treat them as directional — IBM's processor table varies by chip, list rates vary by product, and your actual price depends on volume, contract vehicle and how competitive the cycle was.
| Metric | What it counts | Typical products | Indicative list anchor (pre-discount) |
|---|---|---|---|
| PVU (Processor Value Unit) | Per-core, weighted by IBM's processor table (≈70 PVU/core on x86) | WebSphere, Db2, MQ, traditional middleware | ≈$200 / PVU → ≈$14,000 / x86 core |
| VPC (Virtual Processor Core) | Peak virtual cores made available to the product | Cloud Paks, containerised & OpenShift workloads | Per-VPC; bundled across the Cloud Pak suite |
| RVU (Resource Value Unit) | A managed resource (server, MIPS, terabyte) on a tiered scale | Tivoli, monitoring, storage management | Tiered — unit price falls as volume rises |
| Authorized User | Each named individual with access | Analytics, Cognos, Planning Analytics | Per named user / year |
| S&S (Subscription & Support) | Annual maintenance on net licence value | All Passport Advantage products | ≈20% of net licence price / year |
Work an example. A WebSphere estate of eight x86 cores rated at 70 PVU each is 560 PVUs; at a $200 list that is roughly $112,000 before discount, plus about $22,000 a year in Subscription & Support. Enforce sub-capacity and license only the four virtual cores the product actually runs on, and the same workload drops to 280 PVUs — half the licence and half the recurring S&S. That single decision, sub-capacity versus full-capacity, moves the cost more than any discount IBM will offer on the list rate.
We reconcile deployed PVUs and VPCs against entitlement before the number locks — and defend the sub-capacity position.
A Processor Value Unit is IBM's unit of measure for processor-based licensing. Every core is assigned a PVU rating from IBM's published processor value table — 70 PVUs for most x86 cores, with higher ratings for some Power and mainframe chips — and you multiply the number of cores by the rating to get the PVUs you must own. List prices are then quoted per PVU. Because the rating travels with the silicon, the same software costs more on a higher-rated chip, which is why hardware refresh and IBM licensing have to be planned together. The detail is in our IBM Passport Advantage guide.
PVU is the legacy metric for on-premises middleware. VPC — Virtual Processor Core — is the newer metric IBM uses for containerised software and Cloud Paks, counting the peak virtual cores made available to the product rather than physical cores in the box. Cloud Paks bundle multiple products under one VPC entitlement that can be re-allocated across the suite, which is attractive on paper but makes true-up exposure harder to track. If you are moving to OpenShift or Cloud Paks, model the VPC peak carefully; our Cloud Paks licensing breakdown shows where the bundle helps and where it hides cost.
How comparable enterprises structure Passport Advantage and Enterprise License Agreements — and the clauses that cap S&S uplift.
Sub-capacity licensing — paying for the virtual cores a product uses rather than every physical core in the server — is the single largest lever on IBM cost, and it is conditional. IBM requires the IBM License Metric Tool (ILMT) or an approved equivalent to be deployed, collecting data at least every 30 minutes, with reports generated and retained for two years. Miss that and the entitlement converts to full capacity — every physical core in the cluster, not the few the product touches. In our audit-defence work, broken or never-deployed ILMT is the most common trigger that turns a routine review into a seven-figure claim, because there is no defence once the condition has lapsed. We cover the remediation path in the sub-capacity and ILMT defence guide.
Subscription & Support is the annual fee — historically around 20% of the software's net licence price — that funds version upgrades and support. It is where most of IBM's recurring revenue lives, and it compounds: every uplift is applied to a base that already includes last year's uplift. Over a five-year hold, uncapped S&S can quietly outgrow the original licence spend. The defensive terms are a fixed annual uplift cap (low single digits), the right to drop support on shelved products without re-buying the licence, and protection against re-pricing when you consolidate. We benchmark these in every renewal; the negotiation patterns sit in our IBM ELA negotiation guide.
We size the VPC peak and the S&S trajectory together — the two decisions that set the multi-year cost before signing.
Four moves carry most of the savings. Enforce sub-capacity with healthy, continuous ILMT reporting so you license virtual rather than physical cores. Reconcile deployed PVUs and VPCs against entitlement before any renewal, retiring the licences attached to decommissioned workloads. Consolidate into a Cloud Pak or Enterprise License Agreement only where the bundle is genuinely cheaper than the parts — not because it is offered. And cap the annual S&S uplift contractually. Buyers who do all four typically reduce the IBM run-rate materially versus the proposed renewal. The same discipline applies across the portfolio; if you are also weighing cloud spend, the Oracle Cloud cost breakdown applies the identical metric-first method to OCI, and our IBM practice page sets out how we run a full engagement. When IBM opens an audit, route it through vendor audit defence before responding — and the proof of what disciplined IBM negotiation returns sits in our case studies.
Our IBM practice negotiates for buyers — never IBM. We have documented $1.8B+ in client savings across 340+ engagements, with a 95% client retention rate.
One email a week, no filler — the vendor moves that quietly add 9–18% to a renewal, and how clients take it back out.