IBM Practice
IBM Cloud Pak. The Licensing Guide.
Cloud Pak is the container packaging for IBM software, licensed on one flexible core metric. Read the families, the metric, and the sub capacity rules.
Cloud Pak is the container packaging for IBM software, licensed on one flexible core metric. Read the families, the metric, and the sub capacity rules.
IBM Cloud Pak licenses a whole family of capabilities on one Virtual Processor Core metric, and understanding the metric is the difference between flexibility and shelfware.
Cloud Pak is IBM's containerized packaging for its software portfolio, built to run on Red Hat OpenShift. It is licensed on Virtual Processor Cores, a single flexible metric across the whole bundle.
You buy a pool of entitled cores and run any capability in that Cloud Pak up to the entitled count. That flexibility is the product, and it is what IBM charges for.
IBM documents the packaging on the IBM Cloud Paks product page, and the core counting rules sit in the Passport Advantage sub capacity terms.
A VPC counts a core made available to the Cloud Pak software. Container limits, virtualization, and node placement all change the count, so deployment design directly affects what you license.
Because the metric is uniform, you can shift cores between capabilities as needs change without buying new licenses. That portability is genuine value when you use the breadth, and dead weight when you do not.
IBM packages its software into several Cloud Paks, each grouping related capabilities. Knowing which family you hold and which capabilities you run is the foundation of a defensible position.
The families overlap at the edges, so confirm exactly which capabilities your entitlement covers and which you have actually deployed.
Cloud Pak for Data bundles data management, governance, and analytics. Cloud Pak for Integration bundles API management, messaging, and application connectivity.
Cloud Pak for Business Automation covers workflow and content. Watson AIOps covers IT operations intelligence. Cloud Pak for Security covers threat management and data security across tools.
IBM Cloud Pak families and focus
| Cloud Pak | Capability focus | Common metric | Watch for |
|---|---|---|---|
| Data | Data, governance, analytics | VPC | Unused analytics modules |
| Integration | APIs, messaging, connectivity | VPC | Idle integration runtimes |
| Business Automation | Workflow, content | VPC | Surplus automation cores |
| Security | Threat and data security | VPC | Overlap with point tools |
Sub capacity lets you license only the cores assigned to the Cloud Pak rather than every core in the cluster. Without it, IBM measures full physical capacity, which can multiply the count.
The requirement is the IBM License Metric Tool, installed and producing compliant quarterly reports. No current reports means full capacity at audit.
Converting legacy Processor Value Unit licenses into Cloud Pak VPC uses a published ratio that is rarely one to one. Confirm the exact figure and support continuity in writing before agreeing.
The standard IBM seller pitch is that the Cloud Pak bundle is a strategic platform, so entitling generously now secures cheap future capability and avoids piecemeal buying later. We disagree. In roughly two thirds of the Cloud Pak estates we benchmarked in 2024 and 2025, the future capabilities never deployed and the surplus cores expired as shelfware while support was paid on all of it. The buyer side move is to entitle to deployed capabilities at your evidenced core count, secure written expansion pricing for capabilities you might genuinely add, and decline to prepay for a platform vision the roadmap has not funded.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
On a Cloud Pak you are buying a key to every room, then paying rent on the rooms you never enter.
The renewal turns on evidence of deployment and clean metering. Bring a capability map, current ILMT reports, and the conversion ratio in writing. IBM negotiates against documentation.
Cloud Pak for Security and Integration often overlap with point tools you already own. Identify the duplication and either consolidate onto the Cloud Pak or drop the redundant entitlement.
IBM Cloud Pak is licensed on Virtual Processor Cores across a family of bundled capabilities that run on Red Hat OpenShift. You buy a pool of entitled cores and run any capability in the Cloud Pak up to that count, which is the flexibility IBM charges for.
The main families are Cloud Pak for Data, for Integration, for Business Automation, Watson AIOps, and Cloud Pak for Security. Each groups related capabilities under one VPC entitlement, and they overlap at the edges, so confirm exactly which capabilities your entitlement covers.
A Virtual Processor Core counts a core made available to the Cloud Pak software. Container resource limits, virtualization, and node placement all affect the count, so how you deploy directly changes the number of cores you must license.
Yes, to license on a sub capacity basis. The IBM License Metric Tool must be installed and producing compliant quarterly reports, otherwise IBM measures full physical capacity at audit, which can multiply your core count and your bill.
It is the published rate at which legacy Processor Value Unit licenses convert into Cloud Pak Virtual Processor Cores. The ratio is rarely one to one, so confirm the exact figure, support continuity, and capability parity in writing before agreeing to convert.
In our 2024 to 2025 reviews, 20 to 40 percent of entitled cores supported capabilities the estate never deployed. The overhang usually came from generous entitlement bought for a platform vision that the roadmap never funded.
Usually not. Future capabilities frequently never deploy, leaving surplus cores as shelfware while you pay support on all of it. Entitle to deployed capabilities at your evidenced core count and secure written expansion pricing for anything you might genuinely add.
Co terminating Cloud Pak with the wider IBM agreement usually delivers the most volume leverage, alongside cutting the entitlement overhang. Bring a capability deployment map and current ILMT reports so every cut is defensible.
The VPC metric, each Cloud Pak family, sub capacity with the License Metric Tool, the conversion ratios, and the renewal levers that cut an over entitled estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
