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
7.5
Number of Reviews
37
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 May 2025, in the Container Management category, the mindshare of Google Kubernetes Engine is 2.1%, down from 3.0% compared to the previous year. The mindshare of Komodor is 3.5%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management
 

Featured Reviews

Immánuel Fodor - PeerSpot reviewer
The auto-scaling feature ensures that we only use resources when needed
The most valuable aspect of Google Kubernetes Engine (GKE) is its managed nature, which significantly reduces the burden on our platform team. Features like auto-scaling are highly beneficial for both handling traffic spikes and optimizing costs. Furthermore, Google's promise of good SLA availability, with the service being available in different locations, adds to its robustness.
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.

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 (GKE) takes care of managing Kubernetes, including the main control plane. It also offers solutions for monitoring resources and handling external traffic, which is essential for us. Being a cloud-native solution, it relieves us from worrying about these operational aspects."
"The most valuable feature of Google Kubernetes Engine is how you can automatically scale and load balance."
"The product’s dashboard is very intuitive."
"The solution simplified deployment, making it more automated. Previously, Docker required manual configuration, often done by developers on their computers. However, with Google Kubernetes Engine, automation extends to configuration, deployment, scalability, and viability, primarily originating from Docker rather than Kubernetes. Its most valuable feature is the ease of configuration."
"I highly recommend it to others due to its comprehensive features and cost-effectiveness for various company sizes."
"The initial setup process is simpler and more user-friendly than other cloud providers."
"The scalability is the best feature."
"The feature that I like the most is the ease of use as compared to AWS. Its ease of use is very high, and I can quickly deploy clusters with a simple template."
"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."
"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 more time we use Komodor the more we save. Currently, we have seen around a ten percent return on investment."
"Komodor's multi-cluster centralized event timeline is the most valuable feature."
"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

"The user interface is a bit confusing sometimes. You need to navigate between the various consoles we have. It's hard to figure out where things are. It's frustrating. The documentation could be a bit better."
"The user interface could be improved."
"One of the things I missed a bit is the visibility and availability of solutions. If I compare it to a different solution, it is a bit behind."
"The console for this solution could be improved because it is very limited."
"There is room for improvement in this solution. For example, auto-scaling can be complex. We expect it to be easier to set up and manage, even for our customers."
"I use the Firebase tool with GKE and it would be helpful if the solution can give notifications when we reach the budget limit."
"The network configuration has to be simplified."
"Our critique is that we have to do too much work to get the cluster production-ready."
"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."
"Komodor's visibility could be improved."
"I like the alerts that Komodor provides, but I think the alert interface could be 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."
"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

"The product is a little bit expensive."
"Initially, Google Kubernetes Engine was a little bit cheaper, but now its prices have been increased compared to the pricing model and the features that are made available by its competitors."
"The solution's price is reasonable."
"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."
"Pricing is a bit expensive compared to some other products, but it's acceptable."
"It is competitive, and it is not expensive. It is almost competitive with AWS and the rest of the cloud solutions. We are spending around 3K USD per month. There are four projects that are currently running, and each one is incurring a cost of around 3K USD."
"We are planning to use external support, and hire a commercial partner for it."
"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."
"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."
"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."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
850,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
12%
Retailer
9%
Manufacturing Company
7%
Wellness & Fitness Company
22%
Computer Software Company
15%
Comms Service Provider
8%
Recreational Facilities/Services Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Google Kubernetes Engine?
The on-demand nodes are quite expensive, so we now use spot machines.
What needs improvement with Google Kubernetes Engine?
Gemini could be more integrated with Google Kubernetes Engine ( /products/google-kubernetes-engine-reviews ). For example, it would be helpful if I could easily find log information in a particular...
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 is your experience regarding pricing and costs for Komodor?
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...
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 ...
 

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: April 2025.
850,028 professionals have used our research since 2012.