Openshift’s licensing model shapes how teams plan budgets, deploy clusters, and scale applications. Understanding it is not optional. It determines how cost-effective your workloads are, how predictable your expenses will be, and how flexible your operations can get over time. The wrong choice can lock you in. The right choice can give you control.
OpenShift is licensed by Red Hat and generally based on a subscription model. You don’t “buy” the software — you subscribe to it. Costs are usually tied either to the number of cores or the number of worker nodes. The model is designed to cover enterprise features, high availability, security updates, and official technical support. While the core components are built on Kubernetes, the licensing wraps in the Red Hat-tested stack, the update streams, and the support contract that keeps production clusters stable.
The most common way to license OpenShift is through “cores” or vCPU counts in virtualized setups, and “sockets” in bare metal deployments. This means you pay based on the computing resources OpenShift manages, not the number of apps or cluster size by itself. It rewards efficient capacity planning — idle cores still count toward licensing.
Red Hat provides two main subscription options: Standard and Premium. Standard gives you access to support during business hours and a guaranteed SLA for updates. Premium raises that to 24/7 support with faster response times, suited for production-critical workloads. Both subscription levels include the software, tested updates, security patches, and access to Red Hat’s support portal. Licensing terms are usually annual, with multi-year deals offering cost stability.