Deployment inventory
Record physical systems, virtual machines, cloud instances, clusters and managed nodes by environment. Red Hat subscription applicability follows deployed resources and use, so a high-level user count is not enough.
Red Hat subscriptions
Red Hat licensing
Plan enterprise open-source subscriptions around deployed resources, environments, support expectations and the complete application platform lifecycle.
Request a licensing quoteRequirementMetricTermLifecycleRed Hat
Licensing overview
Map the requirement before comparing offers.
Red Hat uses a subscription model rather than treating enterprise software as a one-off licence purchase. An active subscription can provide access to supported software, updates, knowledge and support services for the covered scope. Planning therefore requires an accurate view of installations and use cases, not simply a download count.
Common requirements include Red Hat Enterprise Linux (RHEL), Red Hat OpenShift and Red Hat Ansible Automation Platform. Red Hat Satellite and other management or platform products may also be relevant. Each family has its own subscription units, variants, deployment rules and support choices, and metrics can differ between physical, virtual, cloud, development and production arrangements.
Atmic can help document the environment and prepare a subscription request without claiming Red Hat partnership or deciding contractual compliance. The current Red Hat product appendix, subscription terms and quotation should be used to validate every quantity, support level and environment-specific right.
Relevant software areas
What teams commonly evaluate.
- Red Hat Enterprise Linux subscriptions for physical, virtual and cloud deployment patterns
- Red Hat OpenShift offerings for supported Kubernetes and application-platform requirements
- Red Hat Ansible Automation Platform for controlled enterprise automation
- Red Hat Satellite and management capabilities for applicable RHEL estates
- Development, test, disaster-recovery and production subscription considerations
Typical business uses
Where the requirement starts.
- Standardising supported Linux for business-critical applications across hybrid infrastructure
- Building a supported container platform for development and operations teams
- Introducing governed automation for repeatable infrastructure and application tasks
- Improving subscription visibility across physical hosts, virtual machines and cloud instances
- Aligning support scope and renewal planning with application criticality and lifecycle
Commercial and technical considerations
Details that can change the right quotation.
Product variant and use case
Identify architecture, workload, guest density, container platform and management pattern. RHEL, OpenShift and Ansible offers use different units and are not interchangeable.
Environment and lifecycle
Separate production, development, test, build, recovery and temporarily inactive systems. Confirm which rights apply to each environment instead of assuming non-production is unlicensed.
Support and service level
Match available support levels and coverage hours to business need, internal capability and application support dependencies. Avoid implying a response commitment not stated in the purchased subscription.
Cloud and third-party purchasing
Marketplace, cloud-provider and bring-your-own-subscription routes can differ. Record who supplies the subscription and support path for each deployed workload.
Discovery checklist
Information to gather before requesting a quote.
- Which RHEL systems, OpenShift clusters and Ansible-managed nodes are in scope?
- Where does each resource run: physical, virtual, private cloud or public cloud?
- Which systems are production, development, test, build or disaster recovery?
- What architectures, socket or core layouts, guest densities and cluster sizes apply?
- What support level and service window does each workload require?
- Which current subscriptions, cloud marketplace purchases and renewal dates exist?
- What growth, migration, extended lifecycle or version constraints are planned?
Renewal and lifecycle planning
Treat renewal as a decision point.
- Reconcile the Red Hat inventory with infrastructure and cloud records on a defined schedule.
- Register covered systems through the appropriate organisation process and preserve purchase evidence.
- Track versions, lifecycle milestones, support level and application dependencies alongside renewal dates.
- Review subscription impact before adding nodes, clusters, guests or cloud instances.
- Validate quantities against current Red Hat terms and product appendices before every 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.
Is Red Hat software purchased as a perpetual licence?
Red Hat enterprise products are generally supplied through subscriptions that cover defined deployments and provide access to supported software, updates and services during the active term. The exact product terms establish the scope.
Does one RHEL subscription cover unlimited virtual machines?
Do not assume so. Available RHEL subscription variants and virtualisation rights depend on the offer and deployment pattern. Supply host, guest, socket or core and environment details for a current calculation.
Are development and disaster-recovery systems automatically covered?
Not automatically. Some offers or terms address specific development or recovery scenarios, but eligibility and conditions must be checked. Include every environment in the inventory and request explicit treatment.
How is Ansible Automation Platform scoped?
Current offerings use defined subscription units and supported deployment patterns. Count the managed estate and describe the automation architecture, environments and support need rather than relying on an Ansible user count alone.
What should be included in a Red Hat quote request?
Provide products, versions, deployment locations, physical and virtual topology, cluster or managed-node counts, environment types, support needs, current subscription records, renewal dates and planned growth.
Red Hat
Prepare a better licensing request.
Share the users, devices, workloads, deployment model, current entitlement and renewal date.