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

Elastic Search vs Palantir Foundry comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 3, 2024

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 Cloud Data Integration
5th
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
95
Ranking in other categories
Indexing and Search (1st), Search as a Service (1st), Vector Databases (2nd)
Palantir Foundry
Ranking in Cloud Data Integration
10th
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
18
Ranking in other categories
Data Integration (13th), IT Operations Analytics (8th), Supply Chain Analytics (1st), Data Migration Appliances (3rd), Data Management Platforms (DMP) (1st), Data and Analytics Service Providers (1st)
 

Mindshare comparison

As of May 2026, in the Cloud Data Integration category, the mindshare of Elastic Search is 1.7%, down from 1.8% compared to the previous year. The mindshare of Palantir Foundry is 4.3%, down from 4.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Data Integration Mindshare Distribution
ProductMindshare (%)
Elastic Search1.7%
Palantir Foundry4.3%
Other94.0%
Cloud Data Integration
 

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.
BA
Associate Vice President at a insurance company with 10,001+ employees
Unified data workflows have empowered collaborative analytics and streamlined AI development
Regarding points for improvement for Palantir Foundry, I see that they are improving day by day. In the last one to two years, I have seen many improvements compared to the two years that I have worked on Palantir Foundry. There are many things that come up, but a few things are not intuitive enough. Now that we are in this AI phase, Palantir Foundry has created some wrappers around the models, allowing us to create using a no-code application, chatbots, and LLM functions. The problem is that interaction with outside applications can be difficult with the current setup that Palantir Foundry has. There are ways to do that, but it is not that intuitive, which is what I feel.

Quotes from Members

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

Pros

"We chose Elasticsearch because we could build a model in a short amount of time, allowing us to build a whole setup in one month and get 93% accuracy, with complex AI-based features built in a shorter span and with high accuracy that wasn't possible with other search enterprise vendors we used."
"The positive impact I've seen from using Elastic Search includes replacing conventional databases and being able to store much more unstructured data."
"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."
"The most valuable feature of Elastic Enterprise Search is user behavior analysis."
"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 special text processing features in this solution are very important for me."
"Search is really powerful."
"The ability to aggregate log and machine data into a searchable index reduces time to identify and isolate issues for an application. Saves time in triage and incident response by eliminating manual steps to access and parse logs on separate systems, within large infrastructure footprints."
"Palantir Foundry is a robust platform that has really strong plugin connectors and provides features for real-time integration."
"Based on my huge experience with Palantir Foundry, I find that starting from the data connection to the end user application, there is a tool for everyone."
"The data lineage is great."
"The interface is really user-friendly."
"The AI engine that comes with Palantir Foundry is quite interesting."
"It is easy to map out a workflow and run trigger-based scripts without having to deploy to another server."
"Great features available in one tool."
"This product has all the various components for getting data, transforming it and visually creating the dashboards without the need to integrate things and no need to check the compatibility."
 

Cons

"There should be more stability."
"I think the first area for improvement is pricing, as the cluster cost for Elastic Search is too high for me."
"There are a few things that did not work for us. When doing a search in a bigger setup, with a huge amount of data where there are several things coming in, it has to be on top of the index that we search."
"The documentation regarding customization could be better."
"An improvement would be to have an interface that allows easier navigation and tracing of logs."
"The one area that can use improvement is the automapping of fields."
"This is not exactly a stable solution, which is why we are considering another compatible tool, and whether we go on with Elasticsearch or change it."
"To do what we want to do with Elastic Search, the queries can get complex and require a fuller understanding of the DSL."
"The solution could use more online documentation for new users."
"There is not a wide user base for the solution's online documentation so it is sometimes difficult to find answers."
"The solution’s data security could be improved."
"They do not have a data center in Europe, and we have lots of personally identifiable information in our dataset that needs to be hosted by a third-party data center like Amazon or Microsoft Azure."
"The major hindrance with Palantir Foundry is that being a very closed product, the cost optimization and costing are not exposed to the end users."
"The one area where improvement could be made is the cost of the solution which is quite expensive."
"The workflow could be improved. Although it works rather seamlessly, the workflow is too complicated sometimes."
"The startup pricing is high, causing concern despite being cost-effective in terms of total cost of ownership."
 

Pricing and Cost Advice

"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."
"we are using a licensed version of the product."
"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."
"The solution is free."
"The version of Elastic Enterprise Search I am using is open source which is free. The pricing model should improve for the enterprise version because it is very expensive."
"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"The price of Elastic Enterprise is very, very competitive."
"Palantir Foundry has different pricing models that can be negotiated."
"Palantir Foundry is an expensive solution."
"It's expensive."
"The solution’s pricing is high."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
892,868 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%
Manufacturing Company
13%
Financial Services Firm
9%
Government
8%
University
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business39
Midsize Enterprise12
Large Enterprise46
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise5
Large Enterprise9
 

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 Palantir Foundry?
Regarding points for improvement for Palantir Foundry, I see that they are improving day by day. In the last one to two years, I have seen many improvements compared to the two years that I have wo...
What is your primary use case for Palantir Foundry?
There are several use cases that we are working on with Palantir Foundry. The first thing is for data model creation for all our data engineering pipelines. That is one use case. Palantir Foundry a...
What advice do you have for others considering Palantir Foundry?
The visualization part in Palantir Foundry works for me at least if I want to see how the data is structured and for an initial analysis, but I would say it is not as matured as Power BI or Tableau...
 

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.
Merck KGaA, Airbus, Ferrari,United States Intelligence Community, United States Department of Defense
Find out what your peers are saying about Elastic Search vs. Palantir Foundry and other solutions. Updated: April 2026.
892,868 professionals have used our research since 2012.