No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon OpenSearch Service vs Devo comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Feb 22, 2026

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 OpenSearch Service
Ranking in Log Management
17th
Average Rating
7.6
Reviews Sentiment
6.7
Number of Reviews
13
Ranking in other categories
Application Performance Monitoring (APM) and Observability (29th), Search as a Service (3rd)
Devo
Ranking in Log Management
21st
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
30
Ranking in other categories
Security Information and Event Management (SIEM) (16th), IT Operations Analytics (7th), AIOps (17th)
 

Mindshare comparison

As of November 2026, in the Log Management category, the mindshare of Amazon OpenSearch Service is 1.2%, down from 2.7% compared to the previous year. The mindshare of Devo is 1.4%, up from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management Mindshare Distribution
ProductMindshare (%)
Amazon OpenSearch Service1.2%
Devo1.4%
Other97.4%
Log Management
 

Featured Reviews

Md. Shahariar Hossen - PeerSpot reviewer
Senior Software Engineer at Cefalo
Event tracking has become smoother and data analytics provide clear insights for user actions
Amazon OpenSearch Service is not providing the processing feature directly. From Amazon OpenSearch Service, we are actually maintaining the AWS SQS, the queue service, which is responsible for providing information about what data has to be modified. So using that SQS, we're actually providing it, but we're not directly using Amazon OpenSearch Service for keeping data to other data pipeline thing. So far we didn't use it for any machine learning purposes, but in future, we have plans to extend or implement this feature. Since AWS itself is secure and Amazon OpenSearch Service is a part of this entire ecosystem, it becomes much easier for security purposes. From the validation point of view, Amazon OpenSearch Service itself provides easy to communicate APIs and up-to-date documents, which is much beneficial. For example, if I'm missing anything, I can directly go and check the documentation. That is actually much easier. I would rate it as really good so far. It's much faster. For our local machine, we can also use a kind of replica of Amazon OpenSearch Service just for development purposes. That is another good feature. I would say for the encryption thing and also the user access control management, it's much faster. For some of these hashing algorithms, it also worked really well so far. To be honest, I didn't find any places where it can be improved. However, I think they could provide more abstraction. For example, still for searching, we have to write down the queries in a specific manner, such as for a specific JSON structure or in a specific way. Otherwise, they don't provide us the actual results. For at least this purpose, I think abstraction could be a bit easier or a bit improved. Other than that, right now there is the age of AI, so some kind of prompting could also work, but I'm not sure how it could be integrated. As a user, lower prices or reasonable pricing is always better. Those can be improved as well. However, it is good that most of the services including Amazon OpenSearch Service actually provide pay as you go pricing. So if there were a bit lower version or a bit less payment methodology, it might be much better.
Usama Khan - PeerSpot reviewer
Team Lead Soc at a tech services company with 51-200 employees
Advanced threat hunting has improved SOC visibility and now supports faster incident response
Devo can improve in how its connectors enhance integration with third-party tools. Devo's architecture works by having you deploy a relay server in the data center of the client side and Devo SIEM is basically on the AWS cloud. There are specific ports which are enabled on the relay server, which are 514 and 13000, 13151, 152. However, when we talk about databases and custom integrations, there are not default ports in the relay server. No default ports are defined. For JDBC drivers, the port number is 1433, but it is not in the relay server. You have to add it manually. For Oracle RDBMS, the port is 1521, and it is also not there by default. I would appreciate more third-party integrations including Fortinet and others. Machine learning models can also be improved. Playbooks in the SOAR can also be improved. Regarding playbooks for automation, we utilize playbooks for automation in SOAR for automated IOC blocking on a firewall, on a web application firewall, on DNS security, etc. The only option for us to run the playbook is to schedule the job for it. However, if I want to manually run the playbook, there is no option for doing so. This needs improvement.

Quotes from Members

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

Pros

"The stability of the product is good."
"Amazon OpenSearch Service has enhanced our organization's ability to store and search large amounts of data efficiently."
"The initial set up is very easy...We really appreciate Amazon!"
"They have the good documentation in the help text and that is the reason the Amazon Elasticsearch is the perfect solution for the current market."
"We retrieve historical data with just a click of a button to move it from cold to hot or warm because it's already stored in the backend storage"
"I would definitely recommend Amazon OpenSearch Service to other professionals due to its fast and reliable search capabilities."
"It's actually easier to collaborate since it is already deployed in the AWS cloud itself."
"Regarding valuable features of the solution, we found with the process, which we have used in both cases where we used the solution that while you're seeing the streaming of data, you can analyze in the initial phase what sort of data you are streaming and whether it is valuable."
"Devo is simpler and easier for beginners because the data ingestion is more streamlined and it includes a visual query interface, whereas Splunk is more complex but also more flexible."
"The ROI has been great as we could launch it in a few months instead of a couple of years, and when you put all the costs together, it is less to have done it than with the open source approach."
"The strength of Devo is not only in that it is pretty intuitive, but it gives you the flexibility and creativity to merge feeds. The prime examples would be using the synthesis or union tables that give you phenomenal capabilities... The ability to use a synthesis or union table to combine all those feeds and make heads or tails of what's going on, and link it to go down a thread, is functionality that I hadn't seen before."
"When we show the people who are in charge of getting funding that we saved this number of man-hours, which correlates to this number of dollars, they're more willing to fight to get that funding for the next fiscal year."
"The most valuable feature is definitely the ability that Devo has to ingest data. From the previous SIEM that I came from and helped my company administer, it really was the type of system where data was parsed on ingest. This meant that if you didn't build the parser efficiently or correctly, sometimes that would bring the system to its knees. You'd have a backlog of processing the logs as it was ingesting them."
"The Hyperstream engine and real-time alerting help my team by leveraging a stream-oriented architecture that minimizes latency during data ingestion."
"In traditional BI solutions, you need to wait a lot of time to have the ability to create visualizations with the data and to do searches. With this kind of platform, you have that information in real-time."
"Devo provides a multi-tenant, cloud-native architecture. This is critical for managed service provider environments or multinational organizations who may have subsidiaries globally. It gives organizations a way to consolidate their data in a single accessible location, yet keep the data separate. This allows for global views and/or isolated views restricted by access controls by company or business unit."
 

Cons

"I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels."
"It would be beneficial to have some level of customization available in the managed service, tailored to the specific use cases of the end users."
"The price is fair yet leans towards the expensive side. I'd rate it five out of ten with respect to capabilities vs. cost."
"I would say that, basically, the configuration part is an area with a shortcoming...Some upgradation is required on the configuration side so that we can get to use it."
"They can enhance data visualization."
"The pricing aspect is a concern. The service is way too costly. For the past month, I used only 30 to 40 MB of data, and the cost was $500. AWS could improve pricing."
"One glaring issue was with our mapping configuration as the system accepted the data we posted, but after a few months, when we attempted complex queries, we realized the date formatting had become problematic."
"As a user, lower prices or reasonable pricing is always better."
"I have not observed a return on investment with Devo in terms of fewer employees needed, money saved, or time saved."
"Some of the documentation could be improved a little bit. A lot of times it doesn't go as deep into some of the critical issues you might run into. They've been really good to shore us up with support, but some of the documentation could be a little bit better."
"An admin who is trying to audit user activity usually cannot go beyond a day in the UI. I would like to have access to pages and pages of that data, going back as far as the storage we have, so I could look at every command or search or deletion or anything that a user has run. As an admin, that would really help. Going back just a day in the UI is not going to help, and that means I have to find a different way to do that."
"There is room for improvement in the ability to parse different log types. I would go as far as to say the product is deficient in its ability to parse multiple, different log types, including logs from major vendors that are supported by competitors. Additionally, the time that it takes to turn around a supported parser for customers and common log source types, which are generally accepted standards in the industry, is not acceptable. This has impacted customer onboarding and customer relationships for us on multiple fronts."
"We only use the core functionality and one of the reasons for this is that their security operation center needs improvement."
"The Activeboards feature is not as mature regarding the look and feel. Its functionality is mature, but the look and feel is not there. For example, if you have some data sets and are trying to get some graphics, you cannot change anything. There's just one format for the graphics. You cannot change the size of the font, the font itself, etc."
"Both response time and support quality need attention."
"Some basic reporting mechanisms have room for improvement."
 

Pricing and Cost Advice

"There is a community edition available and the price of the commercial offering is reasonable."
"The solution is not expensive, but priced averagely, I will say."
"Compared to other cloud platforms, it is manageable and not very expensive."
"You only pay for what you use."
"Devo is definitely cheaper than Splunk. There's no doubt about that. The value from Devo is good. It's definitely more valuable to me than QRadar or LogRhythm or any of the old, traditional SIEMs."
"Devo is a hosted or subscription-based solution, whereas before, we purchased QRadar, so we owned it and just had to pay a maintenance fee. We've encountered this with some other products, too, where we went over to subscription-based. Our thought process is that with subscription based, the provider hosts and maintains the tool, and it's offsite. That comes with some additional fees, but we were able to convince our upper management it was worth the price. We used to pay under 10k a year for maintenance, and now we're paying ten times that. It was a relatively tough sell to our management, but I wonder if we have a choice anymore; this is where the market is."
"The way Devo prices things is based on the amount of data, and I wish the tiers had more granularity. Maybe at this point they do, but when we first negotiated with them, there were only three or four tiers."
"I rate the pricing a four on a scale of one to ten, where one is cheap, and ten is expensive."
"We have an OEM agreement with Devo. It is very similar to the standard licensing agreement because we are charged in the same way as any other customer, e.g., we use the backroom."
"Our licensing fees are billed annually and per terabyte."
"Pricing is based on the number of gigabytes of ingestion by volume, and it's on a 30-day average. If you go over one day, that's not a big deal as long as the average is what you expected it to be."
"It's a per gigabyte cost for ingestion of data. For every gigabyte that you ingest, it's whatever you negotiated your price for. Compared to other contracts that we've had for cloud providers, it's significantly less."
report
Use our free recommendation engine to learn which Log Management solutions are best for your needs.
922,942 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
10%
Computer Software Company
8%
Outsourcing Company
7%
Financial Services Firm
16%
Outsourcing Company
11%
Construction Company
10%
Manufacturing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise2
Large Enterprise4
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise6
Large Enterprise15
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon OpenSearch Service?
I would consider the pricing as a six based on how much data we are handling; if we handle minimal data, it's cheap, but for large data, it becomes costly. Our clients usually pay between $1,00...
What needs improvement with Amazon OpenSearch Service?
Amazon OpenSearch Service is not providing the processing feature directly. From Amazon OpenSearch Service, we are actually maintaining the AWS SQS, the queue service, which is responsible for prov...
What is your primary use case for Amazon OpenSearch Service?
Amazon OpenSearch Service is a user-friendly version of Elasticsearch, as per my understanding. I have been using it for our volunteer management system where around 5,000 to 6,000 users are using ...
What is your experience regarding pricing and costs for Devo?
The pricing could be simpler, and while the initial setup cost for a new instance is a bit expensive, the licensing can currently be user-based or driven by log volume, which is better if there is ...
What needs improvement with Devo?
In terms of improvements, I think Devo falls short with their support model, as they rely mainly on their support team in Spain. Although they do have a support team in North America, they lack kno...
What is your primary use case for Devo?
Devo is the bank's centralized log management platform that my team and I rely on the most. For centralized log management in our day-to-day work, one of the biggest data users would be our Red...
 

Also Known As

Amazon Elasticsearch Service
No data available
 

Overview

 

Sample Customers

VIDCOIN, Wyng, Yellow New Zealand, zipMoney, Cimri, Siemens, Unbabel
United States Air Force, Rubrik, SentinelOne, Critical Start, NHL, Panda Security, Telefonica, CaixaBank, OpenText, IGT, OneMain Financial, SurveyMonkey, FanDuel, H&R Block, Ulta Beauty, Manulife, Moneylion, Chime Bank, Magna International, American Express Global Business Travel
Find out what your peers are saying about Amazon OpenSearch Service vs. Devo and other solutions. Updated: November 2026.
922,942 professionals have used our research since 2012.