Our use case for Qdrant is AI data analysis.
Qdrant Vector Database
QdrantReviews from AWS customer
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Our AI analysis has achieved sub‑second vector searches and now delivers faster insights
What is our primary use case?
What is most valuable?
The best features of Qdrant are GPU support, which enables very fast processing, and a very light footprint as it uses fewer resources.
I assess the value of Qdrant's ability to handle high-dimensional vectors for our AI projects as very positive. It is able to handle all of the AI workloads we have, and we are currently operating at a chunk size of 128KB, where it performs well.
My thoughts on the hybrid search capabilities of Qdrant are that they are very good.
What needs improvement?
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.
Deploying Qdrant is complex when dealing with a cluster. A single node deployment is very easy, but if you want to deploy a cluster, it becomes complex.
For how long have I used the solution?
We have been using Qdrant for the last two years.
What do I think about the stability of the solution?
Qdrant requires maintenance. You need to patch Qdrant as soon as patches are released. We always perform minor updates, and for major updates, we consider them based on migration time and other factors. We always apply patches and minor updates.
How are customer service and support?
I rate the technical support of Qdrant as a nine because I think we have never reached out to them directly, but Qdrant has good support available online, and I can get answers from forums. The support is good.
Which other solutions did I evaluate?
When comparing Qdrant with other databases like MariaDB or TiDB, those databases do not have vector searching capabilities. Qdrant can be compared with other vector databases like Milvus, ClickHouse, and Pinecone. Qdrant operates in its own vector database segment and is good because it supports GPU acceleration, meaning if you can install a graphics card, it will use it, and it has cluster support. There is room for improvement, but it does have cluster support. If you compare other databases like Milvus or Pinecone, they do not have clustering or GPU support; those are very preliminary databases. Qdrant is an enterprise database, and we can rely on it for running enterprise applications. ClickHouse is somewhat comparable to Qdrant, but ClickHouse is a hybrid database rather than a specialized database designed for time series; it is only somewhat comparable to Qdrant.
What other advice do I have?
We are using the default query language for Qdrant, and we have not used anything else. Whatever Qdrant provides by default, we are using it, and we are satisfied with that.
The metrics I use to evaluate the performance in indexing and retrieving vectors with Qdrant focus on response time. Response time is the primary metric.
Qdrant has reduced our response time to less than one second for our 128 KB token sizes, and we are satisfied with that performance.
Qdrant is open source, which means the software is free if you handle it yourself, but you need one or two engineers working on it. Since it is free, it is very good compared to other databases. I rate this review an overall 8.
Hybrid search has improved legal and educational AI retrieval and supports fast model iteration
What is our primary use case?
My primary use cases for Qdrant are legal and educational.
What is most valuable?
The most valuable feature I have found in Qdrant is the sample code. I think they have good examples that make it developer-friendly.
Using Qdrant's hybrid search capability has improved my search results. The ability of Qdrant to handle high-dimensional vectors for my AI projects is pretty fast, and I think it's the best we have used so far. That's why we continue using it and did not check other options anymore.
The configuration of Qdrant is okay. For a developer, it was easy to set the product up and to use it.
What needs improvement?
I should check if real-time data updates in Qdrant have helped improve my models, as I don't even know they have that feature.
A lot of our work is agentic right now, and we have also segmented the content to be logical, so there's not a lot of vector search anymore. I haven't really thought of any additional features that would make Qdrant closer to a perfect score.
For how long have I used the solution?
I have been using Qdrant for two years.
How are customer service and support?
I would rate Qdrant's technical support as community-driven. There's community support since we're not paying anything, and it's more the community support for it. It's open source, so we house it on our server.
I think they provide enough information on the internet, and I am satisfied with it. They explain it well.
Which solution did I use previously and why did I switch?
I switched from Faiss because it's open source and there's not a lot of support. We were worried that moving forward, maybe no one will maintain it, so it's just good for experimenting.
How was the initial setup?
The configuration of Qdrant is okay. For a developer, it was easy to set the product up and to use it.
What's my experience with pricing, setup cost, and licensing?
Using Qdrant is free. We house it and have a VM where we just installed it on the VM.
Which other solutions did I evaluate?
Before finally choosing Qdrant, I did evaluate other options, but that was a long time ago, and I don't know what the state of vector databases is now.
What other advice do I have?
Currently, we are using a vector database called Qdrant, but most of our tasks are agentic, and we don't have it anymore. I can answer a few questions about Qdrant.
I have used Qdrant's hybrid search capability. The use of multiple query languages has impacted my data query processes mostly as Q&A.
We use the Ragas metrics to evaluate Qdrant's performance in indexing and retrieving vectors. All the metrics I consider in Ragas are useful.
In my company, we have around eight or nine people using Qdrant. I think Qdrant is popular enough in my region, but they can probably promote it more.
I rate this review a 9 out of 10.
A quick and easy to setup vector database for RAG needs
scalability & availability
Self-hosted Qdrant Vector DB
depth review of Qdrant.Ai
pricing plans are high.