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
12th
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 February 2025, in the Container Management category, the mindshare of Komodor is 1.5%, up from 0.3% compared to the previous year. The mindshare of Kubernetes is 4.9%, down from 10.2% 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.
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

"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 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."
"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."
"I like Kubernetes' scalability, built-in redundancy, and ease of deployment."
"The most valuable feature of Kubernetes is its support for load balancing."
"The autoscaling feature is the most valuable. Kubernetes itself is an orchestration tool. It automatically detects the load, and it automatically spins up the new Pod in the form of a new microservice deployment."
"With the use of our blueprint, my experience with the initial setup has been a ten out of ten where one is difficult and ten is easy."
"The most valuable feature of Kubernetes is the integration with other solutions, such as Formative and Grafana."
"The most valuable feature is the Zero Touch Operations, which involves a new way of performing operations and support. We do not have to do maintenance, the operations are very simple."
"Kubernetes allows us to update without downtime and to easily deploy new software, which is very beneficial for our operations."
 

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."
"Security could be improved. It would be helpful if there were other security modules built into Kubernetes."
"The front end is very rudimentary."
"The pricing could be improved. It would be ideal if it was a bit less."
"The solution has some issues regarding availability during high loads. Worker nodes are sometimes unavailable, affecting the overall availability of the applications. This is a bug or underlying problem with the tool, and Azure and other providers are looking into improving this by releasing new versions of Kubernetes that fix some of the platform's issues."
"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."
"They need to focus on more security internally."
"One area where Kubernetes could improve is troubleshooting. The current process for troubleshooting and installation can be challenging, especially with a large ecosystem. Better tools and artificial intelligence capabilities developed to assist with troubleshooting, configuration, and support would be helpful. This improvement would be particularly beneficial for large enterprise customers."
"We would to have additional features related to security within the API, instead of needing to install add-ons."
 

Pricing and Cost Advice

"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."
"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."
"The solution is affordable."
"Microsoft provides reasonable costs for Kubernetes."
"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."
"There are no licensing fees."
"We use the solution's open-source version."
"If you're using a public cloud, the cost depends on the number of nodes you are planning to deploy Kubernetes on."
"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"
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
838,713 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Wellness & Fitness Company
23%
Computer Software Company
15%
Recreational Facilities/Services Company
9%
Comms Service Provider
6%
Computer Software Company
18%
Financial Services Firm
13%
Government
8%
Manufacturing Company
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: January 2025.
838,713 professionals have used our research since 2012.