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

Amazon EKS 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

Amazon EKS
Ranking in Container Management
2nd
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
49
Ranking in other categories
Container Security (14th)
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 Amazon EKS is 13.0%, down from 13.5% 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

Rock Wang - PeerSpot reviewer
Managing complex environments effortlessly while focusing on growth
The most beneficial aspect of Amazon EKS is that it helps manage the Kubernetes master node, so I don't need to maintain the master node, including tasks like upgrading. This allows me to focus on business code. If using services like Fargate, I only need to maintain my workload, simply uploading code that will be deployed to the Kubernetes cluster. This is especially beneficial for startup companies that lack the technical resources to manage the Kubernetes cluster. Furthermore, Amazon EKS allows me to utilize Kubernetes cluster-level expansion. If there’s insufficient resource on a machine, the cluster can automatically expand to add new nodes.
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.

Quotes from Members

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

Pros

"It's a faster solution to adopt on native applications."
"It's the best option for medium or large enterprises."
"The most valuable feature is the computing speed."
"Amazon EKS is very scalable."
"The solution's Autoscaler option allows for an increase in worker notes whenever particular thresholds are exceeded."
"EKS provides autoscaling functionality."
"The solution is easy to use."
"The scalability has really helped us a lot in enhancing the customer experience and ensuring quick results."
"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 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."
"The more time we use Komodor the more we save. Currently, we have seen around a ten percent return on investment."
 

Cons

"I would like to see a warm-up time for AWS Fargate, similar to what GCP Cloud Run has."
"There is room for improvement in making Amazon EKS less error-prone when writing on the YAML file."
"I'm having difficulty getting my AWS clusters to communicate with my local machine."
"The main thing to improve with Amazon EKS is the price. However, these services can be very expensive. For example, in countries like Turkey, the cost is too high. That's why we offer our cloud solutions locally. We developed hybrid solutions, but their prices are still very high."
"I would like to see a cloud setup bank management feature."
"The graphical user interface could be better."
"The solution should include a popup for clusters so that all relevant information is visible at the bottom of a page."
"The solution's graphical interface is not the best."
"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."
"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 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."
 

Pricing and Cost Advice

"The solution's pricing is fair enough and a little less costly."
"Amazon EKS’s pricing is ok compared to its competitors."
"The tool's pricing is good."
"Amazon EKS is quite pricey, but the functionality it provides is worth it."
"The price can be a problem for small-sized businesses."
"The product pricing depends on the specific requirements."
"The solution is pricey. The tool's pricing is monthly."
"My company paid for the license."
"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."
"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."
"As far as I can recall, the licensing cost was fair."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
13%
Manufacturing Company
7%
Insurance Company
6%
Wellness & Fitness Company
21%
Computer Software Company
16%
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 do you like most about Amazon EKS?
The product's most valuable features are scalability, observability, and performance.
What is your experience regarding pricing and costs for Amazon EKS?
We are making a significant effort to transform our usage of Amazon EKS, which was previously rated as eight or nine in terms of cost. Now, it stands at six or seven due to optimizing our workload.
What needs improvement with Amazon EKS?
I would like to see improvements in the management capabilities that are native to AWS ( /products/amazon-aws-reviews ) for Amazon EKS. Our current use involves using a different tool to administer...
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

Amazon Elastic Kubernetes Service
No data available
 

Overview

 

Sample Customers

GoDaddy, Pearson, FICO, Intuit, Verizon, Honeywell, Logicworks, RetailMeNot, LogMeIn, Conde Nast, mercari, Trainline, Axway
Information Not Available
Find out what your peers are saying about Amazon EKS vs. Komodor and other solutions. Updated: April 2025.
851,604 professionals have used our research since 2012.