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
14th
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.1
Number of Reviews
62
Ranking in other categories
Server Virtualization Software (9th), Container Management (12th), Hybrid Cloud Computing Platforms (6th), Agile and DevOps Services (1st)
 

Mindshare comparison

As of June 2025, in the PaaS Clouds category, the mindshare of Heroku is 3.2%, up from 2.0% compared to the previous year. The mindshare of Red Hat OpenShift is 12.1%, up from 11.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
PaaS Clouds
 

Featured Reviews

Cristian-Molina - PeerSpot reviewer
Has a quick development cycle and continuous integration
The initial setup is straightforward. Heroku integrates well. You only have to push the code, and it automatically deploys the new version. Whether you have permission depends on the application. Currently, I have one application that I deploy myself. I rate the initial setup a nine out of ten, where one is difficult and ten is easy.
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 solution's most valuable feature is the auto maintenance of databases."
"Valuable for us was the fast deployment. This means the time to market is improved without pain for developers."
"It's easy to push a change and to deploy new things."
"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."
"One of the best things about Heroku is that it is very easy and straightforward to deploy an application."
"We use Heroku to run generic data. We also use it for our customer development environment. It helps us to build and test websites."
"Provides support throughout the whole platform."
"The stability has been good."
"This solution is providing a platform with OOTB features that are difficult to build from scratch."
"OpenShift's superior dashboard is a notable strength, especially when compared to Kubernetes."
"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."
"We are currently dealing with both local support and Red Hat support, and they have been amazing."
"The security is good."
"Its security is most valuable. It's by default secure, which is very important."
 

Cons

"We would like to be notified when something goes wrong in the process. When something is not working, we should get an alert."
"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."
"We have to do daily restarts of some processes, which is annoying, and the support for custom CI could be better."
"Heroku doesn't support Docker images on the CI infrastructure."
"Their support is good, but they can improve their response time."
"Heroku had an authentication problem a few months ago, but they solved it."
"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."
"We experienced issues around desktop security, that stopped us implementing a new feature that had been developed."
"The operators need a lot of improvement, with better integrations."
"I think that OpenShift has too many commands for running services from the CLI, and the configuration files are a little complicated."
"Some of the storage services and integrations with third-party tools should be made possible."
"OpenShift could be improved if it were more accessible for smaller budgets."
"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."
"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."
"The product’s integration with Windows containers and other third-party products needs improvement."
 

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."
"Its price is very good."
"The price of Heroku could be less expensive."
"The tool is free."
"The pricing is standard; the solution isn't particularly expensive or affordable."
"The cost is quite high."
"The licensing cost for OpenShift is expensive when compared to other products. RedHat also charges you additional costs apart from the standard licensing fees."
"My company makes payments towards the licensing costs attached to OpenShift."
"We are currently using the open version, OKD. We plan to get the enterprise version in the future."
"The solution is cost-effective."
"OpenShift is really good when we need to start, but once we get to a certain scale, it becomes too expensive."
"The product’s pricing is expensive."
report
Use our free recommendation engine to learn which PaaS Clouds solutions are best for your needs.
856,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
12%
Educational Organization
9%
Comms Service Provider
6%
Financial Services Firm
30%
Manufacturing Company
9%
Computer Software Company
9%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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 do you like most about OpenShift?
OpenShift facilitates DevOps practices and improves CI/CD workflows in terms of stability compared to Jenkins.
 

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: June 2025.
856,873 professionals have used our research since 2012.