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

Komodor vs Kubernetes 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

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
Kubernetes
Ranking in Container Management
4th
Average Rating
8.6
Reviews Sentiment
7.1
Number of Reviews
78
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2025, in the Container Management category, the mindshare of Komodor is 4.3%, up from 0.3% compared to the previous year. The mindshare of Kubernetes is 5.5%, down from 8.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management
 

Featured Reviews

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.
Venu Boddu - PeerSpot reviewer
Manage infrastructure automation and smooth application deployment with robust auto-scaling capabilities
Kubernetes is highly valuable for its node-based setup, which allows for the running of multiple pods. This feature is essential for infrastructure automation and application deployment. Kubernetes also offers rollback control and auto-scaling capabilities, which are crucial for maintaining an application's availability even if nodes or pods go down. Additionally, Kubernetes supports load balancing to distribute traffic efficiently across multiple pods.

Quotes from Members

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

Pros

"The more time we use Komodor the more we save. Currently, we have seen around a ten percent return on investment."
"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 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."
"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."
"The most valuable feature of Kubernetes is its support for load balancing."
"We use it for various large microservice-based architectures and web services. That's the ideal use case, but it's suitable for any kind of service that can be decomposed and needs to be scaled. Of course, it's much easier to deploy services that are stateless. It"
"The scalability seems quite good."
"The auto-repair function in Kubernetes is perfect. When something breaks, the auto-repair function automatically repairs it. If you are running the content in Kubernetes, you have a good set up. You do not need to do anything for the management of this. So, the automation of Kubernetes is number one."
"A good interface, better than comparable solutions."
"It's really scalable and efficient for resource management."
"The most valuable aspect of the solution is the scalability."
"If you're switching from VMs to Kubernetes, you will see a return because you can pack more into the Kubernetes architecture using containers rather than VMs. You'll see some more savings on your infrastructure, as well."
 

Cons

"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."
"I like the alerts that Komodor provides, but I think the alert interface could be improved."
"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."
"We faced a challenge while migrating and upgrading versions of Kubernetes."
"Management features could be simplified."
"I would rate the stability as five out of ten. If any containers take more space, sometimes the cluster goes down."
"We faced a challenge while migrating and upgrading versions of Kubernetes. After the upgrade, some pods were not up as expected, leading to downtime."
"Lacks some scalability and more user-friendly operability."
"Kubernetes could adopt UI-based approach. A UI-based approach would be really useful in the CI/CD pipeline. They should make everything a little bit more user-friendly. For example, when I'm deploying, it would be nice to load my code and be able to see which components need to be connected."
"The user-interface in regards to the other solution can be improved."
"Kubernetes is a complex solution. The product needs to be more manageable and user-friendly."
 

Pricing and Cost Advice

"As far as I can recall, the licensing cost was fair."
"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."
"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."
"The price of Kubernetes could be lower. However, it is less expensive than VMware Tanzu. Additionally, technical support is expensive. The overall cost of the solution is approximately $1,000 annually."
"There are no licensing fees."
"If you're using a public cloud, the cost depends on the number of nodes you are planning to deploy Kubernetes on."
"It's an affordable solution"
"The solution requires a license to use it."
"The solution itself is open-source, so there is no cost attached to it. However, it requires a virtual machine to operate, which does come at a cost; a choice of a pay as you go model, or a monthly charge via an enterprise agreement. There is a pricing calculator available, where organizations can determine the level and number of virtual machines required, and how much that will cost."
"The management layer is free, which is perfect. You don't need to pay money for the management layer, but in AWS develop service, you need to pay. I think it is €75 per month for the management layer. It is free here, so you can have as many Kubernetes clusters as you need. You are paying just for the workload, that is, for the machine, CPU, memory, and everything."
"Kubernetes is open-source. Kubernetes is free, but we're charged for AWS utilization."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
861,390 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
18%
Wellness & Fitness Company
10%
Comms Service Provider
10%
Media Company
7%
Computer Software Company
14%
Financial Services Firm
12%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

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...
What do you like most about Kubernetes?
There are many good features. I feel that the scale-out features, like replica sets, are very good. The number of running containers can be autoscaled.
What is your experience regarding pricing and costs for Kubernetes?
Since we use Kubernetes on-premises, the costs are related to our expertise and the personnel we hire.
What needs improvement with Kubernetes?
Although we face issues when migrating to new versions of Kubernetes, such as misunderstandings on using new features or integration with proxy services, these issues can be addressed with proper p...
 

Also Known As

No data available
K8
 

Overview

 

Sample Customers

Information Not Available
China unicom, NetEase Cloud, Nav, AppDirect
Find out what your peers are saying about Komodor vs. Kubernetes and other solutions. Updated: June 2025.
861,390 professionals have used our research since 2012.