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

Qdrant vs Redis comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 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

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)
Redis
Ranking in Vector Databases
4th
Average Rating
8.8
Reviews Sentiment
5.9
Number of Reviews
26
Ranking in other categories
NoSQL Databases (4th), Managed NoSQL Databases (6th), In-Memory Data Store Services (1st), AI Software Development (13th)
 

Mindshare comparison

As of May 2026, in the Vector Databases category, the mindshare of Qdrant is 6.9%, down from 7.9% compared to the previous year. The mindshare of Redis is 5.7%, up from 4.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Mindshare Distribution
ProductMindshare (%)
Redis5.7%
Qdrant6.9%
Other87.4%
Vector Databases
 

Featured Reviews

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.
Varuns Ug - PeerSpot reviewer
Senior Software Developer at NIT
Caching has accelerated complex workflows and delivers low latency for high-traffic microservices
A few features of Redis that I use on a day-to-day basis and feel are among the best are extremely low latency and high throughput. Since Redis is in-memory, it makes it ideal for cases such as caching and rate limiting where response time is critical. TTL expiry support is very useful in Redis as it allows me to automatically evict stale data without manual cleanup, which is something I use heavily in my caching strategy. Another point I can mention is that the rich data structures such as strings, hashes, and even sorted sets are very powerful. I have used strings for caching responses and counters, whereas I have used hashes for storing structured objects. One more feature I can tell you about is atomic operations. Redis guarantees atomicity for operations such as incrementing a counter, which is very useful for rate limiting and avoiding race conditions in distributed systems. Finally, I want to emphasize that Redis is easy to scale and integrate, whether through clustering or using a distributed cache across microservices. Redis has impacted my organization positively by providing default support that is very useful. For metrics, in one of my core systems, introducing Redis as a distributed cache helped me achieve around an 80% cache hit rate, which reduced repeated downstream services. Real API latency also improved from around two seconds to approximately 450 milliseconds for P99. It also helped reduce the load on dependent services and databases, which improved overall system reliability.

Quotes from Members

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

Pros

"Qdrant has positively impacted my organization by consuming much less time than building systems through coding."
"Using Qdrant's hybrid search capability has improved my search results."
"Qdrant has reduced our response time to less than one second for our 128 KB token sizes, and we are satisfied with that performance."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"The performance of Redis is very fast."
"I use Redis mostly to cache repeated data that is required."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"The performance of Redis is very fast."
"Overall, I want to say that Redis truly adds value, especially for low latency and high throughput use cases."
"Redis is good for distributed caching management."
 

Cons

"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."
"In future releases, I would like Redis to provide its users with an option like schema validation. Currently, the solution lacks to offer such functionality."
"There are some points where I feel Redis can be improved."
"If we use a lot of data, it will eventually cost us a lot."
"One limitation is that Redis is memory-based, so scaling can become expensive compared to disk-based systems."
"The only thing is the lack of a GUI application. There was a time when we needed to resolve an issue in production. If we had a GUI, it would have been easier."
"Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation."
"Redis presents a single point of failure and lacks fault tolerance."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
 

Pricing and Cost Advice

Information not available
"Redis is an open-source product."
"Redis is an open-source solution. There are not any hidden fees."
"The tool is open-source. There are no additional costs."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is not an overpriced solution."
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
11%
Comms Service Provider
11%
Computer Software Company
10%
Manufacturing Company
8%
Financial Services Firm
24%
Computer Software Company
10%
Comms Service Provider
7%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise6
Large Enterprise10
 

Questions from the Community

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.
What do you like most about Redis?
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you u...
What needs improvement with Redis?
Overall, Redis is a powerful and reliable tool, but there are a few areas for improvement. One limitation is that Redis is memory-based, so scaling can become expensive compared to disk-based syste...
What is your primary use case for Redis?
My main use case for Redis is caching frequently accessed data to improve performance and reduce database load. For example, I cache API responses and user-related data so that repeated requests ca...
 

Comparisons

 

Also Known As

No data available
Redis Enterprise
 

Overview

 

Sample Customers

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
1. Twitter 2. GitHub 3. StackOverflow 4. Pinterest 5. Snapchat 6. Craigslist 7. Digg 8. Weibo 9. Airbnb 10. Uber 11. Slack 12. Trello 13. Shopify 14. Coursera 15. Medium 16. Twitch 17. Foursquare 18. Meetup 19. Kickstarter 20. Docker 21. Heroku 22. Bitbucket 23. Groupon 24. Flipboard 25. SoundCloud 26. BuzzFeed 27. Disqus 28. The New York Times 29. Walmart 30. Nike 31. Sony 32. Philips
Find out what your peers are saying about Qdrant vs. Redis and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.