Try our new research platform with insights from 80,000+ expert users

Google Kubernetes Engine vs Komodor comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 13, 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

Google Kubernetes Engine
Ranking in Container Management
10th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
39
Ranking in other categories
No ranking in other categories
Komodor
Ranking in Container Management
13th
Average Rating
8.8
Reviews Sentiment
9.0
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2025, in the Container Management category, the mindshare of Google Kubernetes Engine is 2.1%, down from 2.4% compared to the previous year. The mindshare of Komodor is 4.0%, up from 0.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management Market Share Distribution
ProductMarket Share (%)
Google Kubernetes Engine2.1%
Komodor4.0%
Other93.9%
Container Management
 

Featured Reviews

Parthasarathy T - PeerSpot reviewer
Managed solutions enable efficient handling of web applications and migration projects
Google Kubernetes Engine can be improved by enabling the in-place upgrade of the machine type of an existing node pool since I currently need to destroy and recreate it. There is no feature present where I can upgrade directly, and having more than 1,000 to 2,000 workloads in one node pool makes changing the node pool name difficult for all those workloads. I choose eight out of ten mainly because of the node pool upgrade challenge I mentioned, but also because of the existence of Anthos service mesh, which is the ingress controller available only for the enterprise Kubernetes Engine. It would be beneficial if it could be offered in the normal Kubernetes Engine with any limitations.
Jacek Kisynski - PeerSpot reviewer
Makes it easier for our development team to "own" Kubernetes, saving our SRE team time
There's nothing in particular that is wrong with Komodor. It's hard to say that there's something we would really like to see improved. 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. I would like to see if we're utilizing nodes in the cluster, if pod allocation is optimal, how much idling we have, and whether we scale up and down efficiently. I would like to see them help us optimize costs further. Because, as our company grows and our clusters get busier and busier, any inefficiency is a lot of money wasted. That's definitely high on our wish list: anything that helps us track wasted resources. I am looking forward to using AI-powered troubleshooting workflow that Komodor unrolled recently.

Quotes from Members

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

Pros

"Google Kubernetes Engine has positively impacted my organization in migration-based projects such as on-prem to GCP and AWS to GCP, as we migrated more than thousands, even 10,000s workload in Google Kubernetes Engine."
"Stability is perfect for me."
"The most valuable aspect of Google Kubernetes Engine (GKE) is its managed nature, which significantly reduces the burden on our platform team."
"On the tip of a command, you can scale in or scale out, and it offers every robust platform to implement DevOps processes for your automation solutions. The product fully supports the IaC concept."
"I am satisfied with the stability offered by the solution."
"We appreciate that it is quite easy to set up a Kubernetes cluster in Google Cloud, using the managed services within this solution."
"Google Kubernetes Engine's most valuable feature is container deployment."
"I highly recommend it to others due to its comprehensive features and cost-effectiveness for various company sizes."
"The more time we use Komodor the more we save. Currently, we have seen around a ten percent return on investment."
"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."
"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."
"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."
"Komodor's multi-cluster centralized event timeline is the most valuable feature."
 

Cons

"I have created a couple of issues with Google tech support, and I am not satisfied with the assistance I received."
"Google Kubernetes Engine's cost should be improved because it is high."
"The console for this solution could be improved because it is very limited."
"The solution does not have a visual interface."
"The primary area for improvement would be the complexity involved when working with Google Kubernetes Engine, especially when using Terraform."
"The network configuration has to be simplified."
"Google Kubernetes Engine is less stable in some highly complex deployments with many nodes."
"t is not very stable."
"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."
"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."
"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 like the alerts that Komodor provides, but I think the alert interface could be improved."
 

Pricing and Cost Advice

"The pricing for GKE is dependent on the type of machine or virtual machine (VM) that is selected for the nodes in the cluster. There is a degree of flexibility in choosing the specifications of the machine, such as the number of CPUs, GPUs, and so on. Google provides a variety of options, allowing the user to create the desired cluster composition. However, the cost can be quite steep when it comes to regional clusters, which are necessary for high availability and failover. This redundancy is crucial for businesses and is required to handle an increase in requests in case of any issues in one region, such as jumping to a different region in case of a failure in the Toronto region. While it may be tempting to choose the cheapest type of machines, this may result in a limited capacity and user numbers, requiring over-provisioning to handle additional requests, such as those for a web application."
"I would rate Kubernetes' pricing four out of five."
"The price for Google Kubernetes Engine could be lower - I'd rate its pricing at three out of five."
"Pricing is a bit expensive compared to some other products, but it's acceptable."
"We are planning to use external support, and hire a commercial partner for it."
"I rate the product's price a six on a scale of one to ten, where one is low price and ten is high price. The product is competitively priced."
"I would rate the solution's pricing a nine out of ten. The tool costs around 3000 dollars per month. There are no additional costs apart from these."
"Currently, it costs around $1000 per month which sorted our deployment. So once we get more clients, having a huge suffix, costs can go up."
"As far as I can recall, the licensing cost was fair."
"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."
"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."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
869,566 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
25%
Computer Software Company
10%
Retailer
8%
Manufacturing Company
6%
Computer Software Company
15%
Comms Service Provider
11%
Media Company
8%
Wellness & Fitness Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business20
Midsize Enterprise6
Large Enterprise15
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Google Kubernetes Engine?
My experience with pricing, setup cost, and licensing for Google Kubernetes Engine is straightforward, as I previously indicated. The need for humans is reduced with GCP since there is no need for ...
What needs improvement with Google Kubernetes Engine?
Google Kubernetes Engine can be improved by enabling the in-place upgrade of the machine type of an existing node pool since I currently need to destroy and recreate it. There is no feature present...
What do you like most about Komodor?
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...
What needs improvement with Komodor?
There's nothing in particular that is wrong with Komodor. It's hard to say that there's something we would really like to see improved. I hope that the cost analytics and resource usage allocation ...
What is your primary use case for Komodor?
We are an HR analytics company, and we do a lot of data processing. Our customers send us their HR-related data, and we process it so that we can run analytics on it. We process it on Kubernetes cl...
 

Also Known As

GKE
No data available
 

Overview

 

Sample Customers

Philips Lighting, Alpha Vertex, GroupBy, BQ
Information Not Available
Find out what your peers are saying about Google Kubernetes Engine vs. Komodor and other solutions. Updated: September 2025.
869,566 professionals have used our research since 2012.