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 June 2025, in the Container Management category, the mindshare of Komodor is 4.1%, up from 0.3% compared to the previous year. The mindshare of Kubernetes is 5.4%, down from 8.7% 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 scanning and support network."
"Kubernetes provides scalable clustering for containers and other means of deployment."
"I am impressed with the product's coupling of resources and flexibility."
"The scalability seems quite good."
"I like that it gives you all the flexibility, for example, auto-scaling. Everything is figured out exactly right. It manages all your workloads without much intervention. It can scale in, scale out, and with security. Everything looks pretty good compared to the old legacy way of working."
"The solution is easy to use."
"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."
"Kubernetes is highly valuable for its node-based setup, which allows for the running of multiple pods."
 

Cons

"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."
"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."
"The front end is very rudimentary."
"We faced a challenge while migrating and upgrading versions of Kubernetes. After the upgrade, some pods were not up as expected, leading to downtime."
"There is room for improvement in this area, as Kubernetes could benefit from having more integrations, such as for scanning vulnerabilities."
"It would be nice if they could make it easier for developers and infrastructure staff to automate some of the pieces that they have to do manually at the moment."
"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."
"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 preparation."
"One feature I would actually like to see is the network monitoring part. When we talk about communities, it's mostly the computer side. But it does have some enhancements on the networking side which they have recently released. I would like to see more enhancement where we can monitor the networks of the Kubernetes cluster or the Kubernetes workloads."
"Kubernetes can be complicated to understand. Improved documentation would help in gaining scalable knowledge and making it more understandable."
 

Pricing and Cost Advice

"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."
"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."
"I would say the solution is worth the money, but it depends on the required workloads, the type of workload, and the scaling requirements etc."
"Google Kubernetes Engine is free in the simplest setup, AWS Kubernetes Engine costs about $50 (depending on the region), in a three master setup, so it's almost the same as the cost of the EC2 instances and it's totally fine from my point of view."
"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."
"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."
"Kubernetes is an open-source solution that can be free. We have some distribution with licenses, such OpenShift and Tucows in Amazon. They are billing services."
"There are no licensing fees."
"Kubernetes is open source and is an orchestration platform. It is a cost effective solution and its pricing depends on your company and how you use it"
"Kubernetes is free; it's open-source software."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
856,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Wellness & Fitness Company
13%
Comms Service Provider
10%
Media Company
7%
Computer Software Company
15%
Financial Services Firm
13%
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 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 ...
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.
856,873 professionals have used our research since 2012.