Red Hat is a subscription business inside an IBM perpetual licensing world.
Red Hat subscriptions, the Red Hat Enterprise Agreement, OpenShift, RHEL, Ansible, JBoss, and the convergence with IBM Cloud Paks. We read the joint position so neither side gets double counted.
Two contract models on the same customer.
Red Hat became a wholly owned subsidiary of IBM in 2019. The commercial model on the Red Hat side has remained largely intact. Subscriptions, the Red Hat Enterprise Agreement (REA), and the per node, per socket, or per core subscription metrics specific to each product are still the operative frame. IBM has not migrated Red Hat customers onto Passport Advantage. The two contract systems sit side by side, and for large enterprises both are in force on the same estate.
The complications appear at three places. First, where IBM Cloud Paks include OpenShift entitlement as part of the Pak. Second, where Red Hat products are sold through IBM channels and the entitlement record is split between the two systems. Third, where renewal cycles on the Red Hat side and the IBM side are not aligned, which creates leverage and counter leverage at different times of the year. We read all three.
The Red Hat audit and entitlement verification mechanics are different from the IBM mechanics. Red Hat operates a subscription model where the deployment must not exceed the subscription count, but the reporting tooling is the Red Hat Subscription Manager and the Red Hat Hybrid Cloud Console. ILMT does not apply. The audit posture is different and the negotiation moves are different. Read the license consulting and negotiation pages for context.
What we cover.
- Red Hat Enterprise Linux (RHEL).
- Red Hat OpenShift Container Platform.
- Red Hat Ansible Automation Platform.
- Red Hat JBoss EAP and middleware.
- Red Hat OpenStack Platform.
- Red Hat Satellite.
- Red Hat Insights and Smart Management.
How we read the joint Red Hat and IBM position.
Subscription inventory
Pull the active Red Hat subscription view from the Red Hat customer portal. Map by product, by metric, by start and end date. Identify subscriptions acquired through IBM channels versus directly from Red Hat. The contract path matters.
Deployment reconciliation
Reconcile Red Hat Subscription Manager and Hybrid Cloud Console data against the subscription count. Identify nodes not registered, nodes double counted, and nodes deployed against a subscription that has lapsed.
Cloud Pak OpenShift overlap
For estates with IBM Cloud Paks, validate the OpenShift entitlement that comes with the Pak against the standalone OpenShift subscription. Flag any double counting. Read the Cloud Pak expertise.
Renewal sequencing
Align the Red Hat renewal cycle with the IBM renewal cycle. Sequence the negotiation to use the joint footprint as leverage. Document the position the buyer should hold at each step. Hand over to the negotiation practice.
Common failure modes.
- OpenShift standalone subscriptions running alongside Pak bundled OpenShift, both billed.
- RHEL subscriptions tied to a machine that has been decommissioned.
- Subscriptions on developer use deployed in production without conversion.
- Ansible Tower subscriptions exceeded on managed node count.
- JBoss Enterprise Application Platform deployed beyond the licensed core count.
- Mixed channel buying so that the entitlement view is split.
Where the leverage is.
- Multi year subscription commits in exchange for discount and price protection.
- Cross product portfolio commits across RHEL, OpenShift, Ansible.
- Conversion of standalone subscriptions into Cloud Pak entitlement where the math works.
- Use of competitive alternatives, particularly on RHEL and on container platforms.
- Alignment of Red Hat and IBM renewal dates so the negotiations stack.
- Negotiating self managed pricing where SaaS pricing is being pushed.
How clients approach Red Hat licensing.
Has IBM merged Red Hat onto Passport Advantage?
No. Red Hat continues to operate on the REA with subscription metrics. Procurement may flow through IBM in some cases, but the underlying subscription terms are the REA.
Does ILMT report on Red Hat?
ILMT can discover RHEL and OpenShift nodes, but it is not the system Red Hat audits against. Red Hat uses the Subscription Manager and Hybrid Cloud Console data.
Is OpenShift bundled into every Cloud Pak?
Most current Cloud Paks include the right to run OpenShift only for the nodes that host the Pak workload. OpenShift used for other workloads needs a separate subscription. See Cloud Paks.
How does Red Hat handle developer use of RHEL?
Red Hat Developer Subscription is free for individual use. Production deployment requires a paid subscription. The boundary is product specific and worth reading before scaling a deployment.
What about CentOS and AlmaLinux?
CentOS Linux as a downstream of RHEL was discontinued. AlmaLinux and Rocky Linux are community supported alternatives. Where they are in the estate, the licensing model and the support posture are different. We document this where it sits next to RHEL.
Resources
Expertise
Services
Need an independent read on this area?
A senior advisor responds within 24 hours and scopes a credible engagement structure within a week.
Get an independent read on this area of your IBM estate.
Tell us where you are in the cycle. A senior advisor will respond within 24 hours with a scoped engagement structure and an availability window. No sales call, no pitch deck. We do not resell IBM software. We have no IBM Business Partner status. Our recommendations are constrained only by what is good for the buyer.
Read more on why independence matters or browse the services overview for engagement structures.
Request a conversation
Corporate email required. Personal email addresses are not accepted.