Why Cloud Pak strategy matters.
The IBM Cloud Pak portfolio is IBM's container native consolidation of the legacy middleware, data, integration, automation, and security portfolios. The Cloud Pak frame changes the licensing basis from PVU (per processor core, weighted by the PVU table) to VPC (per virtual processor core, uniform across platforms) and bundles the underlying Red Hat OpenShift entitlement at a defined ratio.
The strategic frame is the buyer side decision on how to structure the Cloud Pak entitlement: which products to migrate into the Cloud Pak frame, how to size the VPC commitment, where the bundled OpenShift entitlement should land, and how to structure the multi year commitment. The Cloud Pak expertise page documents the operational engagement frame.
1. The Cloud Pak portfolio.
The Cloud Pak portfolio is structured into five major Cloud Paks plus several adjacent product families. Each Cloud Pak bundles a related product set under a single VPC entitlement.
- Cloud Pak for Applications: WebSphere Liberty, WebSphere ND, Mobile Foundation, Application Runtime Modernisation tools.
- Cloud Pak for Data: Db2, watsonx.data, DataStage, Cognos Analytics, Watson Studio, Data Refinery.
- Cloud Pak for Integration: App Connect, API Connect, MQ, DataPower, Event Streams, Aspera.
- Cloud Pak for Business Automation: Business Automation Workflow, FileNet, Operational Decision Manager, RPA.
- Cloud Pak for Security: QRadar, Guardium, Trusteer adjacent capabilities.
The watsonx product family sits adjacent to Cloud Pak for Data on the on premises deployment and standalone on the IBM Cloud SaaS deployment. The watsonx expertise page documents the adjacency.
2. The VPC entitlement basis.
The Cloud Pak entitlement basis is the Virtual Processor Core (VPC). The VPC is the per core entitlement counted against the licensed Cloud Pak count. The VPC simplifies the prior PVU model by removing the per processor type weighting and consolidating on a per core unit.
The VPC count is the deployed core count for the workload running the Cloud Pak components. The measurement is the IBM Licence Service running on the OpenShift cluster carrying the Cloud Pak workload. The VPC measurement is independent of the underlying platform PVU weighting that would apply under the standalone middleware programme.
3. The OpenShift bundling boundary.
Each Cloud Pak entitlement includes a bundled Red Hat OpenShift entitlement at a defined ratio. The bundled OpenShift entitlement is restricted to the Cloud Pak workload. Standalone OpenShift workloads outside the Cloud Pak scope require independent Red Hat entitlement.
The bundling boundary is the most common Red Hat licensing question in the engagements we run. The clean architectural pattern is to run the Cloud Pak workloads on one set of OpenShift clusters (covered by the bundled entitlement) and the standalone OpenShift workloads on a separate set of clusters (covered by independent Red Hat entitlement). The mixed cluster pattern complicates the entitlement reconciliation and is a frequent audit finding surface. The Red Hat expertise page documents the bundling overlay.
4. Conversion ratios.
The Cloud Pak entitlement converts to the constituent product entitlements at a defined ratio. The ratio determines how many product entitlements are obtained per VPC. The ratios are product specific and Cloud Pak specific and are published in the Cloud Pak Licence Information document.
| Cloud Pak | Anchor product | Indicative conversion direction |
|---|---|---|
| Cloud Pak for Applications | WebSphere ND | Favourable for workloads with WebSphere ND, Liberty |
| Cloud Pak for Data | Db2 AESE | Favourable for workloads with Db2 plus Cognos plus DataStage |
| Cloud Pak for Integration | MQ Advanced | Favourable for workloads with MQ plus App Connect plus API Connect |
| Cloud Pak for Business Automation | BAW | Favourable for workloads with the integrated automation stack |
| Cloud Pak for Security | QRadar | Favourable for the integrated security operations stack |
The conversion economics favour the workload mix that consumes multiple products inside the same Cloud Pak. A workload that consumes only one product on the Cloud Pak menu typically licenses more cleanly under the standalone product entitlement. The disciplined strategy maps the deployed workload mix against the Cloud Pak ratio before the commitment.
5. The IBM Licence Service.
The IBM Licence Service is the container native measurement endpoint for the Cloud Pak entitlement. The Licence Service runs on the OpenShift cluster carrying the Cloud Pak workload and measures the VPC consumption per Cloud Pak.
The Licence Service is the Cloud Pak equivalent of ILMT. The Service must be deployed on every cluster carrying Cloud Pak workloads and must report cleanly to the IBM measurement endpoint. The most common Cloud Pak measurement gap is the Licence Service not deployed on every cluster or deployed but not reporting cleanly. The remediation is the parallel discipline to the ILMT discipline. The dedicated reference is ILMT best practices which covers both the ILMT and the Licence Service.
6. The renewal commitment structure.
The Cloud Pak renewal commitment structures the multi year horizon. The committed VPC base is the floor over the term. The headroom is the growth capacity. The carve outs are the workloads routed outside the Cloud Pak frame. The discipline is to commit to the operationally confident base, with headroom for growth, and to keep the speculative capacity outside the commitment.
The Cloud Pak renewal commitment is frequently structured inside a broader ELA frame. The ELA frame captures the larger discount tier in exchange for the multi year revenue visibility. The dedicated reference is ELA versus PA and the Cloud Pak licensing guide white paper.
Frequently asked questions.
Can I migrate to Cloud Pak in stages?
Yes. The phased migration is the more common Fortune 500 pattern. The disciplined phasing migrates the workload subset that captures the conversion ratio favourably first, retains the rest of the workload under the standalone entitlement, and revisits the migration at the next renewal gate.
How does the bundled OpenShift entitlement interact with standalone Red Hat?
The bundled OpenShift is restricted to the Cloud Pak workload. Standalone Red Hat workloads outside the Cloud Pak scope require independent Red Hat entitlement. The clean architectural pattern separates the two cluster sets to avoid the entitlement mixing.
What is the Cloud Pak conversion economics?
The conversion captures benefit when the underlying workload mix consumes multiple bundled products. A workload consuming only one product on the Cloud Pak menu typically licenses more cleanly under the standalone product entitlement. The disciplined strategy maps the workload mix before the commitment.
Does Cloud Pak require sub capacity?
The Cloud Pak licensing basis is the VPC measurement through the Licence Service. The traditional ILMT sub capacity does not apply to the Cloud Pak workload. The non Cloud Pak portfolio continues to use ILMT.
Related pillars across the blog.
IBM Product Licensing Reference Guide.
Product specific licensing for WebSphere, MQ, Db2, Cognos, DataStage, Tivoli, Maximo, Cloud Paks, watsonx, and the Red Hat portfolio. The product reference pillar.
Read the pillarThe Complete IBM Licensing Guide.
The foundational pillar covering programmes, metrics, sub capacity, ILMT, Cloud Paks, Red Hat, mainframe, pricing, audit, and renewal.
Read the licensing pillarWhere to go next.
For the dedicated white paper, continue to the Cloud Pak licensing guide. For the Cloud Pak ROI analysis, continue to the Cloud Pak ROI analysis white paper. For the OpenShift deep dive, continue to the OpenShift licensing deep dive. For the Red Hat post acquisition position, continue to the Red Hat expertise page. For a scoped Cloud Pak strategy engagement, the license consulting service page is the entry point.
Cloud Pak strategy conversation?
An independent senior advisor scopes the Cloud Pak strategy and commitment engagement within a week. No IBM relationship, no resell margin, no commercial conflict.