Red Hat OpenShift.io – Free, end-to-end, cloud-native development

Until that question is answered, you have ZERO patience for any marketing you read: especially fluffy visionary commentary about "digital transformation". You are quite literally making your readers angry because you are not answering their questions.

For anyone launching anything:

1. Make the first goal of your homepage just explaining what the thing is. Be clear. Be specific. People just want to know how to reason about it.

2. Show photos, video, or screenshots. (Even if you don't think it's amazingly sexy.) Seeing the product makes it so much more real.

3. Compare it liberally with what's out in the market now: this is your chance to show how it's similar and why it's different. Can be chart or table.

Then and only then, can you move on to how your product improves the lives of devs, chefs, athletes, etc. who uses it. (But you may not even need to.)

All of our work is open on github under the OpenShift Origin project, Kubernetes, and other projects. We push most of changes upstream.

Doing containers at a scale of 10,000+ running containers would be unimaginably hard without something like OpenShift. Clusters of 1,000s of nodes, Security, RBAC throughout our supported tools, optional SCM (git via GOGS), optional integrated local Docker Registry, optional CI/CD (Jenkins), optional build/artifact repo (Nexus), optional basic metrics (Hawkular, Heapster, Cassandra), optional monitoring (CloudForms, Cockpit), optional EFK logging stack, (Elasticsearch, FluentD, Kibana), horizontal autoscaling, support for NFS, NetApp, OpenStack, RHEV, KVM, VMware, AWS, GCE, Azure, Ceph, GlusterFS, BIG-IP F5, iSCSI, FibreChannel, dynamic node provisioning, dynamic storage provisioning, OAuth2 authentication and app integration, LDAP authentication, SAML2 authentication, Okta, auto SDN creation, SDN segregation, application load balancing, multiple encryption flow options, HTTP/2 support, internally secured communications, Ansible integration. For a solution so encompassing, you need something that marks the way. Most of our customers exchange several parts for what they have or what they want.

And we do all of this with Quality as we develop in the open & commit to upstream projects. We spend $100Ks (probably more) on R&D and testing every release (every 3-4 months). The benefits, again, are usually committed upstream. You have Red Hat's award winning Customer Support. I'll personally vouch for our OpenShift Customer Support Teams. Absolutely amazingly talented and insightful engineers from all over the globe.

One of our biggest customer concerns is in integrating customers' code to run on the Platform, aka, the Last Mile of Integration. IMO, OpenShift.io is intended to reduce that barrier. We support just about all the popular languages, frameworks, and platforms. We have examples & templates for Perl, PHP, Python, Ruby, nodejs, Java (Spring Boot, JBoss, xPaaS, FUSE), and even .Net Core, MySQL, PostgreSQL, MongoDB, CouchDB. Figuring out how to integrate legacy CI/CD, monitoring, logging, IDEs, etc. with OpenShift takes the most time. In choosing OpenShift.io, in return, you get an environment that is built from the get-go to work together.