OpenShift

What it is

Red Hat OpenShift is an enterprise Kubernetes application-platform family, not a single hosting plan. Self-managed editions range from Virtualization Engine and Kubernetes Engine through Container Platform and Platform Plus; managed services run with AWS, Microsoft, Google or IBM under different billing and responsibility models. The advertised $0.076 per hour floor is based on a 4-vCPU three-year reservation and still requires a minimum worker configuration, so it is not a complete cluster price. Trials and a developer sandbox exist, while production cost includes subscriptions or service fees plus infrastructure, storage, networking and operations. Who it is for: large organisations that already run Kubernetes in production, need enterprise support contracts, and want opinionated defaults for security, image registries, CI pipelines and multi-cluster management rather than assembling them from open-source parts. The managed variants on AWS and Azure suit teams that want OpenShift's tooling without operating the control plane. Where it falls short: cost and weight. Licensing is by core or by subscription through Red Hat sales, so there is no self-serve monthly price and small teams are often better served by a managed cloud Kubernetes service or by Rancher. The platform also has strong opinions about how images are built and how routes and operators work; teams arriving from vanilla Kubernetes spend time relearning conventions. OKD, the community upstream, is free but without the support that is the main reason to buy OpenShift.

Key features

• Enterprise Kubernetes

  Runs containerized workloads on a security-focused Kubernetes and RHEL CoreOS foundation.

• Developer platform

  Adds console, Operators, build and deployment workflows, GitOps, pipelines, serverless and service mesh by edition.

• Hybrid deployment

  Supports validated on-premises, cloud and edge infrastructure with consistent APIs and operational patterns.

• Managed services

  Offers jointly or vendor-managed OpenShift services on major public-cloud platforms with product-specific SLAs.

Strengths and trade-offs

Who it is for

Organizations standardizing container and application operations across multiple teams or environments and able to fund platform engineering or a managed service.

Pick it or skip it

Frequently asked questions

Can you run OpenShift on-premise, and what does it cost?

Yes. Red Hat sells four self-managed editions for your own data centre or cloud accounts: Kubernetes Engine, Virtualization Engine, Container Platform and Platform Plus, licensed by core pairs. Red Hat does not publish self-managed prices; the pricing page says cost varies with sizing and subscription choices and routes you to sales. The managed cloud services (ROSA, Azure Red Hat OpenShift, OpenShift Dedicated, OpenShift on IBM Cloud) do list a starting rate: as little as $0.076 per hour for 4 vCPU on a 3-year reserved contract.

Is there a free or community edition of OpenShift?

Red Hat offers a free Developer Sandbox (a minimal, preconfigured environment), a 60-day trial of the self-managed Container Platform on your own infrastructure, and a trial of OpenShift Dedicated. The community upstream distribution is OKD: free, Apache-licensed, community-supported and not covered by Red Hat support.

What does Red Hat's OpenShift subscription guide say you actually have to count?

Two bases, and they are not nodes in the way most people assume. A core-pair is 2 physical cores, or 4 vCPUs — on bare metal it always means physical cores regardless of hyperthreading, so 2 hyperthreaded cores presenting as 4 vCPUs are still one core-pair, and on AWS, Azure or GCP 4 vCPUs are always one core-pair. Core-pair subscriptions are counted at the cluster level, so a single subscription can span several instances, VMs and physical servers. The alternative base is the bare-metal node subscription: one per physical server, and it can never span more than one server. Add-on accelerators (GPUs, TPUs, DPUs, FPGAs) are counted separately by physical device, and every subscription must pick an SLA — Standard 8x5 or Premium 24x7.

Do OpenShift control plane and infrastructure nodes need their own subscriptions?

No, and this is the line item people over-buy. Entitlements for control plane nodes are included in self-managed OpenShift subscriptions and are not counted when you size your purchase. Infrastructure nodes — the ones running cluster support pods such as the HAProxy-based ingress load balancer — are also included, on one condition: no user application pods may run on them. Only compute nodes, where application pods actually run, need to be counted. They may still cost you in infrastructure spend; they just do not consume OpenShift entitlements.

Is there a product called "OpenShift Server"?

No. Red Hat does not sell anything under that name, which is why searches for it land on generic pages. The self-managed line — the thing you install on your own servers — is sold as four editions: OpenShift Kubernetes Engine, OpenShift Container Platform, OpenShift Virtualization Engine (bare-metal only, KVM-based) and OpenShift Platform Plus (x86 clusters only). The word people usually mean by "server" maps to a compute node: an instance of RHEL or RHEL CoreOS where application pods run, and the only node type that consumes a subscription. The other route is the managed cloud services, which Red Hat and its cloud partners operate for you.

Does OpenShift have a free plan?

No free plan is listed on the vendor's pricing page. OpenShift is sold on a quote basis.

Who is OpenShift best for?

Organizations standardizing container and application operations across multiple teams or environments and able to fund platform engineering or a managed service.

What are the main drawbacks of OpenShift?

The trade-offs we noted: Real cost is multi-part: Worker minimums, infrastructure, storage, networking, subscriptions and operations exceed the headline unit rate.; Operational burden varies sharply: Self-managed customers own platform and infrastructure, while managed-service responsibility matrices still leave customer duties.; Edition complexity: Platform Plus, Container Platform, Kubernetes Engine, Virtualization Engine and cloud services bundle different capabilities..

When should you not use OpenShift?

Skip OpenShift if: A handful of simple applications do not justify a minimum multi-node cluster and platform team; The budget treats the advertised reserved vCPU rate as the complete production price; The team has not selected an edition and documented the exact provider/customer responsibility matrix.