Red Hat Middleware Subscriptions Bundles Overview

Updated -

In June of 2018, Red Hat began offering several subscriptions which are sometimes referred to as “bundles” or “flexible subscriptions”. These subscriptions provide customers with a shared pool of processor cores, which can be deployed as any combination of the included products. They also allow customers to reconfigure their deployments as-needed throughout the subscription term - providing dramatically increased deployment flexibility. The only restrictions are that the shared limit of cores not be exceeded and that only the supported products (listed below) are deployed.

Today, Red Hat offers four of these subscriptions. They can be sold with or without OpenShift Container Platform (OCP). When purchased with OCP, they provide one pool of cores for OCP and a separate, equal pool of cores for Middleware. While many customers will elect to deploy their middleware subscription on OCP, this is not a requirement. Like our standalone middleware subscriptions, these new bundled subscriptions can be deployed on-premise or to a public cloud - with or without OCP.

Subscriptions and Supported Products

Subscription Name Red Hat Supported Products and Components Included Life Cycle Link
Red Hat Runtimes JBoss EAP
JBoss Web Server
Cloud Native Runtimes1
Red Hat Data Grid
AMQ (broker only)
Red Hat Single Sign-On
Open Liberty2
JBoss Core Services
Open Liberty
Red Hat Integration All of the products included in Red Hat Runtimes
AMQ (full product with AMQ Streams)
3scale API Management
Service Registry

Service Registry

Red Hat Process Automation All of the products included in Red Hat Runtimes
Decision Manager
Process Automation Manager


Red Hat Middleware Portfolio Red Hat's full Middleware Portfolio - including support for all individual products mentioned in the three subscriptions above. see above

1 Cloud Native Runtimes include Red Hat build of Thorntail, Red Hat build of Eclipse Vert.x, Red Hat build of Node.js, Red Hat build of Quarkus, and Red Hat support for Spring Boot.

2 Open Liberty is not included in sales for Red Hat Runtimes after 2 Jan 2021.

Please note these subscriptions are not “products” and therefore do not have unified life cycles or supported configurations. Rather, these subscriptions provide support for a set of individual products, each with its own lifecycle and supported configurations.

Extended Lifecycle Support (ELS) can be purchased as an add-on to these bundles. ELS will continue to be sold on a per-product basis, and will not be available as a flexible subscription or bundle.


Great stuff. I really like the flexibility these subscriptions bring to the table. I am finding more and more use cases for them.


Thanks for the feedback. We are finding that these bundles are helping with renewals because they give customers a lot of options and pathways to technology without locking them into a narrow set of products.

Sherman Horton, Middleware CPM

Is this the latest version?

Hi, according to "shared pool of processor cores, which can be deployed as any combination of the included product" and JBoss Core Services/SSO is part of Application Runtimes. Does this mean Core Services is within the shared pool of processor of products like EAP/AMQ? Or It still the same like where Core Services has its own shared pool?

My understanding is that you have a separate pool for Core Services...see official appendix section 1.B, which describes the terms:

I miss Open Liberty on Red Hat Application Runtimes

Robert, thanks for raising this. We've updated the article with reference to Open Liberty and link to the life cycle for that. Also, RHOAR (Red Hat OpenShift Application Runtimes) has been split into the individual Cloud Native Runtimes and that is now reflected in the table.

Not sure who is maintaining this but please make following changes - For RH Integration include following Change Data Capture (Supported Config: Service Registry (Supported Config: - For RH Application Runtimes Change name to 'RH Runtimes' Add 'RH build of Quarkus'

can someone please update this article?