Try our new research platform with insights from 80,000+ expert users

Pivotal Cloud Foundry vs Red Hat OpenShift comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 28, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Pivotal Cloud Foundry
Ranking in PaaS Clouds
13th
Average Rating
7.6
Reviews Sentiment
6.7
Number of Reviews
15
Ranking in other categories
No ranking in other categories
Red Hat OpenShift
Ranking in PaaS Clouds
3rd
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
62
Ranking in other categories
Server Virtualization Software (10th), Container Management (11th), Hybrid Cloud Computing Platforms (6th), Agile and DevOps Services (1st)
 

Mindshare comparison

As of October 2025, in the PaaS Clouds category, the mindshare of Pivotal Cloud Foundry is 8.9%, down from 9.0% compared to the previous year. The mindshare of Red Hat OpenShift is 11.6%, down from 11.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
PaaS Clouds Market Share Distribution
ProductMarket Share (%)
Red Hat OpenShift11.6%
Pivotal Cloud Foundry8.9%
Other79.5%
PaaS Clouds
 

Featured Reviews

Vasundhara  Joshi - PeerSpot reviewer
Seamlessly scalable since applications written in Java and .NET do not create issues for its users
Regarding the setup phase, every step is a hurdle. With Pivotal Cloud Foundry, I won't get any proper resources for that. Even if I Google it, there is no proper solution for Pivotal Cloud Foundry. However, if we go for Azure or some other cloud, we can get a lot of information. I believe there is not much information for Pivotal Cloud Foundry since it may be some license issue. If you go for Azure, the migration process is straightforward. Since we have been given 10 GB of space in the public cloud, we are utilizing it in our company. So, we are trying to deploy our application on the cloud, and for us, it is like a trial process for now. From our total application rate, I can say that only two to three percent is on Pivotal Cloud Foundry. Currently, half of the code is in the shell script, which is causing issues. Also, most people in my organization have worked on Java-related code. For most of the applications, they are using the same, that is, shell script and AUTOsist, and so we haven't migrated yet. So that is the reason that we are planning to opt for a hybrid model so that we don't have to migrate completely to Pivotal Cloud Foundry.
Pratul Shukla - PeerSpot reviewer
Adopting a flexible and efficient approach with noticeable improvements in operational costs and continued challenges in job management
Currently, one of the biggest challenges we face is with services and jobs. For spawning batches, although it has crons, it is not easy to integrate with enterprise systems such as Autosys. The entire company uses Autosys, but we are not able to integrate it effectively. We need intermediate servers to run OC utility commands and initiate the cron job. We have to do a lot of modifications to ensure our batches work properly. With physical or virtual servers, even in AWS, we are able to write and manage multiple jobs. Managing batches in Red Hat OpenShift has been a significant challenge. Integrating third parties is a challenge with Red Hat OpenShift. For example, with Elasticsearch, onboarding itself was difficult, running file beats and dealing with routing issues. It is not straightforward, especially since we have some components in AWS as. AWS has many capabilities that come out of the box and are easier to work with compared to Red Hat OpenShift. Red Hat OpenShift's biggest disadvantage is they do not provide any private cloud setup where we can host on our site using their services. The main reason we went with Red Hat OpenShift was because it is a private cloud, and we have regulatory requirements that prevent us from using public cloud.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature of the solution is its ability to scale. The services that connect to the database are also very good."
"The most valuable features are the monitoring and the deployment is easier."
"The solution is stable and resilient. In our company, we do not even see any challenges with the solution."
"The most valuable feature of Pivotal Cloud Foundry is auto-healing and the plenty of other features that are provided."
"Stability is not a concern with this product."
"PCF is open, so the applications run really smoothly and with little downtime."
"It supports CI/CD, and is integrated with the CI/CD very well."
"It provides a set of developer-friendly tools that simplify application deployment."
"The scalability of OpenShift combined with Kubernetes is good. At least from the software standpoint, it becomes quite easy to handle the scalability through configuration. You need to constantly monitor the underlying infrastructure and ensure that it has adequate provisioning. If you have enough infrastructure, then managing the scalability is quite easy which is done through configuration."
"Valuable features include time to market, avoiding vendor lock-in, and the ease of working in a multi-cloud environment."
"Overall, the solution's security throughout the stack and software supply chain is excellent."
"This solution is providing a platform with OOTB features that are difficult to build from scratch."
"We have found the cluster management function to be very good with this product."
"This solution helps us to account for peak seasons involving higher demand than usual. It also gives us confidence in the security of our overall systems."
"Scaling and uptime of the applications are positives."
"Two stand-out features are the security model and value-add features that don't exist in Upstream Kubernetes."
 

Cons

"Something that can be done better is canary deployment. So, right now, we're using blue-green deployment. The support for canary deployment would be nice."
"Pivotal Cloud Foundry doesn't have certain advanced features."
"Pivotal Cloud Foundry could improve the documentation. They are good, but they could improve more. Additionally, it would be beneficial if there were more use case examples."
"In the next release, they should offer additional applications for the databases, and improve the deployment experience."
"I'd like to see a larger service offering."
"Pivotal Cloud Foundry is not scalable, infinitely, because when you install it on a set of virtual machines it is very hard to scale. It's easy to scale on an application level, but not it is not similar to if you were using Amazon. Amazon you can scale thousands of applications."
"It is not straightforward to setup."
"The Pivotal Cloud Foundry's initial setup has a learning curve for my team, but it was easy to use."
"There is no orchestration platform in OpenShift."
"OpenShift can improve monitoring. Sometimes there are issues. Additionally, the solution could benefit from protective tools if something was to happen in our network."
"This is a fairly expensive solution."
"The speed of deploying new applications can be improved."
"It would be great if it supported Bitbucket repositories too."
"Credential not hidden, so people on the same group can view it."
"The GUI could have more capabilities, particularly around virtualization."
"One of the features that I've observed in Tanzu Mission Control is that I can manage multiple Kubernetes environments. For instance, one of my lines of business is using OpenShift OKD; another one wants to use Google Anthos, and somebody else wants to use VMware Tanzu. If I have to manage all these, Tanzu Mission Control is giving me the opportunity to completely manage all of my Kubernetes clusters, whereas, with OpenShift, I can only manage a particular area. I can't manage other Kubernetes clusters. I would like to have the option to manage all Kubernetes clusters with OpenShift."
 

Pricing and Cost Advice

"The pricing is on the higher side and there are cheaper options available."
"You're paying for the number of virtual machines you want to install in the installation."
"The price of Pivotal Cloud Foundry is based on the customer's requirements. However, the price is comparable to other similar solutions."
"We do pay for the licensing cost because we have opted for a private cloud setup. So, it is a cloud setup, and we have to make payments based on the cloud size. I do not consider it very costly when comparing it to the market."
"Licensing is on a monthly basis and right now we pay $24/month. There are no other costs over and above that."
"The price of Pivotal Cloud Foundry could improve. However, in this category of solutions, they are all expensive."
"The product’s pricing is expensive."
"OpenShift is really good when we need to start, but once we get to a certain scale, it becomes too expensive."
"It's expensive. It may be cheaper to invest in building Vanilla Kubernetes, especially if security is not the number one motivation or requirement. Of course, that's difficult, and in some business areas, such as banking, that's not something you can put as a second priority. In other situations, a Vanilla Kubernetes with a sufficiently strong team can be cheaper and almost as effective."
"My company makes payments towards the licensing costs attached to OpenShift."
"The cost is quite high."
"We had a Red Hat Enterprise Linux (RHEL) license for all our servers' operating systems. By having multiple Red Hat products together, you can negotiate costs and leverage on having a sort of enterprise license agreement to reduce the overall outlay or TCO."
"The pricing is standard; the solution isn't particularly expensive or affordable."
"The licensing cost for OpenShift is expensive when compared to other products. RedHat also charges you additional costs apart from the standard licensing fees."
report
Use our free recommendation engine to learn which PaaS Clouds solutions are best for your needs.
868,787 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
37%
Manufacturing Company
17%
Insurance Company
6%
Computer Software Company
4%
Financial Services Firm
28%
Manufacturing Company
10%
Computer Software Company
9%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Large Enterprise11
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise4
Large Enterprise40
 

Questions from the Community

Which would you recommend - Pivotal Cloud Foundry or OpenShift?
Pivotal Cloud Foundry is a cloud-native application platform to simplify app delivery. It is efficient and effective. The best feature is how easy it is to handle external services such as database...
How does OpenShift compare with Amazon AWS?
Open Shift makes managing infrastructure easy because of self-healing and automatic scaling. There is also a wonderful dashboard mechanism to alert us in case the application is over-committing or ...
What do you like most about OpenShift?
OpenShift facilitates DevOps practices and improves CI/CD workflows in terms of stability compared to Jenkins.
What needs improvement with OpenShift?
Currently, one of the biggest challenges we face is with services and jobs. For spawning batches, although it has crons, it is not easy to integrate with enterprise systems such as Autosys. The ent...
 

Also Known As

PCF, Pivotal Application Service (PAS), Pivotal Container Service (PKS), Pivotal Function Service (PFS)
No data available
 

Overview

 

Sample Customers

Humana, Citibank, Mercedes Benz, Liberty Mutual, The Home Depot, GE, West Corp, Merrill Corporation, CoreLogic, Orange, Dish Network, Comcast, Bloomberg, Internal Revenue Service, Ford Motor Company, Garmin, Volkswagen, Solera, Allstate, US Air Force, Lockheed Martin, Boeing, ScotiaBank
UPS, Cathay Pacific, Hilton
Find out what your peers are saying about Pivotal Cloud Foundry vs. Red Hat OpenShift and other solutions. Updated: September 2025.
868,787 professionals have used our research since 2012.