English
English
Search
Log in / Register

Detail

Red Hat Application Services subscription guide

Last Updated:

Table of contents

Introduction

Red Hat Application Services products

Core bands

What products are included with each subscription?

General subscription benefits for all products

Subscription rules 

Layered products 

Product bundles 

Subscription counting and application development life cycle 

Disaster recovery 

Product life cycle 

Extended life-cycle support 

Product-specific supported configurations 

Using Red Hat Application Services products with third-party environments 

Confirmed Stateside Support (for U.S.-based customers) 

Application services entitlements and how to count units and usage

Application services “everywhere” 

Red Hat Cloud Access program 

On-premise usage guidelines 

On Red Hat OpenShift: Container deployment usage guidelines 

Metering of application services usage on Red Hat OpenShift 

On public clouds: Usage guidelines 

Managed services 

Red Hat OpenShift Dedicated 

Red Hat Application Services on Red Hat OpenShift Dedicated 

Red Hat OpenShift Application Services 

Red Hat products, services, and programs 

Red Hat platform products 

Red Hat Services 

Red Hat partners 

Red Hat Developer 

 

Introduction

This subscription guide provides an overview of Red Hat® Application Services subscriptions, their benefits and entitlements, and Red Hat policies covering the use of these subscriptions.

Red Hat has worked over time to increase the value and flexibility of these subscriptions as we continue to broaden and enhance our portfolio of application services products. 

This subscription guide will help you better understand:

  • Red Hat Application Services products and the range of benefits included with each product subscription.
  • Red Hat policies permitting broad deployment of subscriptions across on-premise, private cloud, public cloud, and hosted cloud environments.
  • How you can determine the number of entitlements needed across any customer life-cycle stage and any chosen deployment location.
  • Specific use cases of deploying Red Hat Application Services across public cloud and managed or hosted environments.
  • Specific use cases of integrating Red Hat Application Services with Red Hat Enterprise Linux® or Red Hat OpenShift® platforms, Red Hat Management and Red Hat Storage products, or together with partner and third-party hardware, software, and services. 

Note: Red Hat uses the term “application services” to refer to the capabilities that run on a cloud-native platform. This definition reflects the expansion beyond traditional, bare metal middleware to managed, cloud-native application development services. Red Hat offers these capabilities as cloud services based on our traditional products, in addition to supporting traditional deployments. These cloud services are managed by Red Hat and are delivered as add-ons to managed Red Hat OpenShift offerings (e.g., Red Hat OpenShift Dedicated, Microsoft Azure Red Hat OpenShift) or as services independent from the underlying Red Hat OpenShift layer. 

Red Hat Application Services products

This subscription guide covers the following Red Hat Application Services subscriptions:

  • Bundled offerings:
    • Red Hat Application Services Portfolio
    • Red Hat Runtimes
    • Red Hat Integration
    • Red Hat Process Automation
    • Red Hat OpenShift and Red Hat Runtimes
    • Red Hat OpenShift and Red Hat Integration
    • Red Hat OpenShift and Red Hat Process Automation
    • Red Hat OpenShift and Red Hat Application Services Portfolio
    • Red Hat OpenShift, Red Hat Runtimes, Red Hat OpenShift Data Foundation
    • Red Hat OpenShift, Red Hat Integration, Red Hat OpenShift Data Foundation
    • Red Hat OpenShift, Red Hat Process Automation, Red Hat OpenShift Data Foundation
    • Red Hat OpenShift, Red Hat Application Services Portfolio, Red Hat OpenShift Data Foundation
  • Product offerings:
    • Red Hat JBoss® Enterprise Application Platform
    • Red Hat JBoss Web Server
    • Red Hat Data Grid
    • Red Hat AMQ (includes AMQ Streams, AMQ Broker, and components listed below)
    • Red Hat Fuse
    • Red Hat 3scale API Management
    • Red Hat Decision Manager
    • Red Hat Process Automation Manager
    • Red Hat build of OpenJDK
    • Red Hat build of Quarkus
    • Cloud-native Ret Hat Runtimes, which are Red Hat’s builds of:
      Thorntail, Node.js, Eclipse Vert.x, and Red Hat support of Spring Boot
    • Red Hat Middleware Core Services Collection, which includes:
      Red Hat Single Sign-On, Apache HTTP Server and Jsvc, Web Connectors

Notes:

  • The descriptions in this document also cover all program-specific or route-specific versions of the bundles and products listed above. Examples of these are: 
    • ‘for OpenShift’ or “for OpenShift Dedicated’ product descriptions
    •  ‘Extended life-cycle support add-ons,’ if applicable
    • ‘Certified Cloud Service Provider, embedded, L3-only support partners, OEM’
  • Also, any legacy products that are still supported—such as Red Hat Fuse Service Works or Data Virtualization—will also follow these general rules until their respective end-of-life dates.

Core bands

Red Hat application services products are sold in units of “core bands” or core multiples including 2-core, 4-core, 16-core, and 64-core units. In addition, some products may be available for partner embedded-use in single core multiples.

What products are included with each subscription?

Red Hat application services “bundled subscriptions” helps you deploy a choice of one or more products on the same physical location, or to separate hardware units, provided that each unit running part or all of the product is counted toward the subscription total.

Table 1 shows the complete list of products and selected components included with each subscription. Please see component details pages for a comprehensive list of components. Table 1 outlines which software is eligible for support or deployment in a manner consistent with the “production purposes” definition in Appendix 1 of Red Hat license agreements.

Table 1. Subscription products and components

Red Hat Runtimes Red Hat JBoss EAP, Red Hat JBoss Web Server, Cloud-native Red Hat Runtimes, Red Hat Data Grid, Red Hat AMQ (broker only), OpenJDK, Red Hat Middleware Core Services Collection, Red Hat Single Sign-On
Red Hat Integration Red Hat Fuse, Red Hat AMQ, Red Hat 3scale API Management, Debezium, Service Registry, plus all “Red Hat Runtimes” products and components
Red Hat Process Automation Red Hat Process Automation Manager, Red Hat Decision Manager, plus all “Red Hat Runtimes” products and components

Red Hat Application Services portfolio
(SKU Red Hat Middleware portfolio)

The complete application services portfolio—all of the products listed in Red Hat Runtimes, Red Hat Integration, and Red Hat Process Automation

Red Hat JBoss 
Enterprise Application Platform

Red Hat JBoss EAP, Web Server, cloud-native runtimes, Red Hat build of OpenJDK, Red Hat Middleware Core Services Collection, Red Hat Single Sign-On
Red Hat JBoss Web Server Red Hat JBoss Web Server, Red Hat build of OpenJDK
Red Hat Data GridRed Hat Data Grid, JBoss EAP (restricted for running Red Hat Data Grid only)
Red Hat AMQFull Red Hat AMQ product (clients, broker, streams, online)
Red Hat FuseRed Hat Fuse, Red Hat AMQ, JBoss EAP, OpenJDK, Red Hat Middleware Core Services Collection
Red Hat 3scale API ManagementRed Hat 3scale API Management platform (Red Hat OpenShift sold separately)

Red Hat Decision Manager
(formerly Red Hat JBoss BRMS)

 Red Hat JBoss EAP, Red Hat Decision Manager, Business Optimizer (OptaPlanner), OpenJDK, Red Hat Middleware Core Services Collection

Red Hat Process Automation Manager (formerly Red Hat JBoss BPM Suite)

Red Hat JBoss EAP, Red Hat Decision Manager, Business Optimizer (OptaPlanner), Process Automation Manager, OpenJDK, Red Hat Middleware Core Services Collection

General subscription benefits for all products

Often, a customer’s first question is “Why do I need a subscription?” There are many benefits to purchasing a Red Hat subscription, including:

  • Predictability. Subscriptions are offered on an annual or multiyear basis and include access to new versions at no additional cost, so there are no large upfront license fees or hidden costs.
  • Flexibility. Red Hat’s application services subscriptions provide value through the entire application life cycle—from development through production—and allow a variety of deployment options from on-premise to public cloud.
  • Integrated and certified enterprise platforms. You have access to enterprise open source application services platforms, in source code and binary forms, along with enterprise product documentation specific to each product release.
  • Regular upgrades and updates. These include enhancements, new features, new platform certifications, and access to the latest defect and security fixes.
  • Security response. Subscriptions include Red Hat’s industry-recognized security response process to help you proactively address potential security issues in their environments. Learn more about Red Hat product security.
  • Long-term stability. Each Red Hat application services product has a defined multiyear product life cycle with strict update policies that maintain long-term application stability and compatibility.
  • World-class technical support. Open source application services experts provide unlimited incident support with 24x7 coverage up with one-hour response time for your critical issues.
  • Red Hat Customer Portal access. A single portal for accessing all of the benefits of a Red Hat subscription, including enterprise software delivery, product updates, critical issue notifications, knowledge base access, and case management.
  • Partner certifications. Know that your enterprise application services are fully certified by leading Red Hat independent software vendor (ISV) partners.
  • Legal assurance. The Red Hat Open Source Assurance program safeguards your development and deployment of open source solutions from legal harm. 

Subscription rules 

Layered products

Layered products include multiple underlying products which are intended to be used together. Examples include: 

  • Red Hat Fuse includes Red Hat AMQ and Red Hat JBoss Enterprise Application Platform.
  • Red Hat Process Automation Manager includes Red Hat Process Automation Manager, Red Hat Decision Manager, and Red Hat JBoss Enterprise Application Platform.
  • Red Hat OpenShift, Red Hat Enterprise Linux, Red Hat JBoss Web Server, Red Hat Software Collections, Red Hat Single Sign-On, Red Hat build of Quarkus.

These products and components—which are included in a single SKU—are typically used together with or in support of the named product. 

In some cases, they can be used standalone on separate hardware. However, this requires excess unused capacity and often results in a more expensive usage of a layered product.

For example, the expectation for a customer buying 64 cores of Red Hat Fuse is that the included JBoss EAP will be used as the runtime for Red Hat Fuse. If a customer is only using 48 cores, for example, they might want to repurpose the 16 unused cores for JBoss EAP-only workloads. This is an edge case, but it is fine if the customer chooses to do this. However, they should acknowledge that these are effectively very expensive JBoss EAP cores.

The most important point is that a layered product cannot be deconstructed into numerous individual subscriptions. A 64-core subscription of Red Hat Fuse is not equivalent to numerous 64-core subscriptions for each included product. It provides 64 total cores, upon which one or all products and subcomponents can be deployed.

In select cases—for example, single sign-on in Red Hat OpenShift—the product or component has a restricted use case and cannot be deployed separately from Red Hat OpenShift, regardless of whether excess capacity of the named product exists.

Please see the full product inclusions (Table 1) for all detailed rules.

Product bundles 

A product bundle is a subscription entitlement that offers a single pool of cores intended to be shared across multiple products, components, and use-cases. Your usage could be of several products together—for example, Red Hat Integration has a combined installation, identity management, and user experience. You might also be using individual products (e.g., Red Hat Fuse, JBoss EAP, Red Hat Decision Manager) independently for product-specific use-cases. It does not matter which product or combination of products is deployed at any point in time, as long as the combined core count does not exceed the total number of paid subscription cores. These cores may be used on different CPUs or on any mix of on-premise, private-cloud, or public-cloud environments.

Additional detailed information on Red Hat application services bundled products is available in the Red Hat Middleware Subscriptions Bundles Overview

Subscription counting and application development life cycle

Appendix 1 of Red Hat’s license agreement defines two use-case modes when determining whether to charge application services subscription fees for units running in a specific use case, “developer purposes” and “production purposes.” Any units running for development purposes are not counted and do not require subscription fees for each unit. Any units running for production purposes are counted and do require subscription fees for each unit.

Table 2. Description and appendix 1 licensing requirements

Life-cycle stageCores
Counted?

Single-user, for development purposes

Access by a single developer, on a single-user laptop or desktop, running single-user instances on the laptop or a connected server

Appendix 1: “Development purposes” means using the software for development-related tasks that are performed by a single user acting in a standalone mode such as:

(a) An individual developer writing software code.

(b) A single user performing prototyping or quality assurance testing, where neither involved any form of automated testing, multiuser testing, or multiclient testing.

(c) A Red Hat partner user demonstrating software or hardware that runs with or on the software.

No

Other development use-cases, or quality assurance, load test, staging, production, or hot or active disaster recovery 

A developer-focused project environment shared with more than a single person; continuous integration or functional testing environments; business users testing early prerelease versions of the software; also called user acceptance testing, or staging, or preproduction environments

Appendix 1: “Production purposes” means using the software such as:

(a) In a production environment.

(b) Generally using live data or applications for a purpose other than for development.

(c) Any automated quality assurance or testing, multiuser quality assurance or testing, or multiclient quality assurance testing.

(d) For back-up instances.

Yes

Warm or cold disaster recovery 

Transferring subscriptions. You may transfer, migrate, or otherwise move software subscriptions provided you are accountable for the number and types of units associated with the software subscriptions.

No

Disaster recovery

Cores in hot disaster recovery are counted. When deploying Red Hat application services deployments in disaster recovery (DR) environments, virtual or physical cores across hot DR or failover environments should be included as part of the total core count. Hot DR systems are running concurrently and are ready to receive traffic quickly in the event of a disaster within the primary environment.

Cores in warm disaster recovery are not counted. A warm backup site is already stocked with hardware representing a reasonable facsimile of that found in your datacenter or primary site. To restore service, the last backups from your off-site storage facility must be delivered, and bare metal restoration completed, before the real work of recovery can begin.

Cores in cold disaster recovery are not counted. With cold disaster recovery, if a disaster were to occur and systems under subscription were no longer available, you can temporarily transfer primary subscription entitlements that are no longer in use to your disaster recovery environments (making cold disaster recovery a temporary production environment). The expectation is that these systems will never run concurrently with the primary cores and rarely receive updates, if at all.

Product life cycle

A critical aspect to any Red Hat Application Services subscription is the support policy and product life cycle. This policy is included in Appendix 1 and is considered a legally binding document. It contains information on our software releases and support and should be studied in detail.

Products and certain subcomponents each have a life cycle.

In order to receive the full benefits of your subscription, we require you to:

  1. Run a supported major version of the product,
  2. Run the latest minor release in a major release stream (e.g., JBoss EAP 7.2).
  3. Purchase ELS subscriptions in addition to the base product when running a product version in either Extended Life-cycle Support (ELS)-1 or ELS-2.

Please note that customers frequently sign long-term deals with Red Hat. These deals do not supersede the published dates of our product life cycle. For example, a customer may sign a five-year contract. This does not give them the ability to “choose a version” and run it for five years with no changes. It is likely that a customer with a long-term subscription will need to either migrate to a newer major version or pay for the appropriate ELS add-on during the course of their contract with Red Hat.

Extended life-cycle support

Application Services ELS is an additional product life-cycle support phase that immediately follows the end of a product major version’s maintenance support window. During this phase, Red Hat lowers its overall support obligations for the product version and will only deliver certain bug fixes. Most active Red Hat application services products have at least one major version eligible for ELS. The full list is available on the public product life cycle page. Detailed discussion is available on the support policy and product life cycle page. 

Product-specific supported configurations

Each Red Hat application services product has a specific list of supported and tested configurations

“Tested” means that the specific versions of the product, Java™ Virtual Machine (JVM), platform or operating system (OS), and hardware listed have been tested by Red Hat and are performing properly. “Supported” means that Red Hat will fully support the product (e.g., Red Hat Runtimes) running on a particular JVM—but may very occasionally require the customer to reproduce an issue on a tested platform or involve a third party in resolving the issue if an untested platform or hardware configuration is suspected to be causing the issue. Red Hat targets the most in-demand hardware and software configurations, but cannot test every possible combination. Red Hat offers clear support guidance for using our products with untested third-party environments.

Using Red Hat Application Services products with third-party environments

You may choose to deploy your Red Hat Application Services subscriptions in environments integrated with third-party software or hardware or a public cloud provider. When this happens, Red Hat’s Support team will initially follow the support guidelines listed on each product’s supported configurations page. Additionally, Red Hat will offer a level of support for untested environments. Details of these support policies are available in this Red Hat Customer Portal article on middleware products deployed in third-party environments.

Confirmed Stateside Support (for U.S.-based customers)

Red Hat support is a global effort which requires input from experts around the world. However, some customers require their support to be only from U.S. citizens on U.S. soil. Red Hat Confirmed Stateside Support (CSS) was created to provide that. For example, customers running Red Hat-supported products in Amazon Web Services (AWS) GovCloud require this due to possible exposure of International Traffic in Arms Regulations (ITAR) data and the ensuing legal ramifications.

CSS has costs associated with meeting these special requirements. It necessitates an offsite facility with a dedicated phone line, select U.S. citizen staff with in-depth ITAR training, a specialized workflow, a separate ticketing portal, and many legal considerations to protect sensitive data. The price of CSS reflects the expenses covered by Red Hat to provide these benefits.

We understand that in many cases customers take special care to remove ITAR-sensitive data in support cases. However, the drastic legal ramifications for Red Hat handling ITAR data without CSS outweighs our willingness to take any chances. Red Hat’s Confirmed Stateside Support offering is designed with our information security-conscious customers in mind and is required for customers with Red Hat products on AWS GovCloud. Please contact your Red Hat sales channel for pricing or implementation details. 

Application services entitlements and how to count units and usage

Application services “everywhere”

Red Hat Application Services subscription licensing is very flexible. Subscriptions are licensed and supported across multiple OS and hardware platforms, and across any mix of on-premise, private cloud, and public cloud deployment environments. Subscription entitlements also provide value throughout the full application development and deployment life cycle. 

This subscription licensing flexibility eliminates any need to purchase products for a particular deployment environment (e.g., public cloud), OS or container platform (e.g., Red Hat Enterprise Linux or Red Hat OpenShift), or life-cycle phase (e.g., development). No additional purchases are needed when you move from any one of these environments to another during the term of a subscription.

Subscription flexibility is further highlighted by the Red Hat Application Services bundled offerings—Red Hat Runtimes, Red Hat Integration, and Red Hat Process Automation. These bundles deliver the same freedom as individual products plus an ability to change the usage combination of licensed products and components at any time during the term of a subscription. These subscriptions entitle a shared pool of units that can be used across the eligible and included products.

In the past, some Red Hat Application Services products have contained specialized descriptions, such as “Red Hat Fuse for OpenShift” or “Red Hat JBoss EAP for OpenShift Dedicated.” The entitlements created by each or any of these branded descriptions are the same. The additional descriptions were intended to highlight that these products were certified and tested to deploy on Red Hat OpenShift. We decided to remove the special product naming to avoid any confusion created by having multiple descriptions, and reinforce that our application services products are licensed to deploy on any or all of these environments. 

Red Hat Cloud Access program

The Red Hat Cloud Access program lets you migrate your Red Hat subscription deployments to any Red Hat certified cloud provider. This includes well known public cloud providers such as Amazon Web Services, IBM Cloud, Microsoft Azure, Google Cloud, and Alibaba Cloud. This includes providing a consistent application environment across physical, virtual, and cloud deployments. 

Red Hat Application Services subscriptions convert using the same vCPU-to-core ratio that is used by the cloud provider to handle routine hyperthreading. This is commonly two vCPUs per core, but may vary with specialized processor hardware configurations. Each vendor describes this conversion. For examples, consult the AWS guide

On-premise usage guidelines

The following principles apply to noncontainerized subscription deployments, such as application services on Red Hat Enterprise Linux on a physical server in a datacenter.

Physical cores, virtual cores

  • Physical cores are our standard unit of measure. 
  • Cores may be deployed across multiple CPU sockets, CPUs, or servers. 
  • Virtual cores and vCPUs can be counted, but need to align with physical cores. 
  • If physical cores can be counted when deploying in a virtualized environment, then these units will be counted.
  • If you do not know which or how many physical cores in a CPU socket-pair use our software, then we charge for all of the cores in the CPU socket-pair.
  • You need to count all cores or vCPUs in a CPU socket-pair unless they are using known core-limiting software that limits the use of our software within that socket-pair.

Virtual machines

  • You can create a variable-sized virtual machine (VM) within a CPU socket-pair. VMs are built atop underlying physical cores. We count the physical cores that contain the VM.
  • If use of our software is limited to a VM which only uses a subset of physical cores in the socket-pair, then we only count those physical cores associated with the VM.
  • You need to count all cores or vCPUs within a VM unless they are using known core-limiting software that limits the use of our software within that VM.
  • “Virtual cores” are physical cores used within a virtual environment or VM. 

Hyperthreading, vCPUs

  • Hyperthreading creates more, but smaller, virtual CPUs across a fixed number of physical cores. The vCPU has become a common logical unit-of-measure in cloud-based platforms. With noncompute intensive apps, customers can take advantage of the larger number of hyperthreaded vCPUs without expanding the physical core utilization.
  • This does not change our counting rules. We continue to charge for the underlying physical cores.
  • You can count the hyperthreaded vCPUs using the common (2) vCPU-to-(1) core ratio. This ratio only applies if hyperthreading is in use.
  • If you only know the vCPU count and not the core count, we will allow 2:1 if hyperthreading is being used. We will count 1:1 if hyperthreading is not in use.

On Red Hat OpenShift: Container deployment usage guidelines

Unit counting on container platforms such as Red Hat OpenShift has some differences in comparison with noncontainer deployments.

What is the same as noncontainer deployment?

  • The vCPU/core remains the countable unit for entitlements and license tracking. Container platforms measure pods and nodes within a cluster. But, these are user-defined groupings of vCPUs/cores. 

What is different from noncontainer deployment?

  • Red Hat OpenShift (or the container platform) automates the starting and stopping of application services workload instances. This simplifies Red Hat’s entitlements counting policy to charging only for cores or vCPUs that are concurrently running at any given time during the subscription period. 
  • It does not matter where the application services workload gets deployed within the overall cluster. As long as the concurrent usage of cores remains at or below the level of the active subscription, no additional cores need to be added to a subscription.
  • Core/vCPU sizes of container instances are individually tracked, logged, and summed together, even partial vCPU or subcore instances, for any given period of time.  For billing purposes, this summary is rounded up to the nearest whole selling unit, 2-cores. 

    Example:
  • Customer deploys (10) 300-millicore and (1) 500-millicore JBoss EAP containers within an OpenShift cluster.
  • This adds up to 3.5 total JBoss EAP cores across these 11 container instances.
  • Since the smallest SKU unit we sell is 2-cores, the customer would buy (2) x 2-core JBoss EAP subscriptions to cover this usage.

    Only the sum of all instances used at any given time needs to be rounded up to a multiple of SKU-units. Any individual container instances can be measured in partial core sizes. 

You may choose to set predefined limits on Red Hat Application Services workload sizing by limiting a workload to specific nodes in a cluster. This approach may offer certain advantages to a customer, but is not required by Red Hat for metering or counting purposes.

Note: If you purchase the same number of Red Hat Runtimes cores as exists in your Red Hat OpenShift cluster, for example, there is no need to count the number of Red Hat Runtimes cores running during any given period. The Red Hat OpenShift cluster can have unlimited Red Hat Runtimes usage within this cluster. 

Metering of application services usage on Red Hat OpenShift

Red Hat Application Services subscriptions are license-only enforcement. Red Hat does not deliver any tooling that restricts the deployment of application services products based on any subscription limits. 

As of 2020, Red Hat product teams are working to deliver tooling that delivers the needed end-to-end product tagging, metering, and reporting that will help customers determine how many cores of any application services product are running throughout an OpenShift cluster at any point in time. This reporting is part of an overall Red Hat Subscription Watch monitoring and reporting tool that allows Red Hat customers to see the usage of any Red Hat product.

On public clouds: Usage guidelines

We highlighted earlier in this subscription guide that Red Hat Application Services subscription licensing is very flexible. Subscriptions are licensed and supported across multiple OS and hardware platforms, and across any combination of on-premise, private cloud, and public cloud deployment environments. This means that unit counting of cores and vCPUs on public clouds uses the same approach as on-premise (noncontainer deployments) or on Red Hat OpenShift (container deployments).

Managed services

Red Hat OpenShift Dedicated 

Red Hat OpenShift Dedicated is an OpenShift cluster provided as a managed cloud service, configured for high availability (HA), and dedicated to a single customer (single-tenant). OpenShift Dedicated is managed by Red Hat Site Reliability Engineering, providing increased security and years of operational experience working with OpenShift in both development and production. OpenShift Dedicated also comes with award-winning 24x7 Red Hat Premium Support and a 99.95% Service Level Agreement (SLA).

When purchased as a single subscription which includes cloud infrastructure from Red Hat, OpenShift Dedicated runs on shared hardware on Amazon Web Services (AWS). Each cluster is single-tenant (dedicated to a single customer). For customers interested in hosting on Microsoft Azure, there is the jointly-offered Microsoft Azure Red Hat OpenShift. There is also the option for running OpenShift Dedicated on your existing cloud infrastructure. Learn more about Red Hat OpenShift Dedicated

Red Hat Application Services on Red Hat OpenShift Dedicated

You can mix your application services core entitlements—whether you purchased them as on-premise, Red Hat Application Services for Red Hat OpenShift, or Red Hat Application Services for OpenShift Dedicated. This applies to OpenShift Dedicated, Microsoft Azure Red Hat OpenShift, Red Hat OpenShift on IBM Cloud (jointly engineered), and Red Hat OpenShift Service on AWS (jointly managed and supported). However, you are responsible for honoring subscription entitlement limits associated with your Red Hat Application Services purchases. 

Because OpenShift Dedicated can be deployed on three different instance classes, Red Hat uses these conversion rates for deploying core entitlements on OpenShift Dedicated:

  • Standard instance class, conversion rate = (4) OpenShift Dedicated vCPUs per (2) cores, our standard vCPU-to-core ratio policy.
  • High CPU instance class, conversion rate = (8) OpenShift Dedicated vCPU per (4) cores, our standard policy but applied to double-core-sized instances.
  • High Memory instance class, conversion rate = (4) OpenShift Dedicated vCPU per (3) cores, this is a 50% uplift that we are applying to high-memory usage. 

Some product features may not work the same with OpenShift Dedicated as with an on-premise deployment. As Red Hat teams make these discoveries, we will be sharing this list of differences in Red Hat’s Customer Portal. 

Red Hat manages a repository of application services images that can be deployed on OpenShift Dedicated. If you want to use a version of an application services product that is not in this repository, say an older version of EAP, then you are responsible for any handling, installation, or deployment of the application services software onto OpenShift Dedicated.

Red Hat OpenShift Application Services

Red Hat offers fully managed application services on managed OpenShift (e.g., OpenShift Dedicated, Red Hat OpenShift Service on AWS, Azure Red Hat OpenShift) that are based on the same technologies as our self-managed products. These applications services—like the base layer OpenShift Dedicated—are managed by Red Hat and are backed by a service level availability commitment. 

These services may be offered in different patterns. Some are add-ons to managed OpenShift where you would purchase an instance or instances of managed OpenShift and add these services to that cluster. You are responsible for ensuring that your OpenShift cluster has sufficient resources to run the add-on and any other services as you wish.

The other pattern is more like an “instance-as-a-service” where you purchase access to a defined quantity of the service but do not have to purchase managed OpenShift.

Red Hat products, services, and programs 

Red Hat platform products

Red Hat Enterprise Linux

Red Hat is one of the leading contributors to Linux. It is an open source operating system (OS). It is the foundation from which you can scale existing apps—and roll out emerging technologies—across bare-metal, virtual, container, and all types of cloud environments.

Red Hat OpenShift

Built by open source leaders, Red Hat OpenShift is the leading enterprise Kubernetes platform. Red Hat OpenShift provides a security-focused, consistent foundation to deliver applications anywhere, with full-stack automated operations and streamlined developer workflows. With Red Hat OpenShift, innovators can focus on what matters, stay competitive, and outpace continually rising customer expectations.

Red Hat OpenShift includes everything you need for hybrid cloud, enterprise container and Kubernetes development and deployments. It includes an enterprise-grade Linux operating system, container runtime, networking, monitoring, container registry, authentication, and authorization solutions. These components are tested together for unified operations on a complete Kubernetes platform spanning every cloud.

Red Hat Services

Close the gap between what you know and what you need from architecture through adoption and training. Our teams and resources help you get the most out of your technology investment. No matter where you are in your journey with Red Hat products, we have offerings designed to help you do more.

  1. Red Hat Training and Certification

    Discover: Find out how to use Red Hat products with our course and exam offerings. Our skills paths will help you embrace emerging technologies.
  2. Red Hat Consulting

    Adopt: Collaborate with our technical experts to take your use of Red Hat technologies to the next level. We will help you build a solution that addresses all of your technology needs.
  3. Red Hat Open Innovation Labs

    Innovate: Team up with us in an immersive residency focused on culture, process, and tools. We can help you transform your organization's approach to application development and DevOps.
  4. Red Hat Technical Account Management

    Scale: Connect with a technical advisor for proactive help and specialized guidance. Our seasoned professionals will help shape your technology strategy to meet your toughest business challenges.
  5. Red Hat Support

    Engage: Get the most out of your Red Hat portfolio with the information you need. You can get focused help from the best engineers in the industry and exchange ideas with peers and mentors.

Red Hat partners

When partners win, we win.

Red Hat’s partners play an integral role in our go-to-market strategy and overall success. Our partner program offers competitive benefits that allow partners to increase their expertise and sell and deliver open source technology that is ready for today’s enterprise.

Our programs

Solution Provider Program

Global Independent Software Vendors (ISV) Program

Global Systems Integrators (GSI) Program

Certified Cloud and Service Provider Program

Embedded Program

Training and Certification Partner Program

Professional Services Partner Program

Red Hat Partner Connect

Get more information on Red Hat’s partner programs.

Red Hat Developer 

Red Hat Developer is a global community of passionate Red Hat technology experts and enthusiasts, built by and for developers. The Red Hat Developer program provides the tools, technologies, and community developers need. Join this program to solve problems, connect with colleagues, discover what’s next, and lead projects forward.

The Red Hat Developer program is for developers, software engineers, web designers, front-end designers, user experience (UX) designers, computer scientists, architects, testers, product managers, project managers, and team leads. 

Get more information at developers.redhat.com.