Red Hat OpenShift Container Platform

Commercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.

  • AWS
  • Azure
  • Google Cloud
  • Alibaba Cloud
  • IBM Cloud
Customer-operated Servers / containers Commercial Only

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    OpenShift installation on AWS, Azure, Google Cloud or IBM Cloud; Assisted Installer Technology Preview on Alibaba Cloud

  2. Operated by

    Your team

    Customer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOpenShift installation on AWS, Azure, Google Cloud or IBM Cloud; Assisted Installer Technology Preview on Alibaba Cloud
InfrastructureServers / containers
OpenShift Container Platform runs persistent control-plane and worker nodes plus integrated cluster operators and storage services in the customer cloud.
Licensing modelCommercial Only
The selected self-managed OpenShift Container Platform edition is delivered through a commercial Red Hat subscription with entitlement and support terms.
LicenseCommercial Red Hat OpenShift subscription.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The 4.20 Authentication Operator supports an external OIDC identity provider using authorization-code flow, discovery and mapped claims. This authenticates platform users; applications running on the cluster need their own identity integration. Review browser/CLI token workflows and selected provider compatibility.

OpenShift 4.20 platform-user OIDC through the integrated OAuth service · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

Red Hat documents installer-provisioned AWS infrastructure using the release-matched openshift-install tool, install configuration, pull secret and cloud credentials. Customer-managed networking and permissions require review. Use the entitled Red Hat release distribution; the upstream installer source alone is not the product entitlement.

OpenShift Container Platform 4.20 AWS installer path · Source ↗ · Deployment artifact ↗ (Upstream installer source; obtain matching Red Hat release tooling and pull secret) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The 4.20 AWS installation matrix gives bootstrap/control-plane minima of 4 vCPUs, 16 GB RAM and 100 GB disk, and compute nodes 2 vCPUs, 8 GB and 100 GB. A standard cluster uses multiple control-plane and worker machines; workload pods, operators, storage, bootstrap and HA capacity are additional.

OpenShift 4.20 per-machine installation floors, not complete workload sizing · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Self-managed subscriptions can use core-pairs or bare-metal nodes. On hyperscaler VMs, one core-pair covers four vCPUs; aggregate compute-node entitlement and support level must be sized. AI accelerators may require separate subscriptions. Obtain the applicable order and price.

Red Hat self-managed OpenShift Container Platform subscription guide · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

This entry covers self-managed OpenShift Container Platform, not OpenShift Dedicated, ROSA, Azure Red Hat OpenShift or other managed services. The installer can provision infrastructure or integrate with customer-provisioned resources; review credential scope, subscription entitlements and lifecycle support before installation. The documented Alibaba Cloud Assisted Installer path is Technology Preview, outside Red Hat production SLAs and not recommended for production.

Category fit

Backend platforms
Provides a self-managed Kubernetes application platform with integrated operators, developer workflows, networking, registry and cluster services.
DevOps
Provides platform engineering, build, deployment and operations workflows for applications across customer-managed clusters.

Compare within Backend platforms

  • Appwrite Self-HostedSelf-hosted backend services for authentication, databases, storage, functions and messaging.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Gravitee API Management Self-HostedOpen-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Hasura GraphQL Engine v2GraphQL API engine that exposes connected databases through permission-aware application APIs.
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • KeystoneJS (Keystone 6)Self-hosted content backend with a configurable GraphQL API and administration interface.
    • Northflank
    Customer-operated · Open Source / Open Core
  • Kong Gateway Self-ManagedOpen-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Medplum Self-HostedOpen-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Parse ServerNode.js application backend for data APIs, users, permissions and server-side application logic.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Heroku
    Customer-operated · Open Source / Open Core

Showing 8 of 11 other listings in Backend platforms. These products address related workflows; read their category-fit notes before comparing scope. See all of Backend platforms →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.

      Red Hat's current installation overview explicitly distinguishes self-managed OpenShift Container Platform and documents installer- and user-provisioned installation paths on AWS, Microsoft Azure and Google Cloud using customer accounts and credentials.

    • Self-managed OpenShift on IBM Cloud ↗ · IBM Cloud

      Vendor / upstream documentation · Reviewed 2026-11-15 · Version: 4.21. Vendor support commitment: not assessed; confirm the selected release and contract.

      Red Hat documents installer-provisioned deployment into customer IBM Cloud infrastructure, including account IAM/API keys, region selection, VPC networking and cluster administration.

    • OpenShift on Alibaba Cloud — Technology Preview ↗ · Alibaba Cloud

      Vendor / upstream documentation · Reviewed 2026-11-15 · Version: 4.21 Technology Preview. Vendor support commitment: not assessed; confirm the selected release and contract.

      Red Hat documents Assisted Installer deployment using customer Alibaba Cloud OSS images, ECS machines, VPC and DNS. This 4.21 path is Technology Preview: outside production SLAs, potentially incomplete and not recommended by Red Hat for production.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory