Red Hat Enterprise Linux subscription variants are the different commercial forms in which Red Hat sells Red Hat Enterprise Linux (RHEL). All of them are term-based subscriptions to Subscription Services (software access, maintenance and support); Appendix 1 states that there are no fees associated with the Red Hat Software licenses themselves.[1] The variants reuse a small set of Units, chiefly the Socket-pair, the Virtual Node and the System, and are told apart by their Supported Use Case: the environment and purpose for which Red Hat provides Subscription Services. Appendix 1 requires the subscription type to match the use; its own example is that a RHEL Desktop subscription used on a server obliges the customer to buy a RHEL Server subscription.[1]
Two documents govern the variants. Product Appendix 1 Exhibit 1.A is the binding table of Units, capacities and Use Cases. The RHEL subscription guide explains them for purchasing staff and states that nothing in it supersedes Appendix 1.[2]
Editions
Server variants
| Variant | Unit and capacity (Appendix 1 Exhibit 1.A) | Use Case limits |
|---|---|---|
| RHEL Server | Socket-pair per Physical Node or 2 Virtual Nodes | RHEL Use Case: server computing on Supported Configurations |
| RHEL Server Entry Level | Socket-pair per Physical Node, no Virtual Nodes | Physical only, self-support only, not stackable |
| RHEL for Virtual Datacenters | Socket-pair per Physical Node, unlimited Virtual Nodes | No host operating system entitlement |
| RHEL for SAP Solutions | As RHEL Server | SAP-certified configurations running HANA, S/4HANA or NetWeaver |
| RHEL for Virtual Datacenters for SAP Solutions | As Virtual Datacenters | RHEL and SAP Use Cases |
| RHEL for Third Party Migration | As RHEL Server | Only the Units migrated at original purchase; no add-ons |
| RHEL for Real Time | Socket-pair per Physical Node | Applications certified for the real-time kernel |
| RHEL for Power | Up to 4 processor cores or Socket-pair per Physical or Virtual Node | IBM Power systems |
| RHEL for IBM Z | IBM Z IFL | IBM Z; only cores used by RHEL are entitled |
RHEL for SAP Solutions follows the same Unit as RHEL Server but is supported only on configurations certified by SAP to run SAP HANA, S/4HANA or NetWeaver (rule).[1] The subscription guide lists the extra content bundled with it: the High Availability add-on solutions for SAP, Red Hat Lightspeed, Red Hat Satellite, Extended Update Support, Update Services for SAP Solutions (E4S) and RHEL System Roles for SAP. It is also offered as a cloud marketplace listing on AWS, Azure and Google Cloud.[2]
RHEL for Third Party Migration covers only the number of Units migrated from third-party software at the original purchase and does not support Add-On Subscriptions (rule).[1] The guide describes it as a conversion offer for other RPM-based distributions that can include up to four years of Extended Life Cycle Support. Since 1 April 2025 the Real Time components have been included in RHEL subscriptions generally.[2]
Self-support and Entry Level
Self-support subscriptions include no Red Hat customer support, cannot be stacked, are not intended for production environments and are not for use with Red Hat Cloud Access.[2] RHEL for Server Entry Level goes further: it can be deployed only on physical systems, is available only with self-support, cannot be stacked, and accepts only one add-on, Red Hat Satellite (rule). The guide notes that Entry Level and Self-support are available only in some regions.
Workstation and Desktop
Workstation and Desktop are sold per System, with CPU and memory limits rather than a Socket-pair (rule, rule).[1]
| Variant | Capacity | Use Case |
|---|---|---|
| RHEL Workstation | 2 CPU, unlimited RAM, 1 Physical Node or 4 Virtual Nodes | Personal computing system for a single user at a directly connected keyboard and display; includes one Satellite Module |
| RHEL Desktop | 1 CPU, up to 8GB RAM, 1 Virtual Guest | As Workstation, but excludes open source server applications (Apache, Samba, NFS), testing and development, and sharing data with peers |
Production support for Desktop is limited to Support Contacts who are help desk staff, not end users. The subscription guide lists Workstation uses such as graphics-intensive design and engineering, front-end systems for GPU workloads, VDI in private or public clouds, hosting one or four VMs for single-user use, and application development targeting RHEL or OpenShift; it is available with Premium, Standard and Self-support on x86.[2] The guide also states that a Workstation subscription may not be used as a production server.
High performance computing and academic
The HPC Use Case requires a Cluster used for compute-intensive distributed tasks, with head nodes not exceeding a quarter of the nodes, identical RHEL configuration on compute nodes and at least four Physical Nodes.[1] Red Hat sells HPC Head Node and HPC Compute Node subscriptions; when both are used in the same Cluster, compute nodes inherit the head node’s Service Level (rule). The subscription guide assigns standard RHEL subscriptions to login and storage nodes.[2] The Academic Site Subscription is counted per FTE with a floor of 1,000 FTEs and applies only to accredited institutions’ teaching and learning uses; outside that Use Case, standard RHEL rates apply.[1]
Developer offerings
Appendix 1 separates Development Use from Production Use. For RHEL and the other Exhibit 1.A products, demonstration, individual coding and testing, and multi-user development, test and integration are all Development Use; only deployment activities are Production Use. For OpenShift, middleware, storage, Ansible and Satellite, multi-user development, test and integration is already Production Use (rule).[1] Deployment activities include backup instances, whether cold or hot.
| Offering | Terms |
|---|---|
| Red Hat Developer Subscription for Individuals | No cost; up to 16 physical or virtual nodes; personal use only, not corporate use; development, testing or production; self-supported (rule) |
| RHEL for Business Developers | No cost; 25 physical, virtual or cloud instances per registered user; development and test only (rule) |
| Red Hat Developer Subscription for Teams | No cost; unlimited instances for organizations already running other Red Hat offerings; RHEL and add-ons excluding OpenShift Container Platform; self-supported, Development Use only (rule) |
| RHEL Developer Workstation and Developer Support | Paid; Professional (two business day response) or Enterprise (four Standard Business Hours response); one System (Workstation) or 25 Systems (Developer Support) |
| RHEL Developer Suite | RHEL with development tools, certain add-ons, Real Time and Satellite; Software Maintenance but no Support |
Sources: Appendix 1 sections 2.3 and Exhibit 1.A sections 3 and 4;[1] RHEL subscription guide, developer offerings.[2] Developer Subscriptions carry limited or no support and may not be used for Production Use; using Developer Suite for production obliges the customer to buy the applicable Units. The Enterprise Agreement forbids creating multiple Red Hat accounts to circumvent Unit limits (rule).
Metrics
The variants use these catalog Units: Socket-pair, Virtual Node, Physical Node, System, CPU and GB of RAM as capacity limits for Workstation and Desktop, FTE for academic sites, IBM Z IFL for IBM Z, Peripheral Board for RHEL on ARM-based smart NICs, and System on a Chip for edge devices.
Counting / floors
Add-ons
Add-On Subscriptions are supported only on active Standard or Premium base subscriptions and certain developer offerings (rule).[1] The subscription guide states that all RHEL add-ons except Red Hat Satellite require Standard or Premium, that add-ons follow the same Socket-pair model and portability as RHEL Server, and that an add-on inherits the service level of the RHEL subscription it is attached to.[2] The High Availability Add-On supports clusters of up to 64 nodes; the Resilient Storage Add-On, which includes High Availability and is not supported with RHEL 10, supports up to 16 nodes.
Lifecycle add-ons
Every RHEL subscription includes ten years of support per major release. Extended Update Support (24 months) and Enhanced EUS (48 months) extend a specific minor release; two-year EUS is included at no extra cost in the Premium subscription for x86, and self-support subscriptions are not eligible.[2] Extended Life Cycle Support runs for at least 36 months beyond the ten-year lifecycle, covering the last minor release, and is sold with Premium subscriptions and Standard for IBM Z and x86. Appendix 1 requires EUS (other than RHEL EUS), ELS and ELS Long Life add-ons to be bought for every Unit running the covered version, not for a subset (rule).[1]
Disaster recovery
The subscription guide distinguishes hot, warm and cold DR and requires paid subscriptions for hot DR only (rule). Hot DR systems run concurrently with production and replicate data; warm DR systems are prepared but hold no customer workload and do not replicate; cold DR has infrastructure but not the full technology to restore service. For warm and cold DR, subscriptions are transferred from the primary environment when a disaster occurs.[2] Appendix 1 separately defines a Disaster Recovery Use Case for systems used intermittently, which must have the same Service Levels and configurations as production and excludes active workloads.[1]
Virtualization & partitioning
RHEL for Virtual Datacenters grants unlimited guests per subscribed Socket-pair but no host operating system. The subscription guide adds a pooling condition: when pooling Virtual Datacenters subscriptions, all hosts in a cluster must have uniform SLAs and must all be subscribed, unless the hypervisor can restrict and enforce RHEL workloads to a subset of hosts (rule).[2] The guide’s worksheets present Virtual Datacenters as more cost-effective for dense virtualization and the two-guest Server subscription for low-density environments of four or fewer guests per host. On IBM Z and LinuxONE only the cores used by RHEL need entitlement, whatever partitioning method is used.
Included management and analytics
Every RHEL subscription includes Red Hat Lightspeed, the analytics service formerly called Red Hat Insights, which the subscription guide describes as a management service provided as part of the subscription.[2][3] Systems are registered with Red Hat Subscription Management, accessed from the Customer Portal, which tracks the systems registered to each subscription. Red Hat Satellite is a separately purchased add-on except where a SKU bundles it (see Red Hat Ansible Automation Platform and Satellite managed-node licensing).
Cloud / BYOL
RHEL Server and its add-ons can move between physical, virtual and cloud deployments without changing terms, but self-support subscriptions are not eligible for Cloud Access, and unaffiliated RHEL Server subscriptions need Red Hat’s permission to move off-site or to a cloud. RHEL Server is also sold as a cloud marketplace offering on AWS and Azure.[2] See Red Hat Cloud Access and pay-as-you-go cloud subscriptions.
Programs
RHEL variants are bought under the Red Hat Enterprise Agreement and Product Appendix 1 (see Red Hat Enterprise Agreement, Appendix 1 terms and support levels).
Out of scope
- RHEL AI and Red Hat AI Inference, which use AI Accelerator Units.
- Red Hat OpenStack Platform and Red Hat Virtualization, which share Exhibit 1.A but are not RHEL variants.
- Edge offerings (RHEL for Distributed Computing, Red Hat Device Edge) beyond the SoC Unit.
- List prices and regional availability of individual SKUs.