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

Cloud Foundry vs Pivotal Cloud Foundry vs Red Hat OpenShift comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

Mindshare comparison

As of October 2025, in the PaaS Clouds category, the mindshare of Cloud Foundry is 2.1%, up from 0.6% compared to the previous year. 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%
Cloud Foundry2.1%
Other77.4%
PaaS Clouds
 

Featured Reviews

Carlos Bittrich - PeerSpot reviewer
Quick to deploy but being deprecated by IBM and should be merged with Kubernetes
We enjoy the fast deployment. Cloud Foundry builds the runtime environment directly without requiring dependency management from the developer or administrator. The autoscaling is great. It is just a switch that needs to be turned on, and autoscaling starts working. At this moment, you begin to see different meters about usage that helps you in updating the scaling limits, which help you tune the running instances. Besides this, autoscaling can be scheduled, so in times of low activity, you can have lower limits or increase in advance for special dates. It has good logging. CF has logging events that help identify when a transaction runs and its response time which helps in monitoring execution.
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

"My favorite component of IBM's solution is Node-RED, which greatly shortens the amount of time required to develop, test, and deploy new applications."
"Cloud Foundry builds the runtime environment directly without requiring dependency management from the user."
"IBM is the only vendor to offer integration with blockchain for smart contract development."
"The most valuable feature of the solution is its ability to scale. The services that connect to the database are also very good."
"Pivotal Cloud Foundry is very easy to use compared to other cloud technologies. It has a very good performance."
"We find its stability and scalability valuable."
"It is a scalable product...We are not facing any particular issues since most of the applications in our company are written in Java and .NET."
"The most valuable features of Pivotal Cloud Foundry are its ease of use and the command line interface has the ability to push instances to the cloud easily."
"It provides a set of developer-friendly tools that simplify application deployment."
"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."
"The company had a product called device financing, where the company worked as a partner with Google. It allowed customers to take mobile phones on loan or via credit. When we migrated those services to OpenShift in February last year, we were able to sell over 100,000 devices in a single day, which was very good."
"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."
"OpenShift's superior dashboard is a notable strength, especially when compared to Kubernetes."
"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."
"Great integration with Jenkins for constant integration and development. Supports all the major languages and environments - PHP, Java, Node.js, Ruby, etc."
"The product's initial setup is very easy, especially compared to AWS."
"Its interface is good. The other part is the seamless integration with the stack that I have. Because my stack is mostly of Red Hat, which is running on top of VMware virtualization, I have had no issues with integrating both of these and trying to install them. We had a seamless integration with the other non-Red Hat products as well."
"The concept of containers and scaling on demand is a feature I appreciate the most about Red Hat OpenShift."
 

Cons

"In IBM Cloud, the product has been deprecated in favor of Kubernetes, which is a more complicated infrastructure to manage."
"After the initial excitement period with Node-RED is over, you crave the need of additional integrations to third-party services."
"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."
"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."
"The Pivotal Cloud Foundry's initial setup has a learning curve for my team, but it was easy to use."
"Pivotal Cloud Foundry doesn't have certain advanced features."
"There is a lot of uncertainty surrounding the future of Pivotal Cloud Foundry."
"The user interface should be simpler to navigate because it t can take time for users to learn it."
"I'd like to see a larger service offering."
"It could use auto-scaling based on criteria such as transaction volume, queue backlog, etc. Currently, it is limited to CPU and memory."
"OpenShift requires a very expensive and complex infrastructure. These demands can deter people from learning OpenShift."
"I think that OpenShift has too many commands for running services from the CLI, and the configuration files are a little complicated."
"OpenShift could improve by providing the ability to integrate with public cloud platforms. This way we can easily use the services that these platforms offer. For instance, Amazon AWS. However, all the three major hyper-scalers solutions offer excellent DevOps and CI/CD tooling. If there was an easy way to integrate with them it would be beneficial. We need a way to easily integrate with the monitoring and dashboard services that they provide."
"One glaring flaw is how OpenShift handles operators. Sometimes operators are forced to go into a particular namespace. When you do that, OpenShift creates an installation plan for everything in that namespace. These operators may be completely separate from each other and have nothing to do with each other, but now they are tied at the hip. You can't upgrade one without upgrading all of them. That's a huge mistake and highly problematic."
"My team has found some bugs in OpenShift due to continuous integration, and this is an area for improvement in the platform. RedHat should fix the bugs. Another area for improvement in OpenShift is that upgrading clusters can be challenging, resulting in downtime. Application support also needs improvement in OpenShift because the platform doesn't support all applications in the cloud. I'd like upgraded storage in the next release of OpenShift, especially when I need to do a DR exercise. It would also be good if the platform allows mirroring with another cluster, or more portability in terms of moving applications to another cluster."
"The operators need a lot of improvement, with better integrations."
"We need some kind of a multi-cluster management solution from the Red Hat site."
 

Pricing and Cost Advice

"The pricing models should be reworked to the needs of a wider range of companies. Some customers will not be able to afford it until quite a few years into production, even after good PoC results and a successful launch."
"IBM has a free tier and payment option depending on the products selected."
"You are allocated a minimum amount of resources in the free tier. This seems fair and highly scalable, as you pay per usage as per cloud pricing schemes."
"The price of Pivotal Cloud Foundry could improve. However, in this category of solutions, they are all expensive."
"You're paying for the number of virtual machines you want to install in the installation."
"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."
"The price of Pivotal Cloud Foundry is based on the customer's requirements. However, the price is comparable to other similar solutions."
"The pricing is on the higher side and there are cheaper options available."
"Licensing is on a monthly basis and right now we pay $24/month. There are no other costs over and above that."
"The solution is cost-effective."
"The pricing for OpenShift includes support and licensing, which costs approximately $400."
"The pricing is standard; the solution isn't particularly expensive or affordable."
"The product's support is expensive. I would rate the tool's pricing an eight out of ten."
"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."
"It's important to start small because the solution is scalable. We can build our cluster and look at the bundle option, not the external subscriptions. Talking to the people at Red Hat can save us money."
"I don't deal with the cost part, but I know that the cost is very high when compared to other products. They charge for CPU and memory, but we don't worry about it."
"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.
871,358 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Manufacturing Company
13%
Computer Software Company
11%
Energy/Utilities Company
7%
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
No data available
By reviewers
Company SizeCount
Small Business5
Large Enterprise11
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise4
Large Enterprise40
 

Questions from the Community

Ask a question
Earn 20 points
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....
How does OpenShift compare with Amazon AWS?
Open Shift makes managing infrastructure easy because of self-healing and automatic scaling. There is also a wonderfu...
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 cro...
 

Also Known As

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

Overview

 

Sample Customers

Grape Up, c-Com, KONE, TITAN, CSAA, Bosch, Allstate, Verizon, West Corp., Telstra
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 Microsoft, Amazon Web Services (AWS), Red Hat and others in PaaS Clouds. Updated: September 2025.
871,358 professionals have used our research since 2012.