We performed a comparison between Heroku and OpenShift based on real PeerSpot user reviews.
Find out in this report how the two PaaS Clouds solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We use Heroku to run generic data. We also use it for our customer development environment. It helps us to build and test websites."
"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."
"I like the tool's scalability, CLI, and dashboards."
"What I found most valuable about this solution is that it's easy to use and integrate with GitHub actions."
"The platform is very Node.js-friendly, which is something that is important to us."
"Thanks to Heroku, we don't need to do as much direct management in AWS."
"The most valuable feature of Heroku is the continuous integration and applications it provides."
"We want to build a solution that can be deployable to any cloud because of client requirements and OpenShift allows us to do this."
"The most valuable feature is the auto scalers for all microservices. The feature allows us to place request limits and it is much cheaper than AWS."
"We are able to operate client’s platform without downtime during security patch management each month and provide a good SLA (as scalability for applications is processed during heavy client website load, automatically)."
"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."
"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."
"The stability has been good."
"OpenShift offers more stability than Kubernetes."
"Great integration with Jenkins for constant integration and development. Supports all the major languages and environments - PHP, Java, Node.js, Ruby, etc."
"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."
"They could flesh out some of their analytics a little more."
"We have to do daily restarts of some processes, which is annoying, and the support for custom CI could be better."
"We would like to be notified when something goes wrong in the process. When something is not working, we should get an alert."
"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."
"The tool's configuration is complex."
"Their support is good, but they can improve their response time."
"The solution needs to support the new features in Kubernetes more quickly."
"The monitoring part could be better to monitor the performance."
"I want easier node management and more user-friendly scripts for installing master and worker nodes."
"The software-defined networking part of it caused us quite a bit of heartburn. We ran into a lot of problems with the difference between on-prem and cloud, where we had to make quite a number of modifications... They've since resolved it, so it's not really an issue anymore."
"The interface could be simplified a bit more."
"We want to see better alerting, especially in critical situations requiring immediate intervention. Until we go to the dashboard, it can be challenging to quickly recognize that there's an issue for us to deal with. Therefore, a popup of the event or a tweaked GUI to catch our attention when it's alerting would be a welcome change. Everything else is good. We don't need any additional features. From the operations perspective, as an administrator, there is nothing concerning."
"Not a ten because it's not a standard solution and the endpoint protection user has to prepare with documentation or have training from other people. It's not easy to start because it's not like other solutions."
"Credential not hidden, so people on the same group can view it."
Heroku is ranked 13th in PaaS Clouds with 27 reviews while OpenShift is ranked 4th in PaaS Clouds with 53 reviews. Heroku is rated 8.4, while OpenShift is rated 8.4. The top reviewer of Heroku writes "Useful for mobile and web applications, and helps with rapid development cycle ". On the other hand, the top reviewer of OpenShift writes "Provides us with the flexibility and efficiency of cloud-native stacks while enabling us to meet regulatory constraints". Heroku is most compared with Microsoft Azure, Google Cloud, Google App Engine, Pivotal Cloud Foundry and Amazon Lightsail, whereas OpenShift is most compared with Amazon AWS, Pivotal Cloud Foundry, Microsoft Azure, Google Cloud and SUSE Cloud Application Platform. See our Heroku vs. OpenShift report.
See our list of best PaaS Clouds vendors.
We monitor all PaaS Clouds reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.