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 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."
"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."
"Kubernetes offers a lot of great features such as scalability and great portability of applications."
"It is a very good solution for deploying microservices in an application. It has a lot of freedom in it, which makes it very interesting. It is also web-enabled. You can run services in other virtual applications and virtual machines."
"I rate Kubernetes nine out of ten."
"I like that it has really boosted cloud-native development and stood the test of time. The underlying architecture allows one to scale as per the business KPIs much faster."
"The ease of use if the solution is a very valuable aspect for us."
"The most valuable feature is that it's a container orchestrator. It has a huge user base and it is easily incorporated into all of the public clouds."
"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."
"Having fast storage classes is very important."
 

Cons

"Komodor's visibility 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."
"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."
"I like the alerts that Komodor provides, but I think the alert interface could be improved."
"The solution could be more stable."
"Kubernetes' VM functionality and security could be improved."
"In the financial service sector, I'd rate scalability an eight out of ten. But do it in a controlled manner, not auto-scaling. If your application has a bug and you enable the autoscaler, it will spike your costs. If someone deploys an application with a bug, that's automatically a problem."
"There are several areas where Kubernetes could improve."
"It's complex to manage and requires specialists."
"Kubernetes should improve its consistency across different types of deployments. My customers tell me that they get much better performance when Kubernetes is deployed on VM versus PaaS services from Azure."
"The tool needs to improve its UI. The tool is very complex and basic."
"The Kubernetes dashboard can be improved. It is currently a mess. We were using Rancher earlier, and everyone was happy with the dashboard. Right now, we are using Kubernetes, and it's not working with Microsoft workstations. We still have problems with the dashboard. It's terrible."
 

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."
"You need to pay for a license if you buy branded products. For example, if you take the services from Azure, AWS, or Google, the price of the Kubernetes cluster is inclusive of the service that's being offered to us on a pay-and-use model."
"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."
"We use the solution's open-source version."
"The solution is open source and has no fees."
"Kubernetes is open source. But we have to manage Kubernetes as a team, and the overhead is a bit high. Compared with the platforms like Cloud Foundry, which has a much less operational overhead. Kubernetes, I have to manage the code, and I have to hire the developers. If someone has a product, a developer should know exactly what he's writing or high availability, and all those things may differ the costs."
"Pricing isn't a major concern for us. Since we resell Kubernetes services and focus on providing support, integration, and education, we don't usually have pricing issues. Our customers are more concerned with getting the right support and services than the cost. So, the value we provide is more important than the actual pricing. Pricing might change in the future, but it’s not a big issue for us right now."
"If you have a solid AKS and a solid DevOps process, you'll automatically get an ROI, not just in terms of cost but also in how quickly you can see your business application progress."
"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."
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.