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

Elastic Search vs Supabase Vector comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

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)
Supabase Vector
Ranking in Vector Databases
9th
Average Rating
8.4
Reviews Sentiment
5.3
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

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 Supabase Vector is 7.4%, up from 5.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Mindshare Distribution
ProductMindshare (%)
Elastic Search4.5%
Supabase Vector7.4%
Other88.1%
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.
AmritDash - PeerSpot reviewer
Automation Engineer at a educational organization with 11-50 employees
Unified course data has streamlined our AI study assistant and still needs better large-scale search
There can be compute spikes when we scale up, which we noticed during our intake season while processing millions of records. Massive similarity searches on a lot of vectors can spike the database CPU and potentially slow down API requests, so we had to move to a higher plan in Supabase for handling this during our intake season. There is no native hybrid search yet, which can combine keyword search and vector search. Supabase supports both, but combining them requires writing a custom Postgres function, while dedicated tools on other platforms allow you to do that out of the box. On some level, we face indexing complexity with Supabase Vector because although vectors expedite searches, we need to use indexes such as HNSW or IVF Flat. Tuning these indexes in Postgres requires advanced knowledge, and we needed a dedicated Supabase expert or to hire someone capable of understanding these complex queries and set this up for us, making it not a plug-and-play solution for a massive scale project with tens of millions of vectors. Vectors are stored in Postgres, and we can perform a lot of similarity searches on millions of vectors, which can spike database CPU and potentially slow down the app, but apart from that, everything seems positive.

Quotes from Members

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

Pros

"Search is really powerful."
"Elasticsearch helps us to store the data in key value pairs and, based on that, we can produce visualisations in Kibana."
"One thing I appreciate about Elastic Search is the ability to aggregate everything into one dashboard, so I can have monitoring, logs, and traces in one portal instead of having multiple different tools to do the same."
"The most valuable feature of Elastic Enterprise Search is user behavior analysis."
"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."
"Overall, considering key aspects like cost, learning curve, and data indexing architecture, Elasticsearch is a very good tool."
"The most valuable feature of Elastic Enterprise Search is the opportunity to search behind and between different logs."
"The observability is the best available because it provides granular insights that identify reasons for defects."
"Supabase enables us to lower the skill floor while keeping the ceiling high."
"Supabase Vector has positively impacted our organization quite a lot, as we moved away from Pinecone to a unified platform where we store relational and vectorized data together, reducing automation times and eliminating the hassle of managing and maintaining two separate databases in sync."
"The platform's role-level security feature is quite effective for spatial data management."
"Supabase Vector is easy to set up and cost-effective because the alternative is Firebase, which requires a credit card."
"Supabase enables us to lower the skill floor while keeping the ceiling high."
"Supabase Vector rapidly increases the speed and efficiency with which I search through a database, helping with my data analysis tasks."
 

Cons

"Elastic Search could benefit from a more user-friendly onboarding process for beginners."
"Elasticsearch could improve by honoring Unix environmental variables and not relying only on those provided by Java (e.g. installing plugins over the Unix http proxy)."
"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, but with Elastic Search, it takes a little bit of time, ten to fifteen seconds."
"I see that there are areas in Elastic Search that have room for improvement, such as user documentation and onboarding processes."
"The real-time search functionality is not operational due to its impact on system resources."
"Elastic needs to work on their Machine Learning offering because currently they have been trying to make it a black box which doesn't work for a serious user (a Data Scientist) as it doesn't give any control over the underlying algorithm."
"The documentation regarding customization could be better."
"I would rate technical support from Elastic Search as three out of ten. The main issue is a general sum of all factors."
"One area for the solution improvement is the inclusion of more sample code in various programming languages, particularly PHP."
"I notice that the schema visualizer can be improved. Additionally, the internal AI assistant powered by GPT can also be improved."
"I think the support system can be better because after Supabase Vector stopped working in India, there is no support."
"I think there are still many Postgres features that can be developed further by the Supabase team."
"There can be compute spikes when we scale up, which we noticed during our intake season while processing millions of records. Massive similarity searches on a lot of vectors can spike the database CPU and potentially slow down API requests, so we had to move to a higher plan in Supabase for handling this during our intake season."
"I think there are still many Postgres features that can be developed further by the Supabase team."
 

Pricing and Cost Advice

"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."
"We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition."
"The solution is less expensive than Stackdriver and Grafana."
"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"The price of Elasticsearch is fair. It is a more expensive solution, like QRadar. The price for Elasticsearch is not much more than other solutions we have."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"The solution is free."
"An X-Pack license is more affordable than Splunk."
"The solution's cost is reasonable compared to other solutions."
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%
Comms Service Provider
14%
Manufacturing Company
7%
Outsourcing Company
7%
Financial Services Firm
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business39
Midsize Enterprise12
Large Enterprise47
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise1
Large Enterprise2
 

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 needs improvement with Supabase Vector?
I think the support system can be better because after Supabase Vector stopped working in India, there is no support. Nobody knows how to deal with the database now. The naming structure is a littl...
What is your primary use case for Supabase Vector?
I'm using Supabase Vector for the Postgres part. I use their Postgres database as the main requirement for the product from my side. If I am building a small website or any product, I don't need to...
 

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.
Information Not Available
Find out what your peers are saying about Elastic Search vs. Supabase Vector and other solutions. Updated: April 2026.
893,221 professionals have used our research since 2012.