Every system and virtual instance running RHEL needs a subscription, whatever the version. Do your counts match?
Red Hat Enterprise Linux (RHEL) and OpenShift subscriptions count every system, VM, socket-pair and core you deploy, and Red Hat’s agreement lets it check your records. We match your subscriptions to what runs and find the cheapest valid mix before a review.
5%Underpayment above which you also pay for Red Hat’s inspection (Red Hat Enterprise Agreement, EMEA, November 2021)
| Deployment | What one subscription covers |
|---|---|
| Physical server | One socket-pair |
| Virtual machines | Two virtual nodes |
| Virtual Datacenter | Unlimited guests per host socket-pair |
| OpenShift | One core-pair: 2 cores or 4 vCPUs |
Red Hat Enterprise Linux and self-managed OpenShift subscription guides.
Red Hat counts deployments, and deployments grow faster than subscription records. The usual gaps:
Systems nobody countedSubscriptions are owed for every system and virtual instance running RHEL, whatever the version, so old releases and forgotten VMs count too.
The wrong model for the hostPer-guest subscriptions on a dense host where a Virtual Datacenter subscription covers unlimited guests, or Virtual Datacenter on a host with a handful of VMs.
Mixed support levels in a clusterPooling Virtual Datacenter subscriptions needs the same support level on every host in the cluster.
OpenShift on the control planeControl plane nodes are included, until application workloads run on them. In a compact three-node cluster, every core counts.
Cloud on the wrong subscriptionSubscriptions can move between physical, virtual and cloud deployments through Red Hat Cloud Access, but self-support subscriptions cannot be used with Cloud Access.
Growth never reportedThe agreement expects extra units to be reported promptly, with the dates they were deployed, and invoiced. Unreported growth surfaces in a review.
| Rule | What applies |
|---|---|
| Coverage | A subscription for every system and virtual instance running RHEL, regardless of version |
| Physical servers | Per socket-pair: up to 2 occupied sockets. Stack subscriptions for larger machines: an 8-socket server needs 4 |
| Virtual machines | One subscription covers 2 virtual nodes: 40 guests need 20 subscriptions |
| Virtual Datacenter | Unlimited RHEL guests on supported hypervisors (Red Hat Virtualization, VMware, Microsoft Hyper-V), per physical socket-pair. Uniform support levels for pooling across a cluster |
| Public cloud | Move subscriptions between physical, virtual and cloud through Red Hat Cloud Access. Not self-support subscriptions |
| OpenShift | Per core-pair: 2 physical cores or 4 vCPUs, counted across the cluster. Control plane nodes are included unless they run application workloads |
Red Hat Enterprise Linux subscription guide (21 July 2026) and the self-managed Red Hat OpenShift subscription guide. Your Enterprise Agreement and its product appendix govern your terms.
| Clause | Red Hat Enterprise Agreement (EMEA, effective November 2021) |
|---|---|
| Basis of fees | You order and pay for the units you use or deploy |
| Extra units | Report them promptly, with the dates they were used or deployed. Red Hat invoices them |
| Review | Red Hat or its designee may inspect your facilities and records while the agreement is in effect and for one year after, with at least 10 days’ notice for on-site visits |
| Findings | Resolve any non-compliance or underpayment within 15 days of notice |
| Inspection cost | Yours if the underpayment exceeds 5% |
Agreements differ by region and date. Check the version referenced in your order.
These examples use Red Hat’s counting rules. They show how the count moves; the cheaper option depends on your contracted prices.
| RHEL guests on the host | Per-guest subscriptions (2 guests each) | Virtual Datacenter subscriptions |
|---|---|---|
| 4 | 2 | 1 |
| 10 | 5 | 1 |
| 20 | 10 | 1 |
| 40 | 20 | 1 |
The break-even is the guest count at which one Virtual Datacenter subscription costs less than the guest subscriptions it replaces, at your prices.
| Cluster | How it counts | Core-pair subscriptions |
|---|---|---|
| Workers with 250 vCPUs in total | 250 ÷ 4, rounded up | 63 |
| Workers on physical servers, 128 cores in total | 128 ÷ 2 | 64 |
| Compact three-node cluster, 32 cores each | Applications run on the control plane, so all 96 cores count: 96 ÷ 2 | 48 |
Control plane nodes in a standard cluster are included and not counted.
Deployment inventoryRHEL and OpenShift by host, VM, cloud account and cluster.
Subscription positionWhat you must subscribe against what you hold, by model and support level.
Optimization optionsWhere a different subscription model or support level lowers the count, with the trade-offs.
Review readinessThe records Red Hat would ask for, checked and in order.
IndependentWe do not resell any publisher’s licenses or earn income from publishers. Our focus is our customers.
Evidence firstWe check the records a publisher would ask for before anyone else sees them, so you know your position first.
Every publisher in the estateIBM, Red Hat, Oracle, Microsoft and VMware licensing often sit on the same servers. We look at what a change in one does to the others.
By subscription. A physical server is subscribed per socket-pair, up to two occupied sockets, and larger servers stack subscriptions. In virtual environments one subscription covers two virtual nodes, or a Virtual Datacenter subscription covers unlimited guests on a host socket-pair.
Every system and virtual instance running RHEL needs to be covered, regardless of version. On a dense host a Virtual Datacenter subscription can cover all the guests; with a few guests, per-guest subscriptions at two VMs each may cost less.
A subscription for high-density virtualization: unlimited RHEL guests on a supported hypervisor such as Red Hat Virtualization, VMware or Microsoft Hyper-V, sold per physical socket-pair. To pool it across a cluster, every host needs the same support level.
Self-managed OpenShift is subscribed per core-pair (2 cores or 4 vCPUs), so the cost is the core-pair count across the cluster times the subscription price for your edition and support level. Control plane nodes are included unless they run applications.
Self-managed OpenShift is subscribed per core-pair: 2 physical cores or 4 vCPUs, counted across the cluster. Control plane nodes are included unless application workloads run on them, as they do in a compact three-node cluster.
Yes, through Red Hat Cloud Access: subscriptions can move between physical, virtual and cloud deployments without changing their terms. Self-support subscriptions are the exception.
Red Hat’s Enterprise Agreement lets Red Hat or its designee inspect your facilities and records while the agreement is in effect and for a year after. In the EMEA version of November 2021, you pay for the inspection if the underpayment exceeds 5%.
The agreement asks you to report the extra units promptly, with the dates they were deployed, and Red Hat invoices them. We help you establish the count first.
No. Rythium is independent and does not resell publisher licenses or earn income from publishers.
We charge a fixed fee for the assessment, a success-based fee or a hybrid, case by case, depending on the scope and the deliverables you need. Contact us for a scoped quote and tell us your preference.
Tell us what you run and when your subscriptions renew. We will show you what you must cover, what you hold and the cheapest valid way to close the gap.
Cookies on rythium.com
We use essential cookies to make this site work, and additional cookies to measure visits and our ads. You can reject the additional ones or choose which to keep. Privacy Policy