>
White Paper . Red Hat

OpenShift Licensing Deep Dive.

The buyer side reference for Red Hat OpenShift licensing. The subscription metric, the bare metal vs virtual node distinction, the bundled entitlement inside the Cloud Pak portfolio, the overlap question, and the renewal sequencing.

Pages
34
Time to read
44 min
Updated
Q2 2026

What is inside.

  • OpenShift subscriptions: 2 core, 4 core, 16 core, bare metal nodes. The premium versus standard support tier. The conversion to vCPU when running on virtualised infrastructure.
  • The OpenShift entitlement bundled with the Cloud Paks (Applications, Integration, Data, Watson AIOps, Security). The container ratio per Cloud Pak. The boundary the bundle does not cover.
  • The overlap between standalone OpenShift subscriptions and Cloud Pak bundled OpenShift. The duplication that drives unintentional double spend. The methodology to identify and consolidate.
  • The cluster sizing question for licence accountability. The IBM Licence Service per cluster reporting. The Red Hat subscription reconciliation. The two ledgers that must agree.
  • The sub capacity treatment of IBM software running on OpenShift. The VPC and PVU translation to container ratios. The IBM Licence Service requirement on Cloud Pak workloads.
  • The renewal sequencing decision for OpenShift and the IBM Cloud Paks. The misaligned renewal dates question. The benefit of consolidating onto a single anniversary.
  • OpenShift on AWS (ROSA), Azure (ARO), Google Cloud (OSD). The licensing treatment of each. The buyer side decision on cloud committed spend versus Red Hat direct subscription.
  • The buyer side close position on OpenShift. The four commercial asks for the renewal. The three contractual asks for the multi year. The two operational disciplines for the steady state.

Who this is for.

  • The cloud architect operating the OpenShift estate at scale.
  • The director of platform engineering owning the renewal.
  • The procurement lead negotiating the Red Hat enterprise agreement.
  • The CIO consolidating the IBM and Red Hat relationship.
Read the white paper

Access the full guide.

Corporate email required. We use the address to verify the request and to send the related papers in the series.

Please use your corporate email address.
By submitting you agree to our privacy notice. We do not share your details with IBM or any third party.
Independence statement. IBM Licensing Experts is an independent advisory firm. We are not an IBM Business Partner, reseller, or affiliate. We have no resell margin tied to our recommendations. This guide reflects our reading of IBM published terms and current customer practice. Read more on why independence matters.
Table of contents

The 8 chapters in this guide.

1. The OpenShift subscription model

OpenShift subscriptions: 2 core, 4 core, 16 core, bare metal nodes. The premium versus standard support tier. The conversion to vCPU when running on virtualised infrastructure.

2. Cloud Pak bundled OpenShift

The OpenShift entitlement bundled with the Cloud Paks (Applications, Integration, Data, Watson AIOps, Security). The container ratio per Cloud Pak. The boundary the bundle does not cover.

3. The overlap question

The overlap between standalone OpenShift subscriptions and Cloud Pak bundled OpenShift. The duplication that drives unintentional double spend. The methodology to identify and consolidate.

4. OpenShift cluster sizing

The cluster sizing question for licence accountability. The IBM Licence Service per cluster reporting. The Red Hat subscription reconciliation. The two ledgers that must agree.

5. Sub capacity on containers

The sub capacity treatment of IBM software running on OpenShift. The VPC and PVU translation to container ratios. The IBM Licence Service requirement on Cloud Pak workloads.

6. Renewal sequencing

The renewal sequencing decision for OpenShift and the IBM Cloud Paks. The misaligned renewal dates question. The benefit of consolidating onto a single anniversary.

7. Hyperscaler OpenShift

OpenShift on AWS (ROSA), Azure (ARO), Google Cloud (OSD). The licensing treatment of each. The buyer side decision on cloud committed spend versus Red Hat direct subscription.

8. The close position

The buyer side close position on OpenShift. The four commercial asks for the renewal. The three contractual asks for the multi year. The two operational disciplines for the steady state.

Related expertise

Where this guide connects.

This guide connects to Red Hat, Cloud Paks, Sub Capacity, License Consulting, and the broader services portfolio. The work is most powerful when paired with the underlying operational evidence and the renewal cycle timing. See the related papers below and the insights blog for ongoing commentary.

Related white papers

The connected papers in the series.

Red Hat Enterprise Strategy

The strategic frame for the Red Hat relationship.

Read the guide

Cloud Pak Licensing Guide

The Cloud Pak entitlement reference.

Read the guide

Cloud Pak ROI Analysis

The financial case for the OpenShift / Cloud Pak consolidation.

Read the guide