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 uses the term “Application Services” to refer to capabilities that provide customers with tools to design and develop cloud-native architectures and applications for hybrid cloud execution. This definition reflects the evolution of middleware to the cloud, with specific capabilities to run better in orchestrated (Kube and container) environments.
In addition to supporting traditional self-managed Application Services deployments, Red Hat offers capabilities as managed cloud services to provide customer choice in operational responsibilities and accelerate time to value. This guide covers subscription considerations for self-managed Application Services products. Other Red Hat products, including platforms and managed cloud services, are introduced here for context, but subscription considerations for those products on their own are not detailed in this guide.
Red Hat has worked over time to increase the value and flexibility of these subscriptions as we continue to evolve our portfolio of application services products for hybrid cloud operation.
This subscription guide will help you better understand:
This guide covers the following Red Hat Application Services products and bundle subscriptions. See Table 1 below for descriptions.
Red Hat Application Services “bundled subscriptions” help 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. 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.
Streams for Apache Kafka 1
Red Hat build of Debezium
Red Hat 3scale API Management
Red Hat build of Apicurio Registry
Red Hat build of Apache Camel 2
All products and components included as part of Red Hat Runtimes
Red Hat JBoss Enterprise Application Platform
Red Hat Data Grid
Red Hat JBoss Web Server
Red Hat build of Quarkus
Red Hat build of OpenJDK
Red Hat JBoss Enterprise Application Platform expansion pack
Red Hat build of Node.js
Red Hat Build of Keycloak
Migration toolkit for Applications
Migration toolkit for Runtimes
Red Hat build of Apache Camel
Streams for Apache Kafka 1
Red Hat 3scale API Management
Red Hat build of Debezium
Red Hat build of Apicurio Registry,
plus all “Red Hat Runtimes” products and components
Red Hat JBoss Enterprise Application Platform
Red Hat JBoss Web Server
Red Hat support for Spring Boot
Red Hat JBoss Enterprise Application Platform expansion pack
Red Hat build of Node.js
Red Hat build of OpenJDK
Red Hat Single Sign-On
Migration toolkit for applications
Migration toolkit for runtimes
Red Hat JBoss Web Server
Red Hat build of OpenJDK
Migration toolkit for applications
Migration toolkit for runtimes
Red Hat Data Grid
Red Hat JBoss EAP (restricted for running Red Hat Data Grid only)
Red Hat build of Apache Camel
Red Hat JBoss EAP
Red Hat build of OpenJDK
Apache HTTP server
Internet information services (IIS) connector, iPlanet connector,
Apache Commons Jsvc
Red Hat Application Services portfolio
(formerly Red Hat Middleware portfolio)
Red Hat JBoss EAP
Red Hat JBoss Web Server
Cloud-native Red Hat Runtimes
Red Hat Data Grid
AMQ broker (only)
Red Hat Middleware Core Services Collection
Red Hat 3scale API Management
Red Hat Process Automation Manager
Red Hat Decision Manager
Red Hat Process Automation Manager
Red Hat Decision Manager
Red Hat JBoss EAP
Red Hat build of OptaPlanner (formerly Business Optimizer)
Red Hat build of OpenJDK,
(formerly Red Hat JBoss BRMS)
Red Hat JBoss EAP
Red Hat Decision Manager
Red Hat build of OptaPlanner (formerly Business Optimizer)
Red Hat build of OpenJDK
Red Hat JBoss EAP
Red Hat Decision Manager
Red Hat Process Automation Manager
Red Hat build of OptaPlanner (formerly Business Optimizer)
Red Hat build of OpenJDK
Embedded JWS/Tomcat for Spring Boot
Layered products include multiple underlying products, which are intended to be used together. Examples include:
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. For example, a 64-core subscription of Red Hat Fuse is not equivalent to independent 64-core subscriptions for each included product or component. 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.
For the full list of product inclusions, see Table 1.
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 OpenShift and Red Hat Application Foundations bundle has a combined installation, identity management, and user experience. You might also be using individual products (e.g., Red Hat OpenShift, Red Hat build of Camel, Red Hat 3scale API Management, etc.) independently for product-specific use cases. It does not matter which product or combination of products is deployed at any 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.
Application Services products with cluster editions are designed to provide consistency and flexible deployment across the entire Red Hat OpenShift environment. Red Hat recognizes that not all components will be used on each Red Hat OpenShift core across the entire environment and offers favorable pricing for cluster editions to provide customers with a cost-effective and flexible option to deploy any included component at any time during the term of the subscription on Red Hat OpenShift. The total core count for cluster editions must equal the total core count for Red OpenShift during the entire subscription term. See Appendix 1 for details.
Products with bare-metal editions may only be deployed machines using Red Hat OpenShift bare-metal products.
Red Hat Application Services products are sold in units of “core bands” of 2-core and 4-core units. In addition, some products may be available for partner-embedded use in single core multiples.
Appendix 1 of Red Hat’s license agreement defines 2 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.