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
48
Ranking in other categories
Container Security (13th)
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 April 2025, in the Container Management category, the mindshare of Amazon EKS is 13.8%, up from 13.5% compared to the previous year. The mindshare of Komodor is 3.0%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management
 

Featured Reviews

Venkatramanan C.S. - PeerSpot reviewer
Amazon EKS: Why It Shines, Where It Struggles, and How It Can Improve
* EKS incurs an additional management fee ($0.10 per hour per cluster) along with EC2 or Fargate costs.May be expensive for smaller workloads compared to alternatives like AWS ECS.Requires expertise to configure and manage Kubernetes resources effectively.Networking (e.g., setting up VPCs, subnets, and service endpoints) can be complex.Simplifies managing multiple Kubernetes clusters, especially for organizations with hybrid or multi-region setups.Integrated dashboards for Kubernetes metrics, logs, and traces.Simplifies observability without needing third-party tools.
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.

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 features of Amazon EKS are its scalability features."
"The most valuable features of Amazon EKS are its auto scaling ability and the ability for service discovery."
"The scalability has really helped us a lot in enhancing the customer experience and ensuring quick results."
"We haven't faced any major issues in one and a half years of use."
"The solution has very good basic features."
"The most important aspect of Amazon EKS is that it is easy to set up and very easy to upgrade."
"It is a scalable solution."
"It has always helped me. It is the repository where we store our images...The microservices appear to be well-made, and I don't have any comments on them as I don't see any flaws."
"Komodor's multi-cluster centralized event timeline is the most valuable feature."
"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."
"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."
 

Cons

"I would like Amazon EKS to be easier to configure on various environments like Windows or Linux installations"
"Improvement is needed in reducing the complexity of using EKS. While services like EC2 are user-friendly, EKS and ECS present a steep learning curve with significant responsibilities."
"I encountered problems with the product’s documentation."
"They need to work on the Amazon plugins on the Kubernetes cluster."
"I would like to see a cloud setup bank management feature."
"The solution's graphical interface is not the best."
"I'd like to see the solution add a service catalog."
"It's difficult to connect to some of the clusters."
"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 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 like the alerts that Komodor provides, but I think the alert interface could be improved."
"Komodor's visibility could be improved."
"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."
 

Pricing and Cost Advice

"The product is available at such a huge scale in the market since the resources that are offered under the tool are competitively priced and available at a much cheaper rate compared to other solutions."
"Amazon EKS is not a cheap solution."
"The product pricing depends on the specific requirements."
"Amazon EKS is expensive."
"The solution is pricey. The tool's pricing is monthly."
"Cloud based pay-as-you-go pricing"
"The solution is quite costly and developers will start exploring other solutions or moving their workloads to other clouds if costs aren't reduced."
"The tool's pricing is good."
"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."
"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.
845,406 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
23%
Computer Software Company
15%
Comms Service Provider
7%
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?
I do not have specific details on EKS's pricing and licensing compared to other services. However, in general, deploying in the cloud offers lower latency and high availability and reduces manual i...
What needs improvement with Amazon EKS?
* EKS incurs an additional management fee ($0.10 per hour per cluster) along with EC2 or Fargate costs.May be expensive for smaller workloads compared to alternatives like AWS ECS.Requires expertis...
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: March 2025.
845,406 professionals have used our research since 2012.