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

Google Cloud Run vs NGINX Ingress Controller 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)
NGINX Ingress Controller
Ranking in Container Management
18th
Average Rating
9.6
Reviews Sentiment
5.2
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

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.
MuthukaruppasamyR - PeerSpot reviewer
Senior Network At Dxc Technology Professional at DXC Technology
Reverse proxy and security controls have provided flexible access and strong TLS protection
I have utilized NGINX Ingress Controller SSL and TLS termination feature. We have done extensive SSL offloading on NGINX Ingress Controller and made the TLS configurations to match security requirements, allowing certain TLS versions while disabling others such as 1.0, 1.1, and 1.2, and allowing 1.3. The choice depends upon the application requirement. The reverse proxy capabilities of NGINX Ingress Controller in managing distributed applications is central to its main concept. We need to configure it to allow the server to access the outside world and the internet. That is achievable, and we can install and configure NGINX Ingress Controller as a reverse proxy. It can work as a load balancer, but the main part is NGINX Ingress Controller's role as a reverse proxy. If any applications need to be accessed through the proxy to the outside world, then NGINX Ingress Controller is a good product for you. I employ the IP whitelisting feature in NGINX Ingress Controller, which helps secure my application environment. In IP whitelisting, there are several options available. You can determine which IPs to block, for example, if you do not want to give access to specific regions. You can find the list of IP addresses registered in those regions and blacklist them. There is also the web application firewall (WAF) where you can create policies to identify the type of traffic trying to access the application.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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."
"In Google Cloud Run, we are mainly using the feature where we can directly pull images from Docker Hub."
"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."
"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 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 my organization in numerous ways, such as significant cost efficiency and reduced overhead since we only pay for the resources that we use."
"NGINX Ingress Controller has positively impacted my organization by helping us with exposing our applications and managing security and auto-scaling."
"The main benefit is that it is better in performance, provides security with App Protect and WAF and DDoS, and delivers high performance and high stability."
"However, the response, throughput, and solid performance we receive after implementation are often worth it."
"From my experience, I think the main benefit NGINX Ingress Controller provides to the end user is the reliability of NGINX Ingress Controller itself."
 

Cons

"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."
"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."
"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."
"There are a few areas where Google Cloud Run could improve."
"However, there is still a major limitation in GUI capability to manage and observe."
"Nowadays, the quality has been degrading, and I do not expect the same level of service."
"Most customers are satisfied with the reverse proxy capability, but the main issue is that the Ingress NGINX, the one that is most widely used, will be deprecated this month."
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.
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Large Enterprise3
No data available
 

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 ...
What is your experience regarding pricing and costs for NGINX Ingress Controller?
My experience with pricing, setup cost, and licensing was good. The pricing was expensive at first, but throughout the journey, it became feasible.
What needs improvement with NGINX Ingress Controller?
In my opinion, NGINX Ingress Controller can make better improvements for ingress control, and I think they are already the leader in the Ingress and Gateway API. The Gateway API has the capability ...
What is your primary use case for NGINX Ingress Controller?
I am currently working with NGINX Ingress Controller but in a different perspective than before. We haven't used App Protect anymore, but as an implementer, we use it as a front end for an AI gatew...
 

Also Known As

Google Cloud Functions, Google Run, GCF
No data available
 

Overview

Find out what your peers are saying about Amazon Web Services (AWS), Red Hat, Kubernetes and others in Container Management. Updated: April 2026.
894,738 professionals have used our research since 2012.