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

Algolia vs Amazon AWS CloudSearch vs Elastic Search comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

Mindshare comparison

As of April 2026, in the Search as a Service category, the mindshare of Algolia is 9.4%, up from 8.5% compared to the previous year. The mindshare of Amazon AWS CloudSearch is 5.3%, down from 9.2% compared to the previous year. The mindshare of Elastic Search is 17.9%, up from 14.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Elastic Search17.9%
Algolia9.4%
Amazon AWS CloudSearch5.3%
Other67.4%
Search as a Service
 

Featured Reviews

Kozykorpesh Tolep - PeerSpot reviewer
software engineer at a non-tech company with 1,001-5,000 employees
Real-time search has improved device monitoring and now needs better relevance tuning and cost clarity
One area for Algolia's improvement is the relevance of tuning and configuration because it can take some time to properly configure ranking and filtering for a specific use case. If you are new to this or do not have experience with the tuning and configuration of the search, that can take some time to adapt and use this search engine. To make it better, I would appreciate improvement in the relevance of tuning and configuration, as it takes time to properly configure ranking and filtering. I can also say that transparency for scaling usage and cost transparency for when you are scaling would be beneficial.
HarishMahanta - PeerSpot reviewer
Sr PeopleSoft Consultant at People Tech
A reasonably priced solution that provides scalability, stability, reliability, and security
In terms of what needs improvement, I would say that it needs to keep its cost competitive in the market, especially in comparison to other clouds. Let's say we have various clouds in the market, like Google Cloud, Oracle Cloud, and AWS Cloud. However, security-wise, I don't think AWS is bad. It's good only, especially in comparison to Oracle Cloud, if you really use Oracle, while also considering the fact that PeopleSoft is an Oracle product. AWS is a separate cloud, and Oracle has its own cloud. If you are in a new PeopleSoft and Oracle and you are using a third-party cloud, it means it is not easy since we can't think it is easy. I mean, if you are using Oracle products and you are using Oracle Cloud, it will be easier for you. However, it has a cost in comparison to AWS. Oracle Cloud is too costly. According to region, we segregate because it depends on the organization's strength. Let's say your organization has 1,000 customers. In that case, on a daily basis, let's say one customer was released or discontinued using the product. Then, you have to remove the solution. However, if you use Oracle Cloud, that space will remain there. In the case of AWS, they will immediately cut down their space, meaning in terms of reuse ability, it will reduce the cost. In our case, AWS is the best in the market, actually. We have various clouds like Google Cloud and Microsoft Azure Cloud, the features of which are very different. There are a lot of features in AWS Cloud since I am not in the market providing service on the products. I am just using that tool to access our clients' database and deliver our day-to-day service. I interact with the clients regarding their issues, whatever they are facing. There is this one kind of interface we use to access things because they are in AWS Cloud. If your customer is in Oracle Cloud, then there will be a different approach to accessing it. In our case, we can use AWS or Oracle, so it doesn't matter to us.
Anurag Pal - PeerSpot reviewer
Technical Lead at a consultancy with 10,001+ employees
Search and aggregations have transformed how I manage and visualize complex real estate data
Elastic Search consumes lots of memory. You have to provide the heap size a lot if you want the best out of it. The major problem is when a company wants to use Elastic Search but it is at a startup stage. At a startup stage, there is a lot of funds to consider. However, their use case is that they have to use a pretty significant amount of data. For that, it is very expensive. For example, if you take OLTP-based databases in the current scenario, such as ClickHouse or Iceberg, you can do it on 4GB RAM also. Elastic Search is for analytical records. You have to do the analytics on it. According to me, as far as I have seen, people will start moving from Elastic Search sooner or later. Why? Because it is expensive. Another thing is that there is an open source available for that, such as ClickHouse. Around 2014 and 2012, there was only one competitor at that time, which was Solr. But now, not only is Solr there, but you can take ClickHouse and you have Iceberg also. How are we going to compete with them? There is also a fork of Elastic Search that is OpenSearch. As far as I have seen in lots of articles I am reading, users are using it as the ELK stack for logs and analyzing logs. That is not the exact use case. It can do more than that if used correctly. But as it involves lots of cost, people are shifting from Elastic Search to other sources. When I am talking about pricing, it is not only the server pricing. It is the amount of memory it is using. The pricing is basically the heap Java, which is taking memory. That is the major problem happening here. If we have to run an MVP, a client comes to me and says, "Anurag, we need to do a proof of concept. Can we do it if I can pay a 4GB or 16GB expense?" How can I suggest to them that a minimum of 16GB is needed for Elastic Search so that your proof of concept will be proved? In that case, what I have to suggest from the beginning is to go with Cassandra or at the initial stage, go with PostgreSQL. The problem is the memory it is taking. That is the only thing.

Quotes from Members

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

Pros

"The Algolia solution really helped us to improve our conversion rate and click-through rate."
"Algolia provides some cool functionalities like filtering, indexing, and searching."
"Algolia has positively impacted our organization by allowing us a faster time to market."
"Algolia has impacted my organization positively in a good way, as it has shaped the product and it feels as though the product has a premium search engine behind it."
"The tool is easy to use, but you need to know how it works."
"We were working with search products, brands, and different attributes specific to the product; it's faster and easier. The implementation is easy."
"It's scalable. It can be scaled massively."
"The tool is worth the money, and I have seen an ROI."
"It's the best solution for any company; it has a hosting ERP system for any task, AWS is stable, more flexible with its elastic concept, and also very secure with many layers of hardware and software security."
"It will remain alive in the market. The solution will be stable in the market."
"We were able to build the core search functionality using this product."
"CDN service reduces latency when accessing our web application."
"It's the best solution for any company. It has a hosting ERP system for any task. AWS is stable. AWS is more flexible and its elastic concept is a new concept. AWS is also very secure. It has many layers of security, like hardware security and software security. This is a big issue."
"AWS CloudSearch's best features are good performance under high CPU and memory use, and ease of deployment and scaling."
"It is remarkably efficient and beneficial."
"The quality of the solution is good."
"The most valuable feature is the out of the box Kibana."
"ELK Elasticsearch is definitely a stable solution; it is the spec that surprises most of the other logging solutions in the market."
"In the last 18 months Elastic has really caught up and also gone way beyond AWS by putting together all the missing components that make ELK Elasticsearch the most comprehensive stack in the entire Big Data ecosystem."
"A nonstructured database that can manage large amounts of nonstructured data."
"From the customer side, Elastic Search is super fast and very efficient, delivering results quickly."
"The most valuable features are the data store and the X-pack extension."
"Elastic is doing a fantastic job by doing the indexing, and with a couple of indexing configurations, we are able to achieve our goal even though we are maintaining a huge amount of data per day, around millions of transactions for each record."
"I appreciate that Elastic Enterprise Search is easy to use and that we have people on our team who are able to manage it effectively."
 

Cons

"The deployment could be easier for beginners."
"I believe that Algolia could be better economically; it should work in a way whereby you can provide better pricing patterns."
"I think they could improve the analytics view."
"The high cost of the product is an area of concern where improvements are required."
"Joining is quite complex."
"One area for Algolia's improvement is the relevance of tuning and configuration because it can take some time to properly configure ranking and filtering for a specific use case."
"Algolia is not adopted that much, and it would be great if it were made more popular."
"I think they could improve the analytics view."
"We'd like to see more database features."
"The solution should improve the recovery aspects that it has on offer."
"The price of the solution can be expensive."
"Latlon data type only supports single value per document. All other types support multiple values. We faced issues with this because we had scenarios where, for each document, we needed to store multiple latlon values for different geographical locations."
"Security is a concern but they're working on it."
"The solution should improve the recovery aspects that it has on offer."
"Regarding the period of propagation on CDN servers, sometimes we update photos or files and we don't see the update instantly. We need to wait for sometime."
"Security is a concern but they're working on it."
"The one area that can use improvement is the automapping of fields."
"I have not explored Elastic Search at the most. Searching from vector DB is available in Elastic Search, and there is one more concept of graph searching or graph database searching. I have not explored it, but if it is not there, that would be an improvement area where Elastic Search can improve."
"Dashboards could be more flexible, and it would be nice to provide more drill-down capabilities."
"Elastic Enterprise Search could improve the report templates."
"Elastic Enterprise Search can improve by adding some kind of search that can be used out of the box without too much struggle with configuration. With every kind of search engine, there is some kind of special function that you need to do. A simple out-of-the-box search would be useful."
"This solution is stable, but at times the stack will freeze and you have to remove and recreate the cluster."
"An improvement would be to have an interface that allows easier navigation and tracing of logs."
"There is a maximum of 10,000 entries, so the limitation means that if I wanted to analyze certain IP addresses more than 10,000 times, I wouldn't be able to dump or print that information."
 

Pricing and Cost Advice

"In terms of the cost of Algolia, the tool is really expensive for us in Brazil since it comes to about half a million dollars."
"Algolia is a cool, super-easy-to-use, and affordable tool."
"We are currently on a contract with Algolia for licensing and price."
"For any developer starting out, it is worth it."
"I have heard that Algolia is an expensive solution."
"The product is cheap."
"I'm not sure how much we pay a year. It might be around $30,000 a year."
"In comparison to IBM and Microsoft, the pricing is more favorable."
"There was no license needed to use this solution."
"We chose AWS because of its cost and stability."
"On a scale of one to ten, where one point is cheap, and ten points are expensive, I rate the pricing as medium or reasonable."
"Amazon AWS CloudSearch charging is based on how many resources you consume or and the solution is known to be a bit expensive."
"Our license costs around $4,000 per month."
"This product is open-source and can be used free of charge."
"It can be expensive."
"we are using a licensed version of the product."
"An X-Pack license is more affordable than Splunk."
"The solution is not expensive because users have the option of choosing the managed or the subscription model."
"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"The version of Elastic Enterprise Search I am using is open source which is free. The pricing model should improve for the enterprise version because it is very expensive."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
885,444 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
13%
Computer Software Company
11%
Performing Arts
9%
Outsourcing Company
8%
Manufacturing Company
13%
Comms Service Provider
10%
Computer Software Company
9%
Marketing Services Firm
6%
Financial Services Firm
11%
Computer Software Company
10%
Manufacturing Company
9%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise1
Large Enterprise6
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise6
By reviewers
Company SizeCount
Small Business38
Midsize Enterprise10
Large Enterprise46
 

Questions from the Community

What is your experience regarding pricing and costs for Algolia?
The pricing, setup cost, and licensing for Algolia are based on a pay-as-you-go model, which is very efficient. The c...
What needs improvement with Algolia?
The cost scales aggressively as the record count and search operations grow. Keeping the index in sync with our sourc...
What is your primary use case for Algolia?
Algolia powers the font search browse experience at Monotype, where users can search by font name, style, classificat...
Ask a question
Earn 20 points
What do you like most about ELK Elasticsearch?
Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is ve...
What is your experience regarding pricing and costs for ELK Elasticsearch?
On the subject of pricing, Elastic Search is very cost-efficient. You can host it on-premises, which would incur zero...
What needs improvement with ELK Elasticsearch?
From the UI point of view, we are using most probably Kibana, and I think they can do much better than that. That is ...
 

Also Known As

No data available
No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

Birchbox, Twitch, Lacoste, Stripe, WW, Medium, Cousera, National Geographic, Zendesk, Magento
SmugMug
T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Find out what your peers are saying about Elastic, Algolia, Amazon Web Services (AWS) and others in Search as a Service. Updated: March 2026.
885,444 professionals have used our research since 2012.