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

Elastic Search vs Qdrant 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:
 

Categories and Ranking

Elastic Search
Ranking in Vector Databases
2nd
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
96
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st)
Qdrant
Ranking in Vector Databases
5th
Average Rating
9.4
Reviews Sentiment
5.3
Number of Reviews
3
Ranking in other categories
Open Source Databases (11th), AI Data Analysis (18th)
 

Mindshare comparison

As of May 2026, in the Vector Databases category, the mindshare of Elastic Search is 4.5%, down from 5.4% compared to the previous year. The mindshare of Qdrant is 6.9%, down from 7.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Mindshare Distribution
ProductMindshare (%)
Elastic Search4.5%
Qdrant6.9%
Other88.6%
Vector Databases
 

Featured Reviews

reviewer2817942 - PeerSpot reviewer
Senior Software Engineer at a consultancy with 11-50 employees
Logging and vector search have transformed observability and empowered reliable ai agents
Elastic Search is not specifically being used for certain purposes. I deploy Elastic Search database on the cloud and use cloud services so that nobody can attack. However, I do not use Elastic Search to resolve attack issues. The basic main purpose of Elastic Search, as of now, I feel it can do more in the AI area. Sometime I saw that when I am developing RAG and have to generate the embeddings, which I call metadata, sometimes it tries to fail. That durability or issue handling should be improved, but apart from that, I did not find anything as of now. As per my use case, whatever I am using seems pretty good. Apart from that, some definitely improvement will be there. One improvement is that it should be faster. Whenever I am searching any logs, it takes much time. For example, if I open my log in Notepad or a similar tool, I can search the text within a second. With Elastic Search, it takes a little bit of time, ten to fifteen seconds. That can be improved. Sometimes, engineers take time to assign when I create a ticket.
CM
Lead Ai Tech And Tech Automation Engineer at a individual & family service with 1-10 employees
Building accurate no-code resume screeners has saved weeks in document search workflows
I see room for improvement in Qdrant based on what another platform called Weaviate offers. Qdrant provides an excellent vector database with a solid searching method. However, it could elevate its offering by integrating embedding features. Currently, for the workflow automation I build, I rely on other platforms for embedding, so incorporating this feature directly in Qdrant Cloud would eliminate the need to depend on external solutions. A pain point I have encountered was the inactive expiration of the cloud created for certain projects. If the cloud is not used for a week, it gets terminated, which is frustrating. I think increasing that inactivity window in the free tier would be beneficial, as I have faced limitations due to this seven-day inactivity rule, requiring me to reset up the cloud after its termination.

Quotes from Members

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

Pros

"The special text processing features in this solution are very important for me."
"This has improved our organization because we articulated Kubernetes, Docker, and GitHub with amazing simplicity in the scaling up of our service."
"The most valuable features of Elastic Enterprise Search are it's cloud-ready and we do a lot of infrastructure as code. By using ELK, we're able to deploy the solution as part of our ISC deployment."
"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."
"I would recommend Elastic Search to other people who want to have fast search in their applications."
"The initial installation and setup were straightforward."
"I value the feature that allows me to share the dashboards to different people with different levels of access."
"You have dashboards, it is visual, there are maps, you can create canvases. It's more visual than anything that I've ever used."
"Qdrant has reduced our response time to less than one second for our 128 KB token sizes, and we are satisfied with that performance."
"Using Qdrant's hybrid search capability has improved my search results."
"Qdrant has positively impacted my organization by consuming much less time than building systems through coding."
 

Cons

"Improving machine learning capabilities would be beneficial."
"There are some features lacking in ELK Elasticsearch."
"I think the biggest issue we had with Elastic Search was regarding integrations with our multi-factor authentication tool."
"It should be easier to use. It has been getting better because many functions are pre-defined, but it still needs improvement."
"The upgrade experience and inflexibility with fields keeps Elastic Search from being a perfect 10."
"There is a lack of technical people to develop, implement and optimize equipment operation and web queries."
"This solution is stable, but at times the stack will freeze and you have to remove and recreate the cluster."
"It should be easier to use. It has been getting better because many functions are pre-defined, but it still needs improvement."
"A pain point I have encountered was the inactive expiration of the cloud created for certain projects; if the cloud is not used for a week, it gets terminated, which is frustrating."
"The area for improvement in Qdrant is its clustering capability. While it has clustering functionality, it is not easy to set up, and not everyone can configure the clustering, so there is room for improvement in the clustering configuration."
 

Pricing and Cost Advice

"We are using the free version and intend to upgrade."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"This product is open-source and can be used free of charge."
"​The pricing and license model are clear: node-based model."
"We are using the open-sourced version."
"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 cost varies based on factors like usage volume, network load, data storage size, and service utilization. If your usage isn't too extensive, the cost will be lower."
Information not available
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
9%
Manufacturing Company
9%
Retailer
6%
Financial Services Firm
11%
Comms Service Provider
11%
Computer Software Company
10%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business39
Midsize Enterprise12
Large Enterprise47
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for ELK Elasticsearch?
When it comes to pricing, I think we had to pay AWS approximately 1,000 to 1,200 per month for the overall stack. I am not quite certain about how much Elastic Search costs specifically because I w...
What needs improvement with ELK Elasticsearch?
Elastic Search has many features, including Kibana and Logstash, which we regularly use. However, one downside in our product is cost, as it can be expensive when maintaining multiple shards and in...
What is your primary use case for ELK Elasticsearch?
As a developer, I use Elastic Search in developing one of my applications, basically integrating the back-end with Elastic Search. Our main use case for Elastic Search is for Logstash, which is a s...
What is your experience regarding pricing and costs for Qdrant?
Using Qdrant is free. We house it and have a VM where we just installed it on the VM.
What needs improvement with Qdrant?
The area for improvement in Qdrant is its clustering capability. While it has clustering functionality, it is not easy to set up, and not everyone can configure the clustering, so there is room for...
What is your primary use case for Qdrant?
Our use case for Qdrant is AI data analysis.
 

Comparisons

 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
No data available
 

Overview

 

Sample Customers

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.
1. Airbnb 2. Amazon 3. Apple 4. BMW 5.Cisco 6. CocaCola 7. Dell 8. Disney 9. Google 10. HP 11. IBM 12. Intel 13. JPMorgan Chase 14. Kraft Heinz 15. L'Oreal 16. McDonalds 17. Merck 18. Microsoft 19. Nike20. Oracle 21. PG 22. PepsiCo 23. Procter and Gamble 24. Samsung 25. Shell 26. Sony 27. Toyota 28. Visa 29. Walmart 30. WeWork
Find out what your peers are saying about Elastic Search vs. Qdrant and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.