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

Google Cloud Run 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:
 

Categories and Ranking

Google Cloud Run
Ranking in Container Management
15th
Average Rating
8.4
Reviews Sentiment
2.2
Number of Reviews
6
Ranking in other categories
Containers as a Service (CaaS) (5th)
Red Hat OpenShift
Ranking in Container Management
7th
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
73
Ranking in other categories
PaaS Clouds (3rd), Server Virtualization Software (6th), Hybrid Cloud Computing Platforms (4th), Agile and DevOps Services (1st)
 

Featured Reviews

AS
Technical Lead at a tech consulting company with 1,001-5,000 employees
Microservices deployment has become faster and cost optimization is driving daily development
While Google Cloud Run does a great job of reducing costs, to mitigate cold starts, users can set minimum instances, but scaling to zero costs has become a cost-saving advantage even when idle, and idle instance costs might occur. This can be avoided because whenever a heavy container causes a cold start, it affects latency and sensitivity of the application. When it starts from idle to full run, it scales slowly, causing slowness in the service deployed; sometimes some of the APIs fail to respond. It is difficult to identify the bug because it is often due to the idleness of the application and not the code, which can be quite frustrating. Additionally, simple tasks for developers who just want to run a few lines of code can be more complex. I would say optimizing concurrency can improve the experience; currently, managing multiple containers in a single Google Cloud Run instance becomes quite difficult, especially tasks such as logging and local proxy monitoring. Google provides fully orchestrated alternatives, but Cloud Run is better for scaling. Slowness in applications is a notable issue.
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

"In Google Cloud Run, we are mainly using the feature where we can directly pull images from Docker Hub."
"Google Cloud Run has positively impacted my organization in numerous ways, such as significant cost efficiency and reduced overhead since we only pay for the resources that we use."
"Google Cloud Run and the Google Cloud environment positively impact my organization by providing almost 99.9% availability for applications, which instills confidence in the organization and users by reducing the dependency on the physical network and allowing access to applications and data."
"Google Cloud Run has positively impacted our organization by saving us five thousand dollars per month based on scheduling our infrastructure from nine p.m. to nine a.m. for shutdown and starting, as well as stopping the MongoDB clusters."
"Google Cloud Run has impacted my organization positively through faster deployment and development, where developers can deploy applications quickly without worrying about infrastructure, push the app live with just containers, speed up time to market significantly, launch features faster and iterate more often, pay only when code runs without maintaining idle servers, reduce cloud costs dramatically for applications with low or unpredictable traffic, automatically scale based on traffic spikes to handle sudden loads without manual intervention so our business does not lose users during peak hours, and let developers focus on business logic instead of DevOps."
"Google Cloud Run is a very good tool that I use for deploying applications; its ease of deployment, auto scaling features, and resource optimization are very nice features that help individuals deploy their apps and solutions into the cloud without any hiccups."
"In a couple of months, we can move from physical infrastructure to a container."
"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."
"The security features of OpenShift are strong when in use of role-based access."
"A smaller cloud running on containers enables easy deployment with the ability to scale up and scale down, and it can host multiple services on the same platform."
"OpenShift offers an easy-to-use graphical user interface for cluster management, making it more accessible for administrators."
"Customer service is perfect."
"The product has helped kick off applications for developers at speed, as new joiners can just start using the platform without bothering to set up an application stack and/or server stack on their local laptop."
"The virtualization of my APIs means I no longer have to pay VMware large amounts of money to only run in-house solutions."
 

Cons

"There are a few areas that could be improved. We have experienced cold start latency because when scaling from zero, the first request is slow."
"When it starts from idle to full run, it scales slowly, causing slowness in the service deployed; sometimes some of the APIs fail to respond."
"There are a few areas where Google Cloud Run could improve."
"If speaking about improvements for Google Cloud Run, I think they could reduce the cold starts and manage to configure a set number of minimum instances to keep the instances in a warm phase."
"One area where Google Cloud Run could be better is the cold start; when a container scales, it starts from zero and takes a moment to boot up before it can serve the request."
"This solution could be improved by offering best practices on standardization and additional guidance on how to use this solution."
"Autoscaling issues. It does not increase in a seamless manner. Sometimes, CPU utilization/Memory utilization exceeds and the application just hangs or gets into HeapSpace or OutOfMemory error."
"While Red Hat OpenShift is stable, monitoring and reporting capabilities need improvement. Integration with tools like Grafana and Prometheus is necessary for capturing logs, and manually managing these aspects is time-consuming."
"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."
"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."
"This solution is fairly expensive but comes at an average cost compared to other solutions in the market."
"The whole area around the hybrid cloud could be improved. I would like to deploy a Red Hat OpenShift cluster on-premise and on the cloud, then have Red Hat do the entire hybrid cloud management."
 

Pricing and Cost Advice

Information not available
"My company makes payments towards the licensing costs attached to OpenShift."
"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 price depends on the type and the nature of the organizations, along with the types of projects that are of considerable range."
"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 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."
"The cost is quite high."
"Depending on the extent of the product use, licenses are available for a range of time periods, and are renewable at the end of the period."
"Pricing of OpenShift depends on the number of nodes and who is hosting it."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
22%
Manufacturing Company
10%
Government
7%
Computer Software Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Large Enterprise3
By reviewers
Company SizeCount
Small Business19
Midsize Enterprise6
Large Enterprise56
 

Questions from the Community

What needs improvement with Google Cloud Run?
While Google Cloud Run does a great job of reducing costs, to mitigate cold starts, users can set minimum instances, but scaling to zero costs has become a cost-saving advantage even when idle, and...
What is your primary use case for Google Cloud Run?
I am mainly using Google Cloud Run for running microservices and its web APIs, creating GraphQL APIs and validation. I also use it for event-driven processing, uploading files into cloud storage, a...
What advice do you have for others considering Google Cloud Run?
Google Cloud Run is something I have worked with and I have experience using it. The platform is very user-friendly, simple, and easy to use. The portability is highly portable. Google handles its ...
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?
Red Hat OpenShift can be improved by addressing any features, performance, or usability issues. In my view, the performance is very good, and the automatization of the new environment and new machi...
 

Also Known As

Google Cloud Functions, Google Run, GCF
No data available
 

Overview

 

Sample Customers

Information Not Available
UPS, Cathay Pacific, Hilton
Find out what your peers are saying about Google Cloud Run vs. Red Hat OpenShift and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.