IBM Cloud Paks represent IBM's containerised software portfolio — a bundling of IBM middleware, AI tools, and Red Hat OpenShift Container Platform under a single VPC (Virtual Processor Core) pricing model. Understanding how Cloud Pak licensing actually works — including what's included, how VPCs are counted, and where the cost traps hide — is essential before any renewal or initial purchase negotiation.
IBM Cloud Paks are containerised software bundles that package IBM middleware, AI tools, and data management capabilities together with Red Hat OpenShift Container Platform (OCP). Launched in 2019 following the Red Hat acquisition, Cloud Paks represent IBM's strategic pivot from traditional on-premises perpetual licensing toward subscription-based, container-native software delivery.
The Cloud Pak model has several notable characteristics that differentiate it from traditional IBM licensing. First, Cloud Paks include Red Hat OpenShift as part of the bundle — meaning buyers receive OCP entitlements as part of their Cloud Pak subscription. Second, Cloud Paks use VPC (Virtual Processor Core) as the primary pricing unit, replacing the older PVU (Processor Value Unit) model for these products. Third, Cloud Paks are subscription-based with annual or multi-year terms, replacing perpetual licences with ongoing subscription fees.
For context on IBM's broader licensing models including PVU for legacy products, see our IBM PVU Licensing Guide. For IBM's overall negotiation framework, see the IBM Software License Negotiation Guide.
IBM Cloud Paks are IBM's primary vehicle for transitioning enterprise customers from PVU-licensed perpetual software to subscription-based revenue. The VPC pricing model is typically 20–35% more expensive than equivalent PVU licensing for organisations with sub-capacity ILMT deployments — but IBM presents it as simpler and "cloud-ready." Always model the true cost comparison before agreeing to migrate existing PVU entitlements to Cloud Paks.
VPC stands for Virtual Processor Core. It is the licensing metric used for IBM Cloud Paks and a growing range of other IBM products. Understanding how VPCs are counted — and where counting rules create commercial risk — is essential to managing Cloud Pak costs.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
A VPC is counted per virtual processor core (vCPU) assigned to the container workload. IBM counts VPCs based on the number of VCPUs allocated to the Kubernetes worker nodes running Cloud Pak workloads — regardless of actual utilisation. This is a critical distinction: a node provisioned with 16 vCPUs but running at 10% utilisation still counts as 16 VPCs.
| Environment | PVU Count (sub-cap) | VPC Count | Cost Impact |
|---|---|---|---|
| 16-core server, IBM workload on 4 VMs × 4 vCPU | 16 VMs × 70 PVU = 1,120 PVU | 16 VPCs | Depends on unit price — often similar or worse on VPC for dense VM environments |
| Kubernetes: 3 worker nodes × 8 vCPU | N/A (not applicable) | 24 VPCs | VPC model directly maps to infrastructure size |
| Cloud instance: 4 × m5.2xlarge (8 vCPU) | 32 vCPU × 70 PVU = 2,240 PVU | 32 VPCs | VPC model often 20–30% cheaper for cloud-native workloads vs full PVU |
IBM offers eight Cloud Pak product lines covering integration, data, automation, security, network automation, Watson AIOps, business automation, and multi-cloud management. Each includes bundled Red Hat OpenShift and varies in scope and pricing.
| Cloud Pak | Key Products Included | Primary Use Case | List Price Range (VPC/yr) |
|---|---|---|---|
| Cloud Pak for Integration | App Connect, MQ, API Connect, DataPower, Kafka (EventStreams) | API, messaging, integration | £18,000–£28,000/VPC |
| Cloud Pak for Data | Db2, Watson Studio, DataStage, Watson Discovery, OpenScale | Data, AI, analytics platform | £14,000–£22,000/VPC |
| Cloud Pak for Business Automation | Business Automation Workflow, ODM, FileNet, Content Services | BPM, RPA, document management | £12,000–£20,000/VPC |
| Cloud Pak for Security | QRadar, SOAR, ISAM, Guardium, MaaS360 | SIEM, IAM, data security | £16,000–£26,000/VPC |
| Cloud Pak for Network Automation | Network Automation, Telco Network Cloud Manager | Telco network management | £10,000–£18,000/VPC |
| Cloud Pak for Watson AIOps | AIOps Insights, Instana, Turbonomic | IT operations management | £15,000–£24,000/VPC |
List prices are indicative — actual negotiated pricing varies significantly (35–55% below list is achievable). Contact IBM or see our advisor matching service for benchmark guidance.
Every IBM Cloud Pak subscription includes Red Hat OpenShift Container Platform entitlements. This is a meaningful commercial inclusion — OCP licences are not cheap (Red Hat lists OCP at approximately £5,000–£10,000 per core/year), so the bundling affects total value calculations significantly.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
IBM Cloud Pak subscriptions include OCP worker node entitlements in a 1:1 ratio with the VPCs purchased. A 20 VPC Cloud Pak for Integration subscription includes 20 OCP worker node core entitlements. These OCP entitlements can be used for the Cloud Pak workload itself — they don't provide general-purpose OCP licences for non-IBM workloads.
Specifically: the OCP entitlement bundled with Cloud Paks is limited to running the Cloud Pak components. You cannot use these OCP entitlements to run unrelated containerised applications without a separate Red Hat OpenShift subscription. This is a commonly misunderstood point that creates post-audit compliance risk.
If your organisation is also purchasing or renewing Red Hat OpenShift separately, the OCP-bundled-in-Cloud-Pak entitlements create a negotiating opportunity. IBM account teams can sometimes be persuaded to apply Cloud Pak OCP entitlements more broadly, or to credit existing OCP subscriptions against Cloud Pak pricing, particularly in large multi-product transactions. This requires IBM-Red Hat joint commercial approval.
Running Cloud Pak workloads on a shared Kubernetes cluster without proper IBM License Service configuration results in all cluster VCPUs being counted — not just the Cloud Pak nodes. A 200 vCPU cluster running only 40 vCPUs of Cloud Pak workload will be charged for all 200 VPCs without proper scoping. Always deploy IBM License Service with namespace-to-VPC mapping from day one.
IBM Cloud Pak subscriptions typically include limited development and test entitlements. Many organisations inadvertently deploy Cloud Pak in development environments using production licences, doubling their VPC count. IBM's IPLA (International Program License Agreement) terms for Cloud Paks have specific rules on dev/test usage — verify these before spinning up non-production environments.
Cloud Paks like Cloud Pak for Data include dozens of optional "services" (Watson Studio, Db2, DataStage, OpenScale, etc.) that can be activated via the Cloud Pak console. Each activated service may trigger additional VPC charges or licence compliance requirements under your agreement. Activating services "to evaluate them" without reviewing licensing implications is a common and expensive mistake.
Kubernetes HPA (Horizontal Pod Autoscaler) and cluster autoscaler can dynamically expand the number of worker nodes during peak load — temporarily increasing your VPC count. IBM's licence measurement is based on the maximum concurrent VPC count within a measurement period, not average usage. Spikes from auto-scaling can inflate your required licence position significantly. Configure cloud autoscaling with VPC licence limits in mind.
IBM typically offers significant discounts (15–25%) for 3-year Cloud Pak subscriptions versus annual terms. The trap is that 3-year commitments rarely include scale-down rights — if you need fewer VPCs in year 2 or 3, you're still paying for the full original quantity. Always negotiate scale-down rights or annual quantity review clauses into multi-year Cloud Pak agreements.
As noted above, the OCP entitlements bundled with Cloud Paks apply only to Cloud Pak workloads. Organisations running a mixed OpenShift environment may inadvertently purchase separate OCP subscriptions for workloads that could be covered by the Cloud Pak bundle — or conversely, assume Cloud Pak OCP entitlements cover all their OpenShift nodes when they don't. Get clarity in writing on OCP entitlement scope before signing.
IBM offers "Cloud Pak migration programmes" for customers transitioning from PVU-licensed products to Cloud Paks. These programmes often appear attractive (IBM offers credits or discounts to incentivise the transition) but can lock organisations into higher long-term subscription costs versus continuing with perpetual licences. Model 5-year total cost before accepting any Cloud Pak transition offer.
IBM is actively auditing Cloud Pak deployments, particularly for VPC counting accuracy and OCP entitlement scope. IBM License Service deployment and accurate configuration is not optional — it's your primary defence against over-count audit findings. Treat IBM License Service setup as a day-one compliance requirement, not an afterthought.
IBM Cloud Pak list pricing is set high to create room for negotiation. The unit VPC price is the number to focus on, not the bundle discount percentage. Benchmark your VPC price against other enterprises in your sector — ranges of 40–55% below list are achievable for organisations spending £1M+ on Cloud Paks. See our Top IBM Negotiation Advisors for firms that specialise in IBM Cloud Pak benchmarking.
IBM's total commercial relationship with your organisation — across Passport Advantage, Cloud Paks, and Red Hat — can be leveraged as a single negotiating unit. Larger total IBM spend unlocks deeper discounts on Cloud Pak VPC pricing. See IBM Passport Advantage Negotiation Strategies for how to consolidate this leverage effectively.
Negotiate the right to reduce VPC count annually in any multi-year Cloud Pak agreement. IBM will resist, but persistent enterprise buyers — particularly those with credible migration alternatives — can secure annual true-down rights with no penalty for 10–15% VPC reductions. This protects against over-provisioning and gives flexibility as architectural decisions evolve.
Red Hat OpenShift itself faces competitive pressure from upstream Kubernetes (EKS, AKS, GKE). If your organisation is evaluating cloud-managed Kubernetes as an alternative to OpenShift (and by extension, Cloud Paks), present this competitive dynamic explicitly. IBM account teams respond to OCP competitive risk — it often accelerates Cloud Pak discount approval at senior IBM levels.
IBM's standard Cloud Pak terms include limited dev/test rights. Negotiate for specific, clearly defined development environment entitlements (typically 25–50% of production VPCs) at zero additional cost. This avoids the trap of inadvertently using production licences in dev/test environments or paying separately for development deployments.
IBM is gradually introducing consumption-based Cloud Pak pricing (pay-per-use) for some products through IBM Cloud and IBM Technology Expert Labs. For smaller organisations or initial deployments, requesting a consumption-based pilot — with a commitment to convert to subscription at favourable pricing if usage justifies it — gives you real consumption data to anchor future subscription negotiations.
Before signing any Cloud Pak agreement, document in writing exactly how VPCs will be counted in your environment: which nodes are in scope, how IBM License Service will be configured, and what the agreed measurement methodology is. An ambiguous VPC counting methodology creates audit risk and post-deployment cost surprises. Specificity at contract time is far cheaper than disputes at audit time.
IBM's Cloud Pak products bundle Red Hat OpenShift but also compete indirectly with pure Red Hat offerings. In some cases, choosing Red Hat-only solutions (OpenShift plus upstream Apache components) is technically equivalent to Cloud Pak at lower cost. Present this option to IBM as an alternative — IBM would prefer to retain Cloud Pak revenue rather than lose to a Red Hat-only deployment that generates lower IBM ASP. For more on IBM open source alternatives and migration leverage, see IBM to Open Source Migration: Leveraging for Better Pricing.
Need help benchmarking or negotiating your IBM Cloud Pak agreement?
Not every organisation benefits from the Cloud Pak bundling model. The right structure depends on which IBM products you actually need, your existing PVU licensing, your Kubernetes maturity, and your medium-term architectural direction.
| Scenario | Best Commercial Model | Why |
|---|---|---|
| Using multiple IBM integration products (MQ, App Connect, API Connect) | Cloud Pak for Integration | Bundled pricing typically cheaper than individual licences. OCP inclusion adds value if deploying on OpenShift. |
| Single IBM product (e.g., only Db2) | Individual licence | Cloud Pak includes unneeded components. VPC pricing rarely more economical for single-product use. |
| Already have Red Hat OpenShift subscription | Negotiate OCP credit | Avoid paying for OCP twice. Insist on credit for existing OCP against Cloud Pak bundle pricing. |
| Evaluating open source alternatives | Delay Cloud Pak commitment | Complete open source PoC first. Use migration credibility as leverage before signing Cloud Pak multi-year deal. |
| On-premises IBM mainframe shop | PVU/MLC remains appropriate | Cloud Paks don't run on z/OS. Mainframe-centric orgs get limited benefit from Cloud Pak migration. |
For a broader view of IBM audit risk and compliance, see IBM License Audit: What Enterprises Need to Know and IBM ILMT Compliance Guide. For overall IT contract negotiation principles applicable to Cloud Pak agreements, see IT Contract Negotiation Strategy and 25 Software Contract Red Flags to Watch For.
Cloud Pak VPC pricing is highly negotiable. Our matched advisors specialise in IBM Cloud Pak benchmarking, OCP bundling analysis, and achieving 30–45% reductions on Cloud Pak renewals.