System and resource scope
Inventory physical machines, sockets and cores, virtual machines and vCPUs, cloud instances, Kubernetes clusters and managed systems. The relevant unit depends on the selected SUSE offering.
SUSE subscriptions
SUSE Linux licensing
Plan SUSE Linux and Kubernetes subscriptions from the systems, cores, sockets, virtual resources, support scope and management services actually required.
Request a licensing quoteRequirementMetricTermLifecycleSUSE Linux
Licensing overview
Map the requirement before comparing offers.
SUSE offerings cover enterprise Linux, SAP-focused Linux environments, Kubernetes management and mixed-Linux operations. Common current product names include SUSE Linux Enterprise Server (SLES), SUSE Linux Enterprise Server for SAP applications, SUSE Rancher Prime and SUSE Multi-Linux Manager. The appropriate combination depends on workloads and operating responsibility rather than on distribution preference alone.
Subscription units differ across the portfolio and can involve instances, sockets, cores, virtual CPUs, managed systems or other programme-specific measures. Support levels and terms also vary. A useful baseline maps each physical, virtual and cloud system to its function, environment, architecture, management platform, lifecycle requirement and support path.
Atmic can organise that baseline and prepare a quote request without asserting SUSE authorisation or entitlement. Current SUSE subscription terms and the exact quotation must confirm product names, quantities, support level, term and any rights for virtualisation, disaster recovery, cloud deployment or mixed-Linux management.
Relevant software areas
What teams commonly evaluate.
- SUSE Linux Enterprise Server for supported enterprise Linux workloads
- SUSE Linux Enterprise Server for SAP applications where the SAP architecture requires it
- SUSE Rancher Prime for supported Kubernetes management requirements
- SUSE Multi-Linux Manager for applicable lifecycle and configuration management across Linux estates
- SUSE Multi-Linux Support or other current services where a mixed-distribution strategy requires them
- Edge, cloud-native and specialised SUSE offerings where validated by the solution design
Typical business uses
Where the requirement starts.
- Running supported enterprise applications on a standardised SLES platform
- Designing the operating-system and high-availability layer for an SAP landscape
- Managing Kubernetes clusters across data-centre, cloud or edge locations with Rancher Prime
- Improving inventory, patch and lifecycle control across a mixed Linux estate
- Aligning support levels and subscriptions with workload criticality and renewal timing
Commercial and technical considerations
Details that can change the right quotation.
Workload variant
General enterprise workloads, SAP applications, container platforms and mixed-Linux management have different product and support considerations. Select the variant from the validated architecture.
Support level and ownership
Match available support coverage to internal capability and application criticality. Define whether SUSE, a cloud provider, an application vendor or an internal team owns each escalation path.
Lifecycle and extensions
Record versions, standard support milestones, long-term service needs and upgrade constraints. Extended lifecycle services should be planned, not assumed.
Management reach
For Rancher Prime or Multi-Linux Manager, define every managed cluster, node or system and its location. Management coverage and operating-system subscription coverage are related but separate questions.
Discovery checklist
Information to gather before requesting a quote.
- Which SLES, SAP, Kubernetes and mixed-Linux management use cases are in scope?
- How many physical systems, sockets, cores, virtual machines, vCPUs, cloud instances and clusters are involved?
- Which versions, architectures and environment types are currently deployed?
- What support coverage, lifecycle duration and upgrade constraints apply?
- Which systems or clusters will Rancher Prime or Multi-Linux Manager manage?
- What SUSE subscriptions, cloud purchases and renewal dates already exist?
- What growth, recovery, edge or migration scenarios should the quote accommodate?
Renewal and lifecycle planning
Treat renewal as a decision point.
- Maintain a system and cluster register tied to subscription records and responsible owners.
- Track product lifecycle milestones and application certification before scheduling upgrades.
- Review scope before adding managed systems, cluster nodes, virtual resources or new locations.
- Reconcile cloud marketplace and direct subscription paths so support ownership remains clear.
- Validate metrics, support levels and specialised workload rights against the current SUSE terms at renewal.
Product packaging, availability, metrics and terms can change. Final recommendations and quotations should be checked against the vendor’s current official product terms for the selected region and purchasing channel. No partner, reseller or authorisation status is implied on this website.
Licensing FAQ
Questions worth resolving early.
What is the difference between SLES and SLES for SAP applications?
SLES is the general enterprise Linux platform. SLES for SAP applications is a specialised offering for applicable SAP workloads, with product and support capabilities tailored to that context. Use the SAP-certified architecture and current SUSE terms to choose.
What is SUSE Rancher Prime?
It is SUSE's enterprise subscription offering around Rancher for managing Kubernetes environments, with supported capabilities and services defined by the selected subscription. Cluster topology and managed-resource counts are needed for planning.
Can SUSE Multi-Linux Manager manage non-SUSE distributions?
It is designed for applicable mixed-Linux management scenarios, but supported distributions, versions and subscription requirements must be checked in current documentation. Management support does not automatically replace each operating system's own subscription obligations.
How are SUSE subscriptions counted?
Metrics vary by product and deployment and can involve instances, sockets, cores, vCPUs, clusters or managed systems. Provide a detailed topology so the current quote can state the correct unit and quantity.
What is needed for a SUSE quote request?
Provide products, workloads, versions, physical and virtual resources, cluster and managed-system scope, environment types, support level, lifecycle needs, current subscriptions, preferred term and renewal deadline.
SUSE Linux
Prepare a better licensing request.
Share the users, devices, workloads, deployment model, current entitlement and renewal date.