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

Amazon OpenSearch Service vs Stackify 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 Application Performance Monitoring (APM) and Observability
29th
Ranking in Log Management
17th
Average Rating
7.6
Reviews Sentiment
6.7
Number of Reviews
13
Ranking in other categories
Search as a Service (3rd)
Stackify
Ranking in Application Performance Monitoring (APM) and Observability
62nd
Ranking in Log Management
56th
Average Rating
7.8
Number of Reviews
6
Ranking in other categories
IT Infrastructure Monitoring (68th)
 

Mindshare comparison

As of November 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Amazon OpenSearch Service is 0.8%, down from 1.8% compared to the previous year. The mindshare of Stackify is 0.8%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Mindshare Distribution
ProductMindshare (%)
Amazon OpenSearch Service0.8%
Stackify0.8%
Other98.4%
Application Performance Monitoring (APM) and Observability
 

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.
Moses Arigbede - PeerSpot reviewer
Head of DevOps at Partsimony
Easy to set up with great custom dashboards but needs to improve non-.NET infrastructure
They need to improve non-.NET infrastructure. We always had difficulty when it comes to reporting or metrics that come from Linux operating systems and Docker containers. For anything that runs within the Unix environment, we always had problems with them, however, if it was a document-based application, Stackify was 100%, it gave everything. Now, the aggregation agent, the metric agent for Stackify for Linux, collects everything. When I say everything, I mean, everything. It collects so much information that we now started to term it as useless data as all that ingestion will just come in and overwhelm your log retention limit for the month and really this spike up your cost at the end of the month. You'll need to do a lot in order to train down the data coming in from all your Linux environments, to get to what you really need, which actually takes some time as well. I would like to be able to see metrics about individual running containers on the host machines. Stackify has not really gotten that right, as far as I'm concerned. Netdata has done a better job and New Relic has also done a better job. They need to improve on that. We need to be able to see the individual resource usage of containers running within a particular host.

Quotes from Members

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

Pros

"Our customers have seen tangible benefits from Amazon OpenSearch Service, especially in terms of their applications running smoothly, so they do get a return on investment."
"In case there is a failure, Elastic manages everything well, and there no major downtime."
"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."
"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"
"It's a good log management platform. In terms of infrastructure management, it's good."
"The customer service is excellent, rated nine out of ten."
"The stability of the product is good."
"The business analytics capabilities are the most important feature it provides."
"It is very simple and very easy to configure."
"Within few hours of install we've identify the source of issue we've been investigating for few days and couldn't pin point."
"My advice to anyone who wants to use Stackify is to go for it because my experience with it is good."
"We switched from New Relic and Loggly as it provides us more info at a lower price."
"The solution is stable and reliable."
"The performance dashboard and the accurate level of details are beneficial."
"What stood out to us were the metrics and granular details we received."
"The deployment is very fast."
 

Cons

"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."
"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."
"Amazon Elasticsearch can improve the bullion in the near search and the ease of integration with Kibana. Additionally, there could be more flexibility in the configuration and documentation."
"As a user, lower prices or reasonable pricing is always better."
"The price is fair yet leans towards the expensive side. I'd rate it five out of ten with respect to capabilities vs. cost."
"One improvement I would like to see is support for auto-scaling."
"The configuration should be more straightforward because we had to select a lot of things."
"They can enhance data visualization."
"I'm looking to see more performance tools, but heard that they are going to release some."
"It should be easily scalable and configurable in different instances."
"One thing that happens as a new user on Stackify is when you install the agent it pulls everything and if you're not careful, your log allowance will just be exhausted as you are actually pulling too much data."
"It's not easy to set up. It's hard especially for juniors to understand."
"Another improvement would be the agent memory utilization, which led to our recent reevaluation."
"The search feature could be improved."
"I've not used Stackify for a while, and I'm currently using a solution now that's not as good as Stackify. Among the solutions I've been using so far, Stackify has been one of the best for me, but there's always room for improvement. For example, I don't know if it's just me, but when I try to get the log from Stackify, sometimes it doesn't appear in real-time. It takes a few minutes before the logs appear. When I redeploy my solution and the application starts, I don't see the logs immediately, and it would take two to three minutes before I see the logs. I don't know if other customers have a similar experience. It's the wait time for the logs to appear that's a concern for me, could be improved, and is what the Stackify team should be looking into. In terms of any additional feature that I'd like added to the solution, I'm not sure if Stackify has a way to export logs out. I've been trying to do it. On the solution, you can click on a spiral-like icon and it shows you the entire error, and I'd prefer an export button that would let me download the error and save that into a text file, for example, so it'll be available on my local machine for me to reference it, especially because the log keeps going and as you're using the solution, the system keeps pushing messages on to Stackify, so if I'm looking at a particular error at 12:05 PM, for example, by the time I go back to my system and would like to revisit the error at 12:25 PM, on Stackify, the logs would have gone past that level and I won't see it again which makes it difficult. When you now go back to that timestamp, you don't tend to see it immediately, but if the solution had an export feature for me to save that particular error information on my local machine for reference at a later time, I won't have to go back to Stackify. I just go to that log, specifically to that particular export that I've received on my local machine. I can get it and review it, and it would be easier that way versus me going back to Stackify to find that particular error and request that particular information."
"I would like to be able to see metrics about individual running containers on the host machines."
 

Pricing and Cost Advice

"You only pay for what you use."
"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."
"The price is variable. It depends on how much data we have received in that particular month. Usually, it goes up to $2,000, or, at times, $3,000 USD per month."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability 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%
Comms Service Provider
21%
Construction Company
19%
Outsourcing Company
8%
Performing Arts
6%
 

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 Business3
Midsize Enterprise2
Large Enterprise2
 

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 ...
Ask a question
Earn 20 points
 

Also Known As

Amazon Elasticsearch Service
No data available
 

Overview

 

Sample Customers

VIDCOIN, Wyng, Yellow New Zealand, zipMoney, Cimri, Siemens, Unbabel
MyRacePass, ClearSale, Newitts, Carbonite, Boston Software, Children's International, Starkwood Media Group, Fewzion
Find out what your peers are saying about Amazon OpenSearch Service vs. Stackify and other solutions. Updated: October 2026.
922,942 professionals have used our research since 2012.