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

Heroku vs Red Hat OpenShift comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 15, 2024

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

Heroku
Ranking in PaaS Clouds
13th
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
29
Ranking in other categories
No ranking in other categories
Red Hat OpenShift
Ranking in PaaS Clouds
3rd
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
64
Ranking in other categories
Server Virtualization Software (9th), Container Management (9th), Hybrid Cloud Computing Platforms (5th), Agile and DevOps Services (1st)
 

Mindshare comparison

As of March 2026, in the PaaS Clouds category, the mindshare of Heroku is 3.5%, up from 2.7% 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%
Heroku3.5%
Other88.3%
PaaS Clouds
 

Featured Reviews

Faizan Haider - PeerSpot reviewer
Senior Software Engineer at Aldaim Solutions
Used for server deployment and provides auto maintenance of databases
Heroku is deployed on the cloud. We can deploy our private and public projects over at Heroku. Most of the time, when we are starting any new project from scratch, we have to implement our MVP for that project or the core idea. We are unsure how our traffic flow will go or the actual production environment requirements. We don't want to spend the most on the server sites, so then we can use it with our go-to plan for Heroku, and all the resources are available in the basic plan with the minimum expenses. So, it helps us to deploy and make our features available online at the minimum cost. Once we know our needs, we can add the professional add-ons and shift it to another platform. Heroku supports any resource listed in the marketplace. We just have to deploy our AI solutions, and Heroku can also support AI projects. I would recommend the solution to other users. I advise users not to purchase extra add-ons but to make scalable resources so that they can use all the resources efficiently. Overall, I rate the solution a nine out of ten.
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

"The solution's most valuable feature is the auto maintenance of databases."
"One of the best things about Heroku is that it is very easy and straightforward to deploy an application."
"I like the tool's scalability, CLI, and dashboards."
"It is easy to deploy applications, and we don't need to bother about software updates on the server. We don't need to bother about machines, servers, and hardware. We only need to care about the system and functionality that we need or want to develop. They take care of everything else. It provides high availability. It is a pretty good solution that provides everything that we need. It has everything that we need to run our applications. We have many different applications, and we generate three million bills for a company in Brazil. We see more than a billion requests per day in another application. Everything works just fine, and it is very good."
"What I found most valuable about this solution is that it's easy to use and integrate with GitHub actions."
"The most valuable feature of Heroku is the continuous integration and applications it provides."
"Thanks to Heroku, we don't need to do as much direct management in AWS."
"The product is stable."
"What I like best about OpenShift is that it can reduce some of the costs of having multiple applications because you can just move them into small container applications. For example, applications don't need to run for twenty days, only to be used up by Monday. Through OpenShift, you can move some of the small applications into any cloud. I also find the design of OpenShift good."
"OpenShift facilitates DevOps practices and improves CI/CD workflows in terms of stability compared to Jenkins."
"In terms of implementation, OpenShift is very user-friendly, which is an advantage. We are using it along with GitLab for implementing CI/CD pipelines. That's a feature that other products also have, but in OpenShift, we find it good."
"The concept of containers and scaling on demand is a feature I appreciate the most about Red Hat OpenShift."
"OpenShift is based on Kubernetes and we try to use all the Kubernetes objects of OpenShift. We don't use features that are specific to OpenShift, except internal certificates for the services. The one feature that is missing from Kubernetes and that is really useful in OpenShift is the lifecycle of the cluster and the ease of installation. We use VMware and VMware integration internally with the OpenShift installer, which is very good. With OpenShift it's easy to spin up or scale out a cluster."
"Provides support throughout the whole platform."
"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."
"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. For the developer, this means less time waiting for the provisioning and excellent flexibility for development, testing, and production. Also, in such systems it is easy for developers to monitor applications even after deployment."
 

Cons

"Heroku had an authentication problem a few months ago, but they solved it."
"Heroku should increase its slug size limits."
"The pricing could be improved because scaling the database becomes costly."
"I improved the application performance by monitoring and adjusting the cleaner configuration to help set better lightweight limits on containers that run the app instances."
"Heroku doesn't support Docker images on the CI infrastructure."
"We would like to be notified when something goes wrong in the process. When something is not working, we should get an alert."
"They could flesh out some of their analytics a little more."
"We don't find the pipelines intuitive. The user experience could be better. Having to set up multiple apps, then a pipeline, seems like an overkill on the amount of work to do."
"Support could improve with faster response times, as responses are currently quite slow."
"Room for improvement is around the offerings that come as a bundle with the container platform. The packaging of the platform should be done such that customers do not have to purchase additional licenses."
"I had to frequently upgrade my cluster due to OpenShift's rolling updates every six months, which I found to be excessive."
"There are challenges related to additional security layers, connectivity compliance for endpoints, and integration."
"It could use auto-scaling based on criteria such as transaction volume, queue backlog, etc. Currently, it is limited to CPU and memory."
"Documentation and technical support could be improved. The product is good, but when we raise a case with support—say we are having an image issue—the support is not really up to the mark. It is difficult to get support... When we raise a case, their support people will hesitate to get on a call or a screen-sharing session. That is a major drawback when it comes to OpenShift."
"One area for improvement is the documentation. They need to make it a little bit more user-friendly. Also, if you compare certain features and the installation process with Rancher, Rancher is simpler."
"The monitoring part could be better to monitor the performance."
 

Pricing and Cost Advice

"I rate the tool's pricing a three out of ten."
"There is a standard fee for a processing unit, they call them "dynos," and then you pay for add-ons."
"The tool is free."
"The price of Heroku could be less expensive."
"Its price is very good."
"Pricing of OpenShift depends on the number of nodes and who is hosting it."
"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 price depends on the type and the nature of the organizations, along with the types of projects that are of considerable range."
"The pricing is standard; the solution isn't particularly expensive or affordable."
"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."
"My company makes payments towards the licensing costs attached to OpenShift."
"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."
report
Use our free recommendation engine to learn which PaaS Clouds solutions are best for your needs.
883,692 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
9%
University
8%
Comms Service Provider
8%
Financial Services Firm
24%
Manufacturing Company
10%
Computer Software Company
7%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise2
Large Enterprise3
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise4
Large Enterprise43
 

Questions from the Community

What needs improvement with Heroku?
I don't like that the web server crashes every day, every 24 hours. The pricing could be improved because scaling the database becomes costly. The Docker features are not great. You cannot use any ...
What is your primary use case for Heroku?
We use the solution for web applications and web APIs.
What advice do you have for others considering Heroku?
The integration capabilities are great because of the quick integration and the management features. We don't need a lot of expertise and all external DevOps people. Heroku is the easiest platform ...
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 ...
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...
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 is something in the hands of the organization's higher management, especially wh...
 

Overview

 

Sample Customers

Facebook, UrbanDictionary, Code for America, Mailchimp, Rapportive, GitHub, TED, and Lyft.
UPS, Cathay Pacific, Hilton
Find out what your peers are saying about Heroku vs. Red Hat OpenShift and other solutions. Updated: March 2026.
883,692 professionals have used our research since 2012.