RHEL Server Is a Socket-Pair. VDC Covers Guests.
Red Hat does not sell perpetual licenses for Red Hat Enterprise Linux (RHEL). You buy a time-bound subscription for each Unit you run. For RHEL Server the Unit is a physical node counted in socket-pairs (up to two occupied CPU sockets on one machine) or a pair of virtual nodes. RHEL for Virtual Datacenters (VDC) is bought per socket-pair of the hypervisor host and covers unlimited RHEL guests on it. Self-support, Standard and Premium change the support you get, not what you count. At Red Hat’s US online list prices (one year, checked October 2026), RHEL Server Standard is $878.90, Premium $1,428.90, and VDC Standard $3,023.79 per host socket-pair. On a single two-socket host, VDC is cheaper than per-VM subscriptions from seven RHEL guests.
This page covers how paid subscriptions are counted and priced. For RHEL you can run at no cost, see Red Hat’s no-cost RHEL for businesses and developers. To check whether a given host is registered and covered, see how to check if your Red Hat server is licensed. For other distributions, see paid and free alternatives to Red Hat Enterprise Linux.
What a Red Hat subscription actually is
Red Hat’s Product Appendix 1 (February 2026 version, section 1.4) separates two things. The software is governed by perpetual end-user and open source licenses. The Subscription Services (access to Red Hat’s portals, software maintenance, support) are term-based and expire unless you renew. The subscription guide adds that every RHEL subscription includes Red Hat Lightspeed, formerly Insights. The appendix defines a Subscription as “a time bound Red Hat Product offering”. The fees pay for the services, not for the code.
The coverage rule is in section 1.2. While you hold a subscription for a product, you must buy subscriptions “in a quantity equal to the total number and capacity of Units” from the day you start using it. Section 1.2(g) lists what Red Hat calls unauthorized use, including buying or renewing for fewer Units than you run, and splitting one Unit’s subscription across two or more Units. A subscription starts on the earlier of the purchase date and first use (section 1.3).
Those rules apply to every architecture. Most of this page is about x86 and ARM, where RHEL is counted in socket-pairs and virtual nodes. IBM Z, IBM Power and OpenShift use other Units, covered below.
Glossary: socket-pair, stacking, virtual node
Use Red Hat’s definitions, from Appendix 1 Table 1.1 and the RHEL subscription guide (dated 21 July 2026):
| Term | Meaning |
|---|---|
| Socket | A socket occupied by a CPU. |
| Socket-pair | Up to two occupied sockets on one system. Two servers with one socket each are entitled separately: two subscriptions. |
| Stacking | Combining subscriptions to cover a larger machine. A 4-socket server needs two, an 8-socket server four. |
| Physical node | A physical system running the software: server, blade, workstation, laptop. |
| Virtual node (virtual guest) | An instance of the software running, in whole or in part, in a virtual machine or a container. |
| Core | A physical core in a CPU, or a virtual core in a VM or supporting a container. The Unit for IBM Z, Power and core-based OpenShift, not for RHEL Server on x86. |
The common mistake is reading “one subscription covers two sockets” as two one-socket servers sharing a subscription. They cannot. The guide’s sample worksheet makes the point: 10 one-socket servers need 10 subscriptions, not 5.
RHEL Server: one socket-pair, or two virtual nodes
Appendix 1, Exhibit 1.A Table 1, measures Red Hat Enterprise Linux Server (Physical or Virtual Nodes) as a socket-pair for each physical node, or two virtual nodes. The subscription guide adds that the two virtual nodes count “regardless of virtual sockets”. A VM with eight vCPUs is one virtual node. Cores and memory do not enter the count.
The same subscription moves between the two forms. The guide says you may convert a physical two-socket subscription to two virtual instances, and back, without notifying Red Hat. Note 2 to the same table lets virtual-guest subscriptions pool across any system with a subscription of the same service level and guest count. Per-VM subscriptions follow the VM. They are not tied to the host it runs on.
| What you run | RHEL Server subscriptions |
|---|---|
| One 1-socket physical server | 1 (it cannot share with another 1-socket server) |
| One 2-socket physical server | 1 |
| One 4-socket physical server | 2 (stacked) |
| One 8-socket physical server | 4 (stacked) |
| 20 RHEL virtual machines, any size | 10 |
| 7 RHEL virtual machines | 4 (a subscription covers two nodes and cannot be split) |
| 20 RHEL instances in a public cloud, bring your own subscription | 10 |
The guide’s first worksheet adds up a mixed physical estate: 10 one-socket, 10 two-socket, 2 four-socket and 2 eight-socket servers need 10 + 10 + 4 + 8 = 32 subscriptions.
VDC: unlimited guests on the host socket-pair
Red Hat Enterprise Linux for Virtual Datacenters is a physical-node subscription. Its capacity is “Unlimited Virtual Nodes running on a Socket-pair” (Appendix 1, Exhibit 1.A Table 1). You count hypervisor socket-pairs, not guests. The conditions that decide whether it fits:
- Bought for the host, stacked like Server. A 2-socket host needs one VDC subscription, a 4-socket host two.
- Supported hypervisors only. The guide names Red Hat Virtualization, VMware and Microsoft Hyper-V; the store page names OpenShift Virtualization, VMware and Microsoft Hyper-V.
- No host operating system. Note 1 to Table 1: VDC does not include an entitlement for the host operating system. If the hypervisor runs on RHEL, the host needs its own subscription.
- The whole cluster. All hosts in a cluster must be covered, with the same service level on each. You may cover a subset only if the hypervisor can restrict RHEL workloads to it (guide, cluster pooling).
- Add-ons per host. Add-ons bought for a VDC host are priced per host socket-pair. The store lists High Availability at $1,506.45 for VDC against $438.90 for Server.
Section 1.2(d) of Appendix 1 adds one more rule: you buy the highest service level you use. If one node in a cluster needs Premium, every node in that cluster needs Premium.
Per-VM or VDC: worked examples at list price
These examples use Red Hat’s US online store prices for one-year subscriptions, checked October 2026: RHEL Server Standard $878.90 and Premium $1,428.90; RHEL for Virtual Datacenters Standard $3,023.79 and Premium $4,838.79. A quote under an Enterprise Agreement or through a partner sets your own price. The break-even comes from the ratio between the two prices, so check it against your quote.
One 2-socket VMware host, Standard support
| RHEL guests on the host | Server subscriptions (2 guests each) | Per-VM cost | VDC cost (1 socket-pair) | Cheaper |
|---|---|---|---|---|
| 2 | 1 | $878.90 | $3,023.79 | Per-VM |
| 4 | 2 | $1,757.80 | $3,023.79 | Per-VM |
| 6 | 3 | $2,636.70 | $3,023.79 | Per-VM |
| 7 | 4 | $3,515.60 | $3,023.79 | VDC |
| 10 | 5 | $4,394.50 | $3,023.79 | VDC |
| 20 | 10 | $8,789.00 | $3,023.79 | VDC |
Premium gives the same break-even. Six guests cost $4,286.70 per-VM against $4,838.79 for VDC Premium, and seven or eight cost $5,715.60. On a 4-socket host VDC takes two subscriptions ($6,047.58 Standard), and per-VM stays cheaper up to 12 guests.
A 4-host cluster where VMs move
Take four 2-socket hosts in one vSphere cluster with DRS moving VMs between them, and 20 RHEL VMs spread across the cluster. VDC has to cover every host: 4 × $3,023.79 = $12,095.16. Per-VM subscriptions follow the VMs: 10 × $878.90 = $8,789.00. Per-VM wins, although 20 guests on one host would favour VDC.
At 40 RHEL VMs the order flips: per-VM costs $17,578.00 against the same $12,095.16. In this cluster the crossover sits at 27 VMs (14 subscriptions, $12,304.60). Below that, you have two ways to make VDC pay: concentrate RHEL on fewer hosts and restrict it there with hypervisor rules, or keep per-VM.
Mixed estates are normal
Nothing requires one model for the whole estate. A dense production cluster on VDC, a few RHEL VMs on a mostly Windows cluster on per-VM Server subscriptions, and physical database servers on socket-pair Server subscriptions can sit in one account. What has to hold is that each Unit is covered once, at the service level it uses.
Self-support, Standard, Premium: an SLA, not a metric
The Unit stays the same at every support level. What changes is the support. Red Hat’s production support terms:
| Self-support | Standard | Premium | |
|---|---|---|---|
| Hours | None | Standard business hours | Standard business hours, 24x7 for Severity 1 and 2 |
| Channel | None | Web and phone | Web and phone |
| Cases | None | Unlimited | Unlimited |
| Severity 1 initial response | None | 1 business hour | 1 hour |
| Severity 2 initial response | None | 4 business hours | 2 hours |
| Severity 3 initial response | None | 1 business day | 4 business hours |
| Severity 4 initial response | None | 2 business days | 8 business hours |
| RHEL Server list price, 1 year | $383.90 | $878.90 | $1,428.90 |
Self-support is more restricted than the price suggests. The subscription guide says self-support subscriptions include no Red Hat customer support, cannot be stacked, are not intended for production and cannot be used with Cloud Access. The store sells RHEL Server Self-support for physical systems only. Most add-ons need Standard or Premium.
You may buy different levels for different systems. You may not use one level’s support for a system covered at another (guide). Premium on x86 also includes Extended Update Support, covered in the next section.
Add-ons follow the same socket-pair
The guide says add-ons follow the socket-pair model of RHEL Server and can move between physical and virtual systems the same way. Appendix 1, Table 1.2(b), supports add-ons only on active Standard or Premium base subscriptions. The guide makes Satellite the exception: it is the one add-on available with Self-support. Add-ons take the service level of the RHEL subscription they sit on.
| Add-on | What it does | Store price with Server Standard, 1 year |
|---|---|---|
| High Availability | Failover clustering, up to 64 nodes | $438.90 |
| Resilient Storage | Shared block storage for clusters up to 16 nodes; includes High Availability; not supported with RHEL 10 | $878.90 |
| Extended Update Support (EUS) | Two more years of updates on a minor release; included with x86 Premium | $273.90 |
| Enhanced EUS | Two further years, RHEL 9 and later | Not listed |
| Extended Life Cycle Support (ELS) | At least 36 months beyond the 10-year life cycle for a major release’s last minor; not with Self-support | Not listed |
| Red Hat Satellite | Management and content delivery; one entitlement for each RHEL Unit it manages | $1,263.90 as a bundle with Server Standard |
For EUS, ELS and ELS Long Life on the versions they cover, Appendix 1 section 2.6 has the same counting rule as the base product: every Unit running those versions. The appendix excludes RHEL EUS from that clause. Satellite, per Exhibit 1.D, needs an entitlement for each RHEL Unit managed by Satellite, Capsule or Satellite Proxy.
The update add-ons are being consolidated. Red Hat’s RHEL life cycle page says RHEL Standard gives 6 months per minor release, and Premium gives 2 years for eligible minor releases. From RHEL 9, Extended Life Cycle Premium (ELCP), an add-on to Premium, replaces EUS, Enhanced EUS and E4S. It gives 6 years from general availability for even-numbered minor releases from 9.2. Long-Life (LL) add-ons extend that a year at a time. ELCP replaces ELS starting with RHEL 8.10 on 1 June 2029. Existing EUS, Enhanced EUS, E4S and ELS contracts on older releases continue through their committed end dates (legacy page).
Where the Unit is not a socket-pair
| Product | Unit and capacity (Appendix 1 unless noted) |
|---|---|
| RHEL Workstation | Per system: 2 CPUs, one physical node or 4 virtual nodes; single-user personal computing only |
| RHEL Desktop | Per system: 1 CPU, up to 8 GB RAM, 1 virtual guest; not for server applications |
| RHEL for IBM Z | Per IFL; the guide: only the cores RHEL uses, however the machine is partitioned |
| RHEL for Power | Up to 4 processor cores or a socket-pair, physical or virtual |
| RHEL for Distributed Computing, Endpoint | A single socket per physical node, or 2 virtual nodes; edge devices only |
| Red Hat OpenStack Platform | Host socket-pair, unlimited guests included |
| OpenShift (core-based) | 2 cores or 4 vCPUs; the OpenShift subscription guide excludes control plane nodes from the count |
A server running RHEL Desktop or Workstation still needs RHEL Server. Appendix 1 uses that as its example of buying the subscription that matches the use case. The OpenShift guide adds that OpenShift Container Platform and Platform Plus include RHEL guest entitlements for VMs on OpenShift Virtualization, and OpenShift Virtualization Engine does not.
Public cloud: on-demand or Cloud Access
RHEL in AWS, Azure, Google Cloud and other certified clouds can be bought two ways. Red Hat’s comparison of Cloud Access and on-demand subscriptions:
| On-demand (pay as you go) | Cloud Access (bring your own subscription) | |
|---|---|---|
| Who bills | The cloud provider, in the instance price | Red Hat for the subscription, the provider for compute |
| First-line support | The cloud provider | Red Hat |
| Counting | Pay as you go, in the provider’s instance price | Your subscriptions: 2 instances per RHEL Server subscription (guide worksheet) |
| Terms and price | The provider’s | Your Red Hat terms and pricing are unchanged |
Under Appendix 1 section 3, Cloud Access needs eligible subscriptions, and excludes subscriptions whose Units are solely based on physical attributes; the guide adds that Self-support subscriptions are not for Cloud Access. Moving a subscription to the cloud keeps its start date and term, and the cloud provider reports your usage to Red Hat. When you move an instance from on-demand to Cloud Access, cancel the on-demand product with the provider, or you pay twice.
Term, renewal and true-up under the Enterprise Agreement
The Red Hat Enterprise Agreement (North America web version, listed on Red Hat’s agreements page) sets the commercial rules around the appendix:
- Term and auto-renewal (2.2). A service starts at the earliest of first use, purchase date or the order’s start date. Subscriptions renew automatically for the same duration unless either party gives notice at least 30 days before expiry. The subscription guide says Red Hat sends reminders at 90, 60 and 30 days.
- Reporting growth (3.2). If you deploy more Units than you paid for during the term, you report the additional Units and the dates you deployed them to Red Hat or your partner, and pay for them. The general terms set no annual true-up date. The obligation runs from the day you deploy.
- Review (10). During the agreement and for one year after, Red Hat may inspect your facilities and records to verify compliance, with at least 10 days’ notice for on-site visits. You resolve an underpayment within 15 days of notice, and if it exceeds 5% you also pay for the inspection.
Appendix 1 section 1.2(e) lets you reallocate subscriptions between affiliates under the same agreement, provided you report and pay for any additional Units.
Simple Content Access changed attach. It did not change the metric.
Under Simple Content Access (SCA), you no longer attach a subscription to a host. A registered system gets content whatever its subscription status. New accounts defaulted to SCA from 15 July 2022, enabling it became one-way in April 2024, and by November 2024 all accounts without specific exceptions had moved. The transition article records that RHSM entitlement management was discontinued on 30 October 2025, with Satellite 6.15 the last release that supports entitlement mode.
What SCA removed is the technical check. The same article says Red Hat “does require you to maintain the correct quantities and types of subscriptions for your deployments”. A host that updates is not proof that it is covered. That makes your own count the only control. The subscriptions service in the Hybrid Cloud Console gives the usage view, and it needs virt-who host-to-guest mapping to report VDC correctly. Checking an individual host is covered in how to check if your Red Hat server is licensed.
No-cost and developer subscriptions are not the estate
The guide lists three no-cost offerings, all self-supported. The Developer Subscription for Individuals is personal use, up to 16 nodes. RHEL for Business Developers allows up to 25 instances per registered user, for development and test. The Developer Subscription for Teams has unlimited instances for development and test, through Red Hat or a partner. Keep them out of the production count. The details are in no-cost RHEL for businesses.
Appendix 1 Table 1.2(c) treats RHEL development and test, including multi-user test and integration, as Development Use. Deployment activities are Production Use, and a production deployment needs a paid subscription.
How to count your estate
- List every RHEL instance: physical servers, VMs with their current host and cluster, cloud instances marked on-demand or Cloud Access, containers on RHEL hosts. Mark developer and no-cost subscriptions separately.
- For physical servers, count occupied sockets per machine and round up to socket-pairs. Never pair sockets across machines.
- For each hypervisor cluster, count RHEL guests and host socket-pairs. Price per-VM (guests divided by two, rounded up) against VDC (every host in the cluster, or a subset the hypervisor enforces).
- Assign the service level each system actually uses, and apply the cluster rule for Premium.
- Add the add-ons on the same Units: High Availability, Resilient Storage, EUS or ELCP, ELS, Satellite.
- Compare the result with the quantities, levels and end dates in your subscription inventory, and report any excess as the Enterprise Agreement requires.
LICENSEWARE’s Red Hat Deployment Manager does this from your inventory data, applying the physical, per-VM and VDC rules and showing the cheapest compliant cover per host.
Questions
How much does a RHEL license cost?
RHEL is sold as an annual subscription, not a license. Red Hat’s US store lists RHEL Server at $383.90 Self-support, $878.90 Standard and $1,428.90 Premium per year, each for a 2-socket server or 2 VMs. VDC is $3,023.79 Standard or $4,838.79 Premium per host socket-pair. Quoted prices differ.
What are the RHEL license types?
For servers: RHEL Server (physical socket-pair or two virtual nodes), RHEL for Virtual Datacenters (unlimited guests per host socket-pair), and variants such as RHEL for SAP Solutions, HPC and edge. For desktops: Workstation and Desktop. Each comes at a support level, plus optional add-ons.
Can two one-socket servers share one subscription?
No. A socket-pair is up to two sockets on one system. Each one-socket server needs its own subscription.
Do cores or vCPUs matter for RHEL Server?
Not on x86 or ARM. Physical servers count occupied sockets, and VMs count as virtual nodes regardless of virtual sockets. Cores matter for IBM Z, IBM Power and core-based OpenShift.
When is VDC cheaper than per-VM subscriptions?
At list price, from seven RHEL guests on a 2-socket host, Standard or Premium. In a cluster, divide by every host VDC has to cover, not only the hosts where RHEL runs today.
Does VDC cover the hypervisor host itself?
No. VDC does not include the host operating system. A RHEL-based hypervisor host needs its own subscription.
What is the difference between RHEL Standard and Premium?
Support hours and response times. Standard is business hours with a one-business-hour Severity 1 response. Premium adds 24x7 for Severity 1 and 2 with a one-hour Severity 1 response, and includes EUS on x86. The Unit is the same.
With Simple Content Access, do I still need subscriptions?
Yes. SCA removed attaching subscriptions to hosts, not the obligation to buy one for every Unit you run.
Is there an annual true-up for Red Hat?
Not in the Enterprise Agreement’s general terms. You report additional Units, with their deployment dates, when they exceed what you paid for, and Red Hat invoices them. Your order form may add its own terms.
Is RHEL free?
The source code is open, and several no-cost subscriptions exist for individuals, developers and teams. Production use in an organization needs a paid subscription. See no-cost RHEL for businesses for the limits.
Sources
- Red Hat Enterprise Linux subscription guide (21 July 2026: socket-pair, stacking, virtual nodes, portability, VDC rules, support levels, add-ons, Self-support limits, worksheets, IBM Z, developer offerings, renewal reminders): https://www.redhat.com/en/resources/red-hat-enterprise-linux-subscription-guide
- Product Appendix 1, Software and Support Subscriptions, North America English (February 2026: Unit definitions, sections 1.2 to 1.4, 2.6 and 3, Exhibit 1.A Table 1 and Notes 1 and 2, Exhibit 1.B OpenShift, Exhibit 1.D Satellite): https://www.redhat.com/licenses/Appendix-1-NA-English-20260218.pdf
- Red Hat Enterprise Agreement, North America web version (sections 2.2, 3.2 and 10): https://www.redhat.com/licenses/Enterprise_Agreement_Webversion_NA_English_20211109.pdf
- Red Hat Enterprise Agreements index: https://www.redhat.com/en/about/enterprise-agreements
- Red Hat store, RHEL Server (list prices and add-ons, checked October 2026): https://www.redhat.com/en/store/red-hat-enterprise-linux-server
- Red Hat store, RHEL for Virtual Datacenters (list prices, add-ons, hypervisors, checked October 2026): https://www.redhat.com/en/store/red-hat-enterprise-linux-virtual-datacenters
- Production support terms of service (SLA by level): https://access.redhat.com/support/offerings/production/sla
- RHEL life cycle (Standard and Premium minor-release coverage, ELCP, Long-Life): https://access.redhat.com/support/policy/updates/errata
- Legacy extended support offerings: https://access.redhat.com/support/policy/updates/errata_legacy
- Cloud Access versus on-demand subscriptions: https://access.redhat.com/articles/2041283
- Simple Content Access: https://access.redhat.com/articles/simple-content-access
- Transition of subscription services to the Hybrid Cloud Console: https://access.redhat.com/articles/transition_of_subscription_services_to_the_hybrid_cloud_console
- Self-managed Red Hat OpenShift subscription guide (January 2026): https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide
