No more typing reviews! Try our Samantha, our new voice AI agent.

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 April 2026, in the PaaS Clouds category, the mindshare of Cloud Foundry is 2.1%, up from 1.2% compared to the previous year. The mindshare of Pivotal Cloud Foundry is 6.2%, down from 10.0% compared to the previous year. The mindshare of Red Hat OpenShift is 8.2%, down from 12.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
PaaS Clouds Mindshare Distribution
ProductMindshare (%)
Red Hat OpenShift8.2%
Pivotal Cloud Foundry6.2%
Cloud Foundry2.1%
Other83.5%
PaaS Clouds
 

Featured Reviews

Carlos Bittrich - PeerSpot reviewer
Technology Advisor at Fabrik
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.
reviewer2263239 - PeerSpot reviewer
Head of Engineering at a financial services firm with 10,001+ employees
PCF allows for fine-grained configuration, especially regarding scaling but routing limitations
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. A few things, such as what OpenShift does better are cluster management. Like, you can manage the entire thing together. Currently, it's possible to manage all the clusters, especially when it comes to cluster management using straightforward configuration. As of now, we have to handle each application instance individually, which means servicing them one by one. It would be better if we could perform these actions as a group or in a more streamlined manner. One more downside is actually the cost of this environment. So, major downside of Pivotal, it's the cost. So, the runtime running costs are very high. Extremely high.
Pratul Shukla - PeerSpot reviewer
Vice President at a financial services firm with 10,001+ employees
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

"IBM is the only vendor to offer integration with blockchain for smart contract development."
"By moving to IBM Cloud Foundry, we reduced our project time by a factor of two and decreased costs by a factor of four because it was a PoC."
"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."
"I find the ease of deployment and management of microservices to be the most valuable features. The platform also has good auto-scaling capabilities."
"The most valuable feature of Pivotal Cloud Foundry is the UI, it is easy to use."
"The most valuable feature of Pivotal Cloud Foundry is auto-healing and the plenty of other features that are provided."
"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 feature of Pivotal Cloud Foundry is the UI, it is easy to use."
"The most valuable features are the monitoring and the deployment is easier."
"Pivotal Cloud Foundry is very robust, especially for building Java."
"The solution is stable, and we have not experienced any infrastructure issues, so it is very good and captures a few metrics, onboarding to App Dynamics."
"The solution provides a lot of flexibility to the application team for running their applications in the container platform, without needing to monitor the entire infrastructure all the time. It automatically scales and automatically self-heals. There is also a mechanism to alert the team in case it is over-committing or overutilizing the application."
"Self-provisioning support saves a lot of time and unnecessary work from the system administrator who can use this time to run and monitor the infrastructure."
"I would recommend Red Hat OpenShift, especially for its automation capabilities."
"Security is also an important part of this solution. By default, things are running with limited privileges and securely confined to their own resources. This way, different users and projects can all use the same infrastructure."
"It seems like we're getting a pretty high return on our investment because of our ability to navigate, integrate and migrate across platforms."
"The security features of OpenShift are strong when in use of role-based access."
"Save money and get OpenShift."
"The developers seem to like the source-to-image feature. That makes it easy for them to deploy an application from code into containers, so they don't have to think about things. They take it straight from their code into a containerized application. If you don't have OpenShift, you have to build the container and then deploy the container to, say, EKS or something like that."
 

Cons

"After the initial excitement period with Node-RED is over, you crave the need of additional integrations to third-party services."
"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."
"It is not straightforward to setup."
"In the next release, they should offer additional applications for the databases, and improve the deployment experience."
"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 should offer more security features."
"The user interface should be simpler to navigate because it t can take time for users to learn it."
"Pivotal Cloud Foundry is not scalable, infinitely, because when you install it on a set of virtual machines it is very hard to scale."
"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."
"In the next release, I would like to see easy integration with external tools."
"Needs work on volume handling (although this is already better with GlusterFS). Security (SSSD) would also be an improvement."
"Not a ten because it's not a standard solution and the endpoint protection user has to prepare to use it with documentation or has to get training from other people."
"Installation and setup are a bit tedious, especially in a proxy environment."
"OpenShift can improve monitoring. Sometimes there are issues."
"Managing batches in Red Hat OpenShift has been a significant challenge."
"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."
"Autoscaling is a very unique feature, but it could be useful to have more options based on traffic statistics, for example, via Prometheus. So, there should be more ready solutions to autoscale based on specific applications."
 

Pricing and Cost Advice

"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."
"IBM has a free tier and payment option depending on the products selected."
"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."
"You're paying for the number of virtual machines you want to install in the installation."
"The price of Pivotal Cloud Foundry could improve. However, in this category of solutions, they are all expensive."
"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."
"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 product's support is expensive. I would rate the tool's pricing an eight out of ten."
"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."
"The product has reasonable pricing."
"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."
"This solution is fairly expensive but comes at an average cost compared to other solutions in the market."
"The model of pricing and buying licences is quite rigid. We are in the process of negotiating on demand pricing which will help us take advantage of the cloud as a whole."
"We are currently using the open version, OKD. We plan to get the enterprise version in the future."
"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."
report
Use our free recommendation engine to learn which PaaS Clouds solutions are best for your needs.
885,444 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Manufacturing Company
14%
Energy/Utilities Company
8%
Healthcare Company
6%
Financial Services Firm
36%
Manufacturing Company
14%
Insurance Company
5%
Healthcare Company
4%
Financial Services Firm
23%
Manufacturing Company
10%
Government
7%
Computer Software Company
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 Enterprise43
 

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 needs improvement with OpenShift?
Areas where Red Hat OpenShift can be improved include the licensing being a bit complex and maybe expensive, as that ...
What is your primary use case for OpenShift?
My main use case for Red Hat OpenShift is that we had several security tools that we deployed to Red Hat OpenShift pl...
 

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: March 2026.
885,444 professionals have used our research since 2012.