Red Hat Subscriptions Explained: RHEL, Ansible and OpenShift Licensing
This page answers the Red Hat subscription questions buyers actually ask — how RHEL counts virtual machines, what a “managed node” means in Ansible, what OpenShift Platform Plus adds, and whether a three-year term saves you anything. Figures are Red Hat list prices in USD unless stated.
The short answer: RHEL is licensed per two-socket physical node or two virtual machines — vCPU count is irrelevant. Virtual Datacenter becomes cheaper above about seven guests per host socket pair. Ansible licenses your whole managed estate, not what you automate concurrently, and the definition of a node is much broader than servers. And across every Red Hat product line, three-year subscriptions are priced at exactly three times the annual price — multi-year value comes from price protection and negotiating leverage, not a published discount.
Red Hat Enterprise Linux
What does RHEL cost?
| Subscription | SKU | List price, 1 year |
|---|---|---|
| RHEL Server, Self-support | RH00005 | $383.90 |
| RHEL Server, Standard | RH00004 | $878.90 |
| RHEL Server, Premium | RH00003 | $1,428.90 |
| RHEL Workstation, Self-support | RH0986300 | $196.90 |
| RHEL Workstation, Standard | RH0958488 | $328.90 |
| RHEL for SAP Solutions, Standard | RH00764 | $1,923.90 |
| RHEL for SAP Solutions, Premium | RH00763 | $2,363.90 |
| RHEL for Virtual Datacenters, Standard | RH00002 | $3,023.79 |
| RHEL for Virtual Datacenters, Premium | RH00001 | $4,838.79 |
Server subscriptions are priced per socket pair. Workstation is priced per workstation.
How are virtual machines counted for RHEL?
Two guests per subscription, regardless of how many vCPUs each has. Red Hat’s rule is that one RHEL subscription entitles a physical node with up to 2 sockets or 2 virtual nodes, regardless of virtual sockets. Twenty VMs needs ten subscriptions. Virtual CPU counts do not enter into it.
Three corollaries people get wrong:
- A single-socket physical server still consumes a whole subscription. You cannot split one.
- A four-socket server needs two stacked subscriptions.
- Cloud instances under bring-your-own-subscription are counted exactly like VMs — divided by two.
When does Virtual Datacenter become worth it?
Virtual Datacenter switches the model entirely: you buy per host socket pair and run an unlimited number of RHEL guests on that host. The crossover is arithmetic:
$3,023.79 ÷ $878.90 = 3.44 standard subscriptions, which covers 6.9 guests. Above roughly seven RHEL guests per host socket pair, Virtual Datacenter is cheaper. That is probably the single most useful number on this page, and it is the calculation most virtualised estates have never actually run.
Do I need Premium support?
There are three concrete differences, and one of them is not about support at all:
| Severity | Standard | Premium |
|---|---|---|
| Severity 1 | 1 business hour | 1 hour, 24×7 |
| Severity 2 | 4 business hours | 2 hours, 24×7 |
| Severity 3 | 1 business day | 4 business hours |
| Severity 4 | 2 business days | 8 business hours |
| Self-support | No SLA. Updates and Customer Portal access only. | |
The third difference is the commercially interesting one: Extended Update Support is included free with x86-64 Premium subscriptions and is a paid add-on on Standard, at $273.90 per year for the limited-guests SKU. The Premium premium is $550 per socket pair per year. If you need to pin minor releases, EUS alone recovers half of that immediately.
Self-support cannot be used on virtual or cloud instances. Red Hat restricts RH00005 to physical systems. Since most dev and test estates are virtualised, the cheapest SKU is usually unusable for the workload people buy it for. This trips up buyers constantly.
What about the free Developer subscription?
The Red Hat Developer Subscription for Individuals is genuinely free and allows installation on up to 16 systems, physical or virtual. Permitted use covers demos, prototyping, QA, cloud access — and, contrary to widespread belief, small production use is explicitly allowed. The catch is that it is self-supported: Customer Portal knowledge base only, no support cases. A separate paid Developer Subscription for Teams exists for organisations.
What is EUS and ELS, and when do I need them?
Extended Update Support lets you stay on a single minor release for 24 months, receiving full errata for the first six months and then critical and important security fixes plus urgent bug fixes for the remainder. Included with x86-64 Premium; an add-on to Standard. RHEL for SAP Solutions includes it at both levels — do not buy it separately there.
Extended Life Cycle Support applies after the ten-year life cycle ends, providing selected critical security fixes and urgent bug fixes for the last minor release. Only Standard and Premium subscriptions qualify — Desktop and Workstation are ineligible. Without ELS, an estate in the Extended Life phase receives no bug fixes, no security fixes, no hardware enablement and no root cause analysis.
Relevant dates: RHEL 7 is past maintenance and ELS-only until 31 May 2029. RHEL 8 full support ended 31 May 2024 with maintenance ending 31 May 2029. RHEL 9 full support ends 31 May 2027. Red Hat describes all future life cycle dates as approximate and subject to change.
Red Hat Ansible Automation Platform
How is Ansible licensed?
Per managed node per year, sold in node-count tiers, with Standard (business hours) or Premium (24×7) support. Red Hat does not publish Ansible pricing — it is quote-only through Red Hat or a partner. We are a Red Hat partner, so contact us for details or a special quote on your node count.
What we can say about the shape of it from channel list pricing: per-node rates fall roughly 14% moving from a 100-node tier to a 5,000-node tier, and there is essentially no further volume break between 5,000 and 10,000 nodes. If you are sizing near 5,000, there is little to gain by rounding up.
What counts as a managed node?
Far more than servers. Red Hat defines a managed node as any virtual node, physical node, device or identifiable instance of software being directly or indirectly managed by Ansible Automation Platform. That word “indirectly” is doing a lot of work.
Things that count that buyers routinely miss:
- Non-server devices — storage arrays, network gear, SDN, wireless and networking controllers.
- Software instances, not just hosts. Containers, appliances, databases, middleware, applications. One VM running three managed middleware instances can be three or more nodes.
- Indirectly managed targets. If Ansible drives a cloud API or a controller that configures 500 endpoints, each identifiable instance counts.
- Clustered platforms count per instance, not once per cluster.
You cannot rotate entitlements. Red Hat explicitly prohibits managing a total estate larger than your entitled node count, and deleting hosts from the inventory to free capacity is not permitted. This is the number one true-up exposure in Ansible. Buyers scope on “how many servers do we automate today” and get trued up on “how many identifiable instances exist in the inventory.”
One mitigating rule: multiple identifiers for the same host — an alias plus an IP plus an FQDN — do not multiply entitlements.
Red Hat OpenShift
Which OpenShift edition do I need?
There are four self-managed editions, not three:
- OpenShift Kubernetes Engine — entry level, foundational enterprise Kubernetes.
- OpenShift Virtualization Engine — VM workloads only, no container functionality. Aimed squarely at VMware replacement.
- OpenShift Container Platform — adds the developer console, Serverless, Service Mesh, Pipelines and GitOps.
- OpenShift Platform Plus — Red Hat’s recommended tier.
Managed services are ROSA on AWS, ARO on Azure and OpenShift Dedicated on Google Cloud, all at a 99.95% SLA, plus OpenShift on IBM Cloud at 99.99%.
What does Platform Plus add?
Everything in Container Platform, plus four products:
- Advanced Cluster Management — application lifecycle and governance across multiple clusters from one console
- Advanced Cluster Security — Kubernetes-native security with multi-cluster governance
- OpenShift Data Foundation Essentials — persistent software-defined storage. Note Essentials: it is a capacity-limited entitlement, not unlimited ODF. Contact us for the included capacity ceiling before you size storage.
- Red Hat Quay — a scalable central registry
At list, Platform Plus is roughly a 24% uplift over Container Platform. Buying Advanced Cluster Management and Advanced Cluster Security separately costs substantially more, which is why Red Hat marks Platform Plus as recommended. If you run more than a couple of clusters, or have a container security requirement, it is usually the cheaper path.
How is self-managed OpenShift priced?
Two units are live simultaneously: per 2 cores or 4 vCPUs per year, or per physical node for bare metal.
Run both calculations. The bare-metal node SKU is often cheaper than per-core licensing on dense hosts. The crossover sits at roughly 18 cores per node — above that, node-based licensing wins. Estates running modern high-core-count servers on per-core licensing are frequently overpaying for no reason other than that nobody re-ran the maths after a hardware refresh.
Managed OpenShift pricing
ROSA and ARO both charge $0.171 per hour per 4 worker vCPUs. ROSA with hosted control planes adds a $0.25 per hour cluster fee. Unlike self-managed, managed OpenShift has real published multi-year discounts: $1,500 per 4 vCPU per year on demand, $1,000 on a one-year commitment, $667 on three years — savings of 33% to 55%. Infrastructure is billed separately by the cloud provider.
Should I sign a three-year Red Hat agreement?
Not for a list discount — there isn’t one. Across RHEL, Ansible and every OpenShift edition, three-year SKUs are priced at exactly three times the one-year SKU. Sign multi-year for price protection and as negotiating leverage for a discount off list, not because the list itself rewards it. Red Hat raised EUR and GBP pricing 10% in April 2025, so protection has real value. The exception is ROSA and ARO, where multi-year commitment discounts are published and steep.
Frequently asked questions
What is the cost difference between OpenShift and plain Kubernetes?
Upstream Kubernetes has no licence cost, so the whole question is whether the included platform — console, Serverless, Service Mesh, Pipelines, GitOps, lifecycle and CVE management, certified support — costs less than staffing the equivalent yourself. For a 100-core cluster, self-managed Container Platform at list runs into six figures annually before discount. That is a real number, and so is the cost of the two or three platform engineers you would otherwise need. The honest answer depends on your headcount, not on the licence.
BYOS or pay-as-you-go in the cloud?
Bring-your-own-subscription means you pay Red Hat, Red Hat supports you, and the subscription is portable between environments. Pay-as-you-go means you pay the cloud provider, the provider supports you, and the entitlement is locked to that cloud. There is a documented double-billing trap when moving from PAYG to BYOS: you must cancel the on-demand products with the cloud provider or you will be charged for both.
Does the IBM acquisition change how we buy Red Hat?
Not structurally. Red Hat still runs its own partner programme, its own store and its own part numbers, and the independent reseller channel transacts Red Hat SKUs as before. The one real difference is OpenShift that arrives bundled with an IBM Cloud Pak: most Cloud Paks include a restricted-use OpenShift entitlement usable only for that Cloud Pak’s services, and support routes to IBM rather than Red Hat. Mixing Cloud Pak-bundled and directly purchased OpenShift in one estate creates a genuine entitlement-scope and support-routing problem worth untangling before it becomes an incident.
Is there a sovereign support option?
Yes, and it is newer than most buyers realise. EU Confirmed Sovereign Support variants now exist across RHEL and Ansible at roughly a 25–30% premium over the standard SKUs, with a US equivalent called Confirmed Stateside Support. For regulated buyers this is a material line item that often does not appear in an initial quote — contact us and we will price it in from the start.
What is the RHEL Workstation subscription for?
Developer and engineering desktops. It is licensed per workstation rather than per socket pair, includes one physical entitlement plus one guest entitlement, and is not eligible for ELS.
Pricing and subscription terms verified 18 September 2026 against Red Hat’s published store pricing, subscription guide, support SLA documentation and product pages. Ansible and self-managed OpenShift pricing is quote-only — figures describing those models are directional and should be confirmed with a quote. ReleaseTEAM is a Red Hat partner delivering RHEL, Ansible and OpenShift consulting and implementation.
Most Red Hat estates are mis-sized in at least one place
Standard subscriptions where Virtual Datacenter would be cheaper, per-core OpenShift on dense hosts, Ansible scoped on servers rather than nodes. We find these in a subscription review and quantify them before renewal.
Speak With An Expert