SUSE Linux Enterprise and Rancher Prime subscriptions

SUSE Linux Enterprise and Rancher Prime subscriptions are sold by SUSE as a Subscription, which the SUSE Subscription Terms define as “a time-bound right to receive Technical Support Services, Updates and Upgrades for a SUSE Product”.^[1] The software itself is licensed under the EULA and the open source licenses of its components; the commercial count is the number of Units, where a Unit is “a single increment of the metric identified under the ‘Unit of Measure’ column” of the Product Appendices.^[1] For SUSE Linux Enterprise Server (SLES) the Units are socket-pair and virtual-machine bands; for SUSE Rancher Prime they are Cores and vCPUs or Sockets and Cores; for SUSE AI they are Accelerators.^[2] This article covers the July 2026 Subscription Terms and the June 2026 Product Appendices. The model is close to, but not the same as, the Red Hat Socket-pair model; both are forms of subscription licensing.

Editions

The Product Appendices open with a Matrix of SUSE Products that lists each SUSE Offering, its Unit of Measure, whether it is Stackable, and the appendix with the detailed rules.^[2] The families that matter most for an effective license position are:

Some Matrix rows carry former names in brackets (for example SUSE Security, formerly NeuVector); the renaming does not change entitlements already bought under the old name.^[2] SLES with Expanded Support and SUSE Multi-Linux Support (formerly SUSE Liberty Linux) use the same Units as the matching SLES Subscription.^[2] The SUSE Shop sells SLES configurations by environment and processor type, with Standard support at 12x5 hours of access, in 1, 3 and 5 year terms.^[4] Starting 1 July 2021, the Live Patching variants replaced the plain 1-2 Sockets with Unlimited Virtual Machines Subscriptions for SLES and SLES for SAP on x86-64 and Power. Subscriptions bought before that date are unaffected.^[2]

Metrics

The catalog rows keep SUSE’s own names for its Units. The table points to each row and does not restate the definition.

A Physical Server is one physical computer system “regardless of whether the physical computer system has been partitioned by software”, so software partitioning does not create extra servers for counting.^[1] Apart from Arm AArch64 Subscriptions, Units do not distinguish single-core, multi-core or simultaneous multi-threading processors.^[2]

Counting / floors

Coverage requirement (Subscription Terms, July 2026). You must buy enough Subscriptions in the applicable Units to cover every installation and deployment of a SUSE Product, including variants and components. All products with “SUSE Linux Enterprise” or “SLE” in the name count as one product: owning SLES means every SLES for SAP deployment must also be covered, and vice versa. Paying a renewal is deemed a statement of the number of Units deployed.^[1] Rule: Coverage requirement: every installation and deployment; SLE products counted as one.

Over-deployment. Units deployed above those paid for must be reported, and ordered within 30 days of first installation.^[1] Rule: Over-deployment: report and order within 30 days.

No mixing. A Subscription applies only to the exact product and platform bought. x86 benefits cannot be used for the zSystem version, SLES benefits cannot be used for SLES for SAP Applications, and 1-2 Virtual Machine and Unlimited Virtual Machine Subscriptions cannot be mixed on one Physical Server.^[1] Rule: No mixing: exact product, platform and VM subscription type per Physical Server.

Physical servers (Product Appendices, June 2026). A 1-2 Socket server needs one Subscription. Larger servers stack Subscriptions to match or exceed the Socket count, so four Sockets need two. A Subscription cannot cover one Socket on one server and one Socket on another. Odd Socket counts round up: three Sockets need two Subscriptions.^[2] Rule: Physical Servers: 1-2 Socket Subscriptions stack and cannot be split across servers.

IBM z Systems. Subscriptions must match or exceed the number of IFLs running SLES. An unlimited number of SLES instances may run per IFL, and SLE High Availability is included.^[2] Rule: IBM z Systems and LinuxONE: per IFL, unlimited instances per IFL.

Arm AArch64. Servers with 16 or more Cores are counted in 1-2 Socket Subscriptions, capped at 144 Cores per Socket Pair. Below 16 Cores the count is Cores divided by four, rounded up.^[2] Rule: Arm AArch64: 1-2 Sockets at 16+ Cores, groups of 4 Cores below 16.

SUSE Linux Micro. One “1-16 vCores” Subscription per 16 Virtual Cores exposed to the OS, stacked above that (48 Virtual Cores need three). On a SUSE certified cloud provider, each VM needs one Subscription and may have at most 16 Virtual Cores.^[2] Rule: SUSE Linux Micro: 1-16 Virtual Cores, one Subscription per cloud VM.

SUSE Rancher Prime. Rancher Prime is priced per Unit. On Virtualized Deployments the Unit counts Cores and vCPUs and stacks above 2 Cores or 4 vCPUs. On Bare Metal Deployments it counts Sockets and Cores and stacks above 2 Sockets or 64 Cores. Every Core, vCPU or Socket that runs a Managed Instance needs its own Subscription or a bundled one.^[2] Rule: SUSE Rancher Prime: per Unit of Cores/vCPUs or Sockets/Cores for every Managed Instance.

Rancher Prime add-ons. SUSE Security (formerly NeuVector), SUSE Storage (formerly Longhorn), SUSE Virtualization (formerly Harvester), SUSE Observability Platform Optimization and SUSE Private Registry are add-ons. Each needs an add-on Subscription for every SUSE Rancher Prime Subscription you hold, so an add-on cannot cover only part of the Rancher Prime estate.^[2] Rule: Rancher Prime add-ons (SUSE Security, formerly NeuVector, and others): one per Rancher Prime Subscription.

SUSE AI. One Subscription per Accelerator in infrastructure covered by a Platform Subscription, whether or not the Accelerator is running AI workloads. An Accelerator used only for non-AI work can be exempted if the customer proves this to SUSE’s reasonable satisfaction.^[2] Rule: SUSE AI: one Subscription per Accelerator in covered infrastructure.

Virtualization & partitioning

SLES offers two virtualization models (see also virtualization and partitioning):

• Low density. One “1-2 Sockets or 1-2 Virtual Machines” Subscription covers up to 2 VMs on the same Virtualization Host or Virtualization Environment, or in the same Private Cloud account or Public Cloud zone. At any time it is used either on a Physical Server or as VMs, never as one Socket plus one VM, and it may not be used as a Virtualization Host.^[2] Rule: Low-density virtualization: 2 VMs per 1-2 Sockets or 1-2 VMs Subscription.
• High density. A “1-2 Sockets with Unlimited Virtual Machines” Subscription allows unlimited VMs per 1-2 Sockets on a host, stacks for larger hosts, and includes the right to run SUSE Linux Enterprise KVM or Xen as the host. It must be bought for each Virtualization Host capable of running SUSE Products in the Virtualization Environment. Only subscribed Physical Servers may be part of that environment, “irrespective of whether such Physical Server is actually used or for how long”.^[2] Rule: High-density virtualization: Unlimited VMs per 1-2 Sockets on every capable host.

Changing deployment type. When the deployment type changes during the term, the highest valued Subscription must be used. A higher valued Unlimited Virtual Machines Subscription may cover a lower valued 1-2 VM scenario, but not the reverse.^[2] Rule: Changing deployment type mid-term: use the highest valued Subscription.

SAP on KVM. Every KVM host that runs SAP workloads in a customer-owned or dedicated managed environment needs SLES for SAP Applications, 1-2 Sockets with Unlimited Virtual Machines. Plain SLES may not be used for SAP workloads on KVM, and “1 Virtual Machine” Subscriptions may not be used for SAP at all.^[2] Rule: SAP workloads on KVM hosts require SLES for SAP 1-2 Sockets with Unlimited VMs.

IBM Power Sub-Capacity. On POWER8 or later servers with four or more Sockets, where PowerVM limits the capacity available, SUSE allows Subscriptions for a subset of Sockets. The count is a Socket Pair Equivalent: whole Cores available to the Subscription divided by Cores per Socket Pair on that server, with fractional Cores and Socket Pairs rounded up. SUSE’s example is 40 Cores on a server with 10 Cores per Socket, which gives 2 Socket Pair Equivalents.^[2] Rule: IBM Power Sub-Capacity: Socket Pair Equivalent with rounding up.

Mobility. Subscriptions can move to new or different Physical Servers. In SUSE’s example, ten 2-Socket servers replaced by four 4-Socket servers use 8 of the 10 Subscriptions and leave 2 for later.^[2] Rule: Subscriptions transfer to new or different Physical Servers.

Cloud / BYOL

SUSE’s cloud portability program is Bring Your Own Subscription (BYOS), SUSE’s version of cloud BYOL. SUSE Products may run in SUSE-certified Public Clouds listed on SUSE’s Eligible Public Clouds page, and on-premises Subscriptions may be transferred there. The Subscription must first be registered in the SUSE Customer Center (SCC), and the customer consents to the cloud vendor reporting usage to SUSE.^[1] SUSE’s BYOS page names AWS, Azure and Google Cloud.^[3] “Physical only, 1-2 Sockets” and “1 Virtual Machine” Subscriptions are not eligible. An Unlimited Virtual Machines Subscription can be moved to an authorized cloud provider only as 1 or 2 VMs.^[2] Rule: BYOS to Eligible Public Clouds: register in SCC and consent to reporting.

SUSE may remove a cloud vendor from the eligible list on sixty days’ written notice. Subscriptions already transferred there continue for the notice period or the rest of their term, whichever is shorter, and may move to another eligible cloud or back on premises.^[1] Rule: Removal of an Eligible Public Cloud vendor on 60 days notice. On Google Compute Engine, Google’s own documentation says SLES BYOS does not require sole-tenant nodes.^[5]

Purchases on the AWS, Microsoft Azure, Google Cloud or Oracle marketplaces fall under the Marketplace Terms in Appendix 1 of the Subscription Terms. Google and Oracle marketplace purchases are contracted with SUSE LLC.^[1]

Programs

• SUSE Subscription (SUSE Subscription). The Transaction Document sets a fixed term. Subscriptions renew automatically for the same length unless either party gives notice at least 90 days before renewal. Renewal fees use the then-current price list less the original percentage discount.^[1] Rule: Automatic renewal unless 90 days notice; renewal priced from then-current list.
• Bring Your Own Subscription (Bring Your Own Subscription (BYOS)). See Cloud / BYOL.
• Marketplace Terms (Marketplace Terms (Appendix 1)). Appendix 1 to the Subscription Terms.
• Integrated Use (Integrated Use). Available only where the Transaction Document grants it. The Integrated Solution must add a material value-added application, restrict users from accessing the SUSE Product, and appear as a single invoice line item.^[1]

Usage restrictions apply across all programs. Subscriptions are for internal use on infrastructure the customer owns, leases or has managed on its behalf. Outsourced IT providers may use them only to serve the customer.^[1] Rule: Internal Use only; outsourced IT providers permitted. Evaluation Subscriptions last 60 days and Developer Subscriptions one year, and neither may be used in production.^[1] Rule: Evaluation (60 days) and Developer (1 year) Subscriptions: no production use. Records must be kept for two years after the term. A verification shortfall is bought at full list price without discount plus 8% annual interest, and a shortfall of 5% or more also means paying SUSE’s reasonable verification costs.^[1] Rule: Verification: 2-year records; shortfall at full list price plus 8% interest.

Out of scope

• SUSE Shop list prices. The shop shows geolocated prices by configuration and term; this article does not tabulate them.^[4]
• SUSE part numbers. The Product Appendices name Offerings but publish no part numbers, so catalog SKU rows carry Offering names only.
• SLE extensions (High Availability, Geo Clustering, Live Patching as a separate product), Long Term Service Pack Support, SLE Point of Service, SUSE Multi-Linux Manager, SLE Desktop, SLE HPC, SUSE Edge and SUSE Cloud Native Edge beyond the Units named above. See Appendices B to K of the Product Appendices.^[2]
• SUSE SaaS offerings (SUSE SaaS Addendum), third-party software under the Vendor Software Addendum, and professional services.
• Technical Support Handbook service levels beyond the Standard tier shown in the shop.

Catalog rows

Catalog rows for this article, grouped by table.

• Metrics
  • 1-2 Sockets or 1-2 Virtual Machines
  • 1-2 Sockets with Unlimited Virtual Machines
  • Physical only, 1-2 Sockets
  • 1 Virtual Machine
  • Socket Pair
  • Socket Pair Equivalent
  • IFL
  • Group of 4 Cores (Arm AArch64)
  • 1-16 Virtual Cores
  • Cores and vCPUs (SUSE Rancher Prime, Virtualized Deployment)
  • Sockets and Cores (SUSE Rancher Prime, Bare Metal Deployment)
  • Accelerator
  • Authorized User
  • Physical Server
  • Instance
  • Edge Cluster
• Programs
  • SUSE Subscription
  • Bring Your Own Subscription (BYOS)
  • Marketplace Terms (Appendix 1)
  • Integrated Use
• Rules
  • Coverage requirement: every installation and deployment; SLE products counted as one
  • Over-deployment: report and order within 30 days
  • No mixing: exact product, platform and VM subscription type per Physical Server
  • Physical Servers: 1-2 Socket Subscriptions stack and cannot be split across servers
  • Low-density virtualization: 2 VMs per 1-2 Sockets or 1-2 VMs Subscription
  • High-density virtualization: Unlimited VMs per 1-2 Sockets on every capable host
  • Changing deployment type mid-term: use the highest valued Subscription
  • Subscriptions transfer to new or different Physical Servers
  • BYOS to Eligible Public Clouds: register in SCC and consent to reporting
  • Removal of an Eligible Public Cloud vendor on 60 days notice
  • SAP workloads on KVM hosts require SLES for SAP 1-2 Sockets with Unlimited VMs
  • IBM Power Sub-Capacity: Socket Pair Equivalent with rounding up
  • IBM z Systems and LinuxONE: per IFL, unlimited instances per IFL
  • Arm AArch64: 1-2 Sockets at 16+ Cores, groups of 4 Cores below 16
  • SUSE Linux Micro: 1-16 Virtual Cores, one Subscription per cloud VM
  • SUSE Rancher Prime: per Unit of Cores/vCPUs or Sockets/Cores for every Managed Instance
  • Rancher Prime add-ons (SUSE Security, formerly NeuVector, and others): one per Rancher Prime Subscription
  • SUSE AI: one Subscription per Accelerator in covered infrastructure
  • Internal Use only; outsourced IT providers permitted
  • Evaluation (60 days) and Developer (1 year) Subscriptions: no production use
  • Verification: 2-year records; shortfall at full list price plus 8% interest
  • Automatic renewal unless 90 days notice; renewal priced from then-current list
• Evidence (sample)
  • Coverage requirement for SUSE Products (§6.1)
  • No Mixing of Subscriptions (§6.3)
  • Physical Server Subscriptions cannot be split (Appendix A §4)
  • Up to 2 VMs per Subscription (Appendix A §5(a))
  • Every capable Virtualization Host must be licensed (Appendix A §6)
  • SLES for SAP required on KVM hosts running SAP (Appendix A §6(a))
  • Socket Pair Equivalent calculation and rounding (Appendix A §9)
  • Rancher Prime Units and stacking (Appendix M §1)
  • SUSE Security (formerly NeuVector) Add-On (Appendix M §4)
  • Accelerator count regardless of active AI use (Appendix O)
  • BYOS policy and SCC registration (§8.1)
  • Verification results (§17.3)
• Sources
  • SUSE Subscription Terms (July 2026)
  • SUSE Product Appendices for SUSE Offerings (June 2026)
  • SUSE public cloud Bring Your Own Subscription page
  • SUSE Shop: SUSE Linux Enterprise Server