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

Google Cloud Run vs Komodor 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
14th
Average Rating
8.6
Reviews Sentiment
2.2
Number of Reviews
5
Ranking in other categories
Containers as a Service (CaaS) (5th)
Komodor
Ranking in Container Management
13th
Average Rating
8.6
Reviews Sentiment
6.3
Number of Reviews
8
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Vyas Shubham - PeerSpot reviewer
Senior Quality Analyst at a consultancy with 51-200 employees
Serverless containers have transformed how we deploy microservices and event-driven workloads
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. It also impacts user experience for real-time applications. The improvement we require is faster cold starts or smarter pre-warming options. There are also limitations with long-running workloads. It is not ideal for very long or always-running processes, and request timeouts are somewhat restrictive. The improvement we want is better support for persistent workloads without workarounds. We have also identified improvements needed in debugging and observability complexity because logs and monitoring are available, but they feel scattered at times, and debugging distributed microservices is harder. The improvement we require is more unified and developer-friendly debugging tools.
reviewer2785698 - PeerSpot reviewer
Technical Solutions Engineer at a leisure / travel company with 501-1,000 employees
Unified cloud workloads have become visible and teams manage kubernetes issues efficiently
This is the main task that we use Komodor for, and one additional benefit is that it is also helpful for platform and site reliability engineers to check how many clusters are up and running and how many clusters are accepting the workloads from the users. One of the best features that Komodor offers is Cloud AI, which debugs all the logs and gives the exact root cause for the issue. From there, we know we do not need an engineer who is an expert in Kubernetes to debug the issue. Cloud AI has definitely helped my team by saving time, not in a single instance but in multiple cases where we have used Cloud AI for debugging issues in the Kubernetes pods. Komodor has positively impacted our organization. Since adopting it, all the issues we faced while managing Rancher are gone, and we are seeing 100% availability for Komodor. 100% availability with Komodor means there have been improvements in uptime and productivity. For instance, when application teams want to deploy their applications, if Rancher is not up or running, the deployments usually fail at the deployment stage. In the case of Komodor, there have been no such cases reported after adopting it. We saw 100% uptime most of the time, except for some issues with AWS outages.

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 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."
"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 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."
"Komodor's multi-cluster centralized event timeline is the most valuable feature."
"The service overview is definitely the most valuable feature. With it, I can see all the services and see if they're healthy or not without having to go specifically into each workflow individually. It has been immensely helpful for us whenever we've had network issues or other such issues. We've been able to use Komodor and see at a glance where there might be potential issues."
"For example, if I were taking half an hour to solve an issue, it is now done in ten minutes, so I think fifty to sixty percent of the time has been reduced."
"The most valuable aspect is the speed with which I can narrow down what's going on. Usually, I look at the overview of events and then the timeline of an event and the status of the logs to quickly check what's happening or what has happened."
"For example, instead of spending thirty to sixty minutes jumping between logs and different commands, I can usually define the root cause within a minute by using Komodor timeline."
"Since adopting it, all the issues we faced while managing Rancher are gone, and we are seeing 100% availability for Komodor."
"Overall, Komodor is a very good platform for managing Kubernetes-related infrastructure, and as of now, my experience with Komodor is very positive."
"The event timeline has been super helpful, enabling us to overlay node events in the same timeline as deployment events... That helps an engineer very quickly troubleshoot without having to do too much digging."
 

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."
"There are a few areas where Google Cloud Run could improve."
"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."
"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."
"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."
"I hope that the cost analytics and resource usage allocation areas will see further development. For example, where we can now see if the pods are over- or under-provisioned, I wouldn't mind higher-level development."
"Komodor's visibility could be improved."
"I would like to see improvements in how the product is installed. We've already communicated these things directly to Komodor. One feature we would like to see is for Komodor to be highly available on the clusters. Currently, it's only able to run in one instance within the cluster."
"Perhaps a deeper integration with logs and metrics would help."
"I like the alerts that Komodor provides, but I think the alert interface could be improved."
"I chose a rating of eight because it is good, but there are certain capabilities that it should have."
"One thing we don't have visibility into, which I would love to have, is metrics, such as user logins and usage. It's really hard to know what people are doing when I don't have any metrics on that directly."
 

Pricing and Cost Advice

Information not available
"The licensing model is fine. It is per node, which is good, but the pricing is high. Currently, I am fine with it, but I am a little concerned about the pricing as we scale. So, it is on the higher end. On a scale of one to ten, where ten is the most expensive, Komodor is a seven."
"We pay according to the number of resources we have; if we are a small start-up, we have fewer resources and thus pay less."
"Other options pop up, but Komodor's pricing works well for our use case. It's fair, and we appreciate it. A lot of other vendors price their solutions in a way that would cost us disproportionately more money than they should. Komodor's pricing is reasonable in the way they calculate usage and value."
"As far as I can recall, the licensing cost was fair."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
902,894 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Computer Software Company
12%
Manufacturing Company
9%
Comms Service Provider
9%
Media Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Large Enterprise3
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise5
Large Enterprise2
 

Questions from the Community

What needs improvement with Google Cloud Run?
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. Addit...
What is your primary use case for Google Cloud Run?
In my day-to-day work, I use Google Cloud Run for managing and running cluster and containerized applications on the Google Kubernetes Engine and Google Console. I have created multiple application...
What advice do you have for others considering Google Cloud Run?
If any organization has a lot of load on their Google Kubernetes Engine or on Google Cloud, they can easily switch to Google Cloud Run and should start using it because it will help them in many wa...
What is your experience regarding pricing and costs for Komodor?
I am not involved in the pricing, setup cost, and licensing for Komodor, so someone from my team will take care of that. Compared with Rancher or any other tools, Komodor is priced cheaply and avai...
What needs improvement with Komodor?
Perhaps a deeper integration with logs and metrics would help. Today, I still need to jump to an external tool such as a logging or monitoring platform to fully understand the issue. Although Komod...
What is your primary use case for Komodor?
I use Komodor for troubleshooting the platform, focused on tracking logs and also things like crashes and configuration. We use it in our Kubernetes in the CI/CD pipeline.After a new deployment, so...
 

Also Known As

Google Cloud Functions, Google Run, GCF
No data available
 

Overview

Find out what your peers are saying about Google Cloud Run vs. Komodor and other solutions. Updated: June 2026.
902,894 professionals have used our research since 2012.