Earlier quoted context omitted.
It's a well-funded solution to a well-funded problem. Producing platforms for enterprise customers is truly, genuinely difficult. There is enormous variation and complexity between and within customers, which cannot be dismissed easily. Disclosure: I work for VMware, a direct competitor in this space.
Im not knowledgable enough in this area, but I don't understand the value in using Openshift's custom setup over established cloud providers setups like AWS or GCP or Azure or even VMWare(who has been in the vm biz wayyy longer than all of these players.)
The "custom" parts of OpenShift are things you're going to want anyways. They're also optional (to a point) but obviously Supportability will change depending on customer customization. A Container Registry, something to manage your Ingress (we have HAProxy and Ingress Controller), Metrics & Monitoring of containers, pods, and nodes using Prometheus, Grafana, and AlertManager, a logging stack that sucks in your logs from stdout built on Elasticsearch, Fluentd, and Kibana, supported Middleware, Apache Camel, AMQ, Kafk), Java, OpenJDK, JBoss, Tomcat, Spring Boot, node.js, Quarkus, Python, Ruby, PHP stacks, built-in tooling for CI/CD with Jenkins, Tekton. OpenShift can be run almost anywhere that RHEL8 can. We've started down the path of multi-arch supported Kubernetes too, first with IBM Z and others to come. We run OpenShift on Public Clouds, Private Clouds, VMs and Baremetal.