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 Market Share Distribution
ProductMarket Share (%)
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

"What I found most valuable about this solution is that it's easy to use and integrate with GitHub actions."
"The solution's most valuable feature is the auto maintenance of databases."
"It's easy to push a change and to deploy new things."
"The most valuable feature of Heroku is the continuous integration and applications it provides."
"Valuable for us was the fast deployment. This means the time to market is improved without pain for developers."
"We use Heroku to run generic data. We also use it for our customer development environment. It helps us to build and test websites."
"Thanks to Heroku, we don't need to do as much direct management in AWS."
"The product is stable."
"Key features are WildFly, because it standardizes infrastructure and the git repository and docker. Git is essential for source code and Docker for infrastructure."
"It has features that enhance security, ease of deployment, and service exposure compared to Kubernetes."
"The product's initial setup is very easy, especially compared to AWS."
"OpenShift offers more stability than Kubernetes."
"Excellent GUI support, so one does not need to use the command line client for almost any tasks. Great support for building images directly from Git repositories with hooks."
"I am impressed with the product's security features."
"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."
"We have found the cluster management function to be very good with this product."
 

Cons

"We have to do daily restarts of some processes, which is annoying, and the support for custom CI could be better."
"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 should increase its slug size limits."
"I think this solution would be improved if free demos were available indefinitely."
"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."
"The pricing could be improved because scaling the database becomes costly."
"Their support is good, but they can improve their response time."
"They could work on the pricing model, making it more flexible and possibly lower."
"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."
"Support could improve with faster response times, as responses are currently quite slow."
"The solution needs to support the new features in Kubernetes more quickly."
"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."
"Needs work on volume handling (although this is already better with GlusterFS). Security (SSSD) would also be an improvement."
"The platform's documentation could be more comprehensive to cover the full spectrum of user needs. Sometimes, achieving specific goals is challenging due to a lack of detailed guidance."
"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."
 

Pricing and Cost Advice

"There is a standard fee for a processing unit, they call them "dynos," and then you pay for add-ons."
"I rate the tool's pricing a three out of ten."
"The price of Heroku could be less expensive."
"The tool is free."
"Its price is very good."
"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."
"OpenShift is really good when we need to start, but once we get to a certain scale, it becomes too expensive."
"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 solution is cost-effective."
"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."
"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."
"The pricing for OpenShift includes support and licensing, which costs approximately $400."
"Pricing of OpenShift depends on the number of nodes and who is hosting it."
report
Use our free recommendation engine to learn which PaaS Clouds solutions are best for your needs.
883,044 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
8%
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 do you like most about Heroku?
I like the tool's scalability, CLI, and dashboards.
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.
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,044 professionals have used our research since 2012.