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

HashiCorp Nomad 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

HashiCorp Nomad
Ranking in Container Management
15th
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
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 June 2025, in the Container Management category, the mindshare of HashiCorp Nomad is 2.9%, up from 1.9% compared to the previous year. The mindshare of Komodor is 4.1%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management
 

Featured Reviews

Zeeshan Akhtar - PeerSpot reviewer
Has out of the box features , which is good for companies that don't want to spend too much time on research
I've noticed a few UI issues. For example, when monitoring services and tasks, sometimes the tasks keep disconnecting. If you open the shell in HashiCorp Nomad using the exit button, it often disconnects, and you have to log in again. Sometimes, when I check the logs in the UI for microservices tasks, I encounter an issue where the logs are not visible. However, if I log in again after some time, refresh the page, or check a different container, the logs usually appear. These logs are being generated, as I can see them being shipped to my LogView. I'm not sure if this is a product issue or something related to our deployment, but I've noticed it.
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

"If you face an issue with an image during deployment, the solution will automatically revert to the last stable image."
"You could get most of HashiCorp Nomad's features from other microservice orchestrators like Kubernetes. The tool's advantage is its ease of use and integration with services like Envoy. With Kubernetes, you must think about many things, like UI integration, which vault to use, and how to discover the service. With the tool, many things come out of the box, making it easy to start. For example, using the Ingress proxy with the tool is quite easy, while it's trickier with Kubernetes."
"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 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 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."
"Komodor's multi-cluster centralized event timeline is the most valuable feature."
 

Cons

"I've noticed a few UI issues. For example, when monitoring services and tasks, sometimes the tasks keep disconnecting. If you open the shell in HashiCorp Nomad using the exit button, it often disconnects, and you have to log in again. Sometimes, when I check the logs in the UI for microservices tasks, I encounter an issue where the logs are not visible. However, if I log in again after some time, refresh the page, or check a different container, the logs usually appear. These logs are being generated, as I can see them being shipped to my LogView. I'm not sure if this is a product issue or something related to our deployment, but I've noticed it."
"It would be good to have a UI interface so that developers could receive notifications for jobs in a bad state."
"I like the alerts that Komodor provides, but I think the alert interface 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."
"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."
 

Pricing and Cost Advice

Information not available
"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."
"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."
"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."
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
18%
Financial Services Firm
17%
Government
9%
Comms Service Provider
8%
Computer Software Company
16%
Wellness & Fitness Company
13%
Comms Service Provider
10%
Media Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Questions from the Community

What needs improvement with HashiCorp Nomad?
Sometimes, the job is in a bad state, and we don't get any notifications. It would be good to have a UI interface so that developers could receive notifications for jobs in a bad state.
What is your primary use case for HashiCorp Nomad?
We use HashiCorp Nomad mainly to deploy our images in the form of jobs. It is also used for load balancing, containerization, and instance deployment.
What advice do you have for others considering HashiCorp Nomad?
I would recommend HashiCorp Nomad to other users because it is the best tool for deployment. It is easy for a beginner to learn to use HashiCorp Nomad for the first time. Any developer with a decen...
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 ...
 

Comparisons

 

Overview

Find out what your peers are saying about HashiCorp Nomad vs. Komodor and other solutions. Updated: June 2025.
856,873 professionals have used our research since 2012.