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

Chroma vs Elastic Search comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 3, 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

Chroma
Ranking in Vector Databases
17th
Average Rating
8.6
Reviews Sentiment
5.6
Number of Reviews
2
Ranking in other categories
No ranking in other categories
Elastic Search
Ranking in Vector Databases
6th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
100
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st)
 

Mindshare comparison

As of September 2026, in the Vector Databases category, the mindshare of Chroma is 5.9%, down from 11.3% compared to the previous year. The mindshare of Elastic Search is 5.3%, up from 4.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Mindshare Distribution
ProductMindshare (%)
Elastic Search5.3%
Chroma5.9%
Other88.8%
Vector Databases
 

Featured Reviews

GagandeepSingh1 - PeerSpot reviewer
Data Science Manager at Zykrr
A simple and easy to use solution that can run on a two-course CPU
We collect customer's feedback, and then we present it to the clients It's very easy to set up and runs easily. It doesn't require great hardware and can run on a two-course CPU with four gigs. The hybrid algorithm needs improvement. I have been using Chroma for one year.  I had some trouble…
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.

Quotes from Members

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

Pros

"The solution's most valuable feature is its documentation, which allows new users to easily learn, deploy, and use it."
"It's very easy to set up and runs easily."
"The most valuable feature of Elastic Enterprise Search is the opportunity to search behind and between different logs."
"I have found the sort capability of Elastic very useful for allowing us to find the information we need very quickly."
"It is highly valuable because of its simplicity in maintenance, where most tasks are handled for you, and it offers a plethora of built-in features."
"Elastic Enterprise Search is scalable. On a scale of one to 10, with one being not scalable and 10 being very scalable, I give Elastic Enterprise Search a 10."
"I am impressed with the product's Logstash. The tool is fast and customizable. You can build beautiful dashboards with it. It is useful and reliable."
"The solution is valuable for log analytics."
"The flexibility and the support for diverse languages that it provides for searching the database are most valuable, and we can use different languages to query the database."
"There are a lot of good things about this solution. First, it is an extremely fast search. We have quite an extensive number of logs, and we can search through billions of documents in just a few minutes, and get the results we're looking for."
 

Cons

"The hybrid algorithm needs improvement."
"I think Chroma doesn't have a ready-made containerized image available."
"This solution is stable, but at times the stack will freeze and you have to remove and recreate the cluster."
"Elastic Search needs to improve its technical support. It should be customer-friendly and have good support."
"From the UI point of view, we are using most probably Kibana, and I think they can do much better than that."
"Scalability and ROI are the areas they have to improve."
"They could improve some of the platform's infrastructure management capabilities."
"Elasticsearch should have simpler commands for window filtering."
"Its licensing needs to be improved. They don't offer a perpetual license. They want to know how many nodes you will be using, and they ask for an annual subscription. Otherwise, they don't give you permission to use it. Our customers are generally military or police departments or customers without connection to the internet. Therefore, this model is not suitable for us. This subscription-based model is not the best for OEM vendors. Another annoying thing about Elasticsearch is its roadmap. We are developing something, and then they say, "Okay. We have removed that feature in this release," and when we are adapting to that release, they say, "Okay. We have removed that one as well." We don't know what they will remove in the next version. They are not looking for backward compatibility from the customers' perspective. They just remove a feature and say, "Okay. We've removed this one." In terms of new features, it should have an ODBC driver so that you can search and integrate this product with existing BI tools and reporting tools. Currently, you need to go for third parties, such as CData, in order to achieve this. ODBC driver is the most important feature required. Its Community Edition does not have security features. For example, you cannot authenticate with a username and password. It should have security features. They might have put it in the latest release."
"I think the pricing of Elastic Search is really, really expensive."
 

Pricing and Cost Advice

"The current version is an open-source."
"The basic license is free, but it comes with a lot of features that aren't free. With a gold license, we get active directory integration. With a platinum license, we get alerting."
"I rate Elastic Search's pricing an eight out of ten."
"The solution is not expensive because users have the option of choosing the managed or the subscription model."
"The solution is free."
"We are using the free version and intend to upgrade."
"The solution is less expensive than Stackdriver and Grafana."
"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"The solution is affordable."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
11%
Financial Services Firm
11%
Comms Service Provider
9%
Manufacturing Company
8%
Financial Services Firm
11%
Outsourcing Company
9%
Manufacturing Company
9%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise50
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for ELK Elasticsearch?
The pricing for Elastic Search is mainly budgeted according to the organization budget, so we take it as a yearly subscription, and that is acceptable since we do get a fair discount when we are ta...
What needs improvement with ELK Elasticsearch?
When we get the logs, it is mostly about how we edit the configurations and how we make changes according to the requirements of our organization. In these cases, the logs sometimes can be a bit in...
What is your primary use case for ELK Elasticsearch?
I am the Elastic Search admin for my organization, and we are using Elastic Search to handle the traffic to GCP. The monitoring of all the clusters and all the deployments are quite good, and compa...
 

Comparisons

 

Also Known As

No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

1. Google 2. Netflix 3. Amazon 4. Facebook 5. Microsoft 6. Apple 7. Twitter 8. Spotify 9. Adobe 10. Uber 11. Airbnb 12. LinkedIn 13. Pinterest 14. Snapchat 15. Dropbox 16. Salesforce 17. IBM 18. Intel 19. Oracle 20. Cisco 21. HP 22. Dell 23. Samsung 24. Sony 25. LG 26. Panasonic 27. Philips 28. Toshiba 29. Nokia 30. Motorola 31. Xiaomi 32. Huawei
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 Chroma vs. Elastic Search and other solutions. Updated: August 2026.
913,806 professionals have used our research since 2012.