Know your OpenShift position before the renewal letter
Red Hat OpenShift is licensed by the core-pair — not by node or socket — and that one fact is where six-figure true-ups come from. This is the buyer-side playbook for knowing your real position before an audit or renewal forces the conversation.
“RenewalIntel exists because of a $250,000 surprise. Our founder watched an OpenShift renewal arrive with a core-pair overage no one saw coming — the cluster had quietly scaled past its entitlement months earlier. That gap was knowable the whole time. We built the platform so it never hides again.”
Three ways OpenShift overage builds up unseen
Core-pair, not node
OpenShift is licensed by the core-pair — two physical cores, or four vCPUs, per unit. Counting nodes or sockets misstates the position from the start, and partial pairs round up.
Autoscaling drift
Worker nodes that scale out under load add cores — and core-pairs — that no one reconciles against the subscription until the renewal letter arrives.
Offering mismatch
Self-managed, ROSA, ARO, and Dedicated each entitle cores differently. Apply the wrong model and the gap is mispriced in either direction.
From subscription to a defensible position
No market benchmarks or guesswork — your position is measured against what your cluster actually runs.
Bring in your data
Pull your Red Hat subscriptions and node inventory — by export or read-only collection. Nothing reaches into your cluster.
Reconcile per SKU
RenewalIntel resolves the SKUs, applies core-pair math with the right offering rules, and computes entitled vs consumed core-pairs.
Get the verdict + evidence
A clear position, the priced gap, and the underlying calculation — every number traced to its source, before the invoice does the math for you.
Guides for every OpenShift licensing question
How Red Hat core-pair licensing actually works
Core-pairs, rounding, and the SKU math behind every OpenShift subscription.
Read guideROSA, ARO, and self-managed: which OpenShift cores are billable
The entitlement model differs by offering — and getting it wrong misprices the gap.
Read guideWhy autoscaling quietly breaks your OpenShift subscription
The single most common source of a surprise OpenShift bill, and how to stay ahead of it.
Read guideThe OpenShift renewal and audit checklist
Walk in with your own defensible number instead of reacting to Red Hat’s figure.
Read guideKnow your OpenShift position before the audit
Reconcile entitled core-pairs against what your cluster actually runs. No credit card required.