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
93
Ranking in other categories
Indexing and Search (1st), Search as a Service (1st), Vector Databases (3rd)
Palantir Foundry
Ranking in Cloud Data Integration
12th
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
18
Ranking in other categories
Data Integration (10th), 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 April 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.4% 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

Anurag Pal - PeerSpot reviewer
Technical Lead at YatriPay Limited
Search and aggregations have transformed how I manage and visualize complex real estate data
Elastic Search consumes lots of memory. You have to provide the heap size a lot if you want the best out of it. The major problem is when a company wants to use Elastic Search but it is at a startup stage. At a startup stage, there is a lot of funds to consider. However, their use case is that they have to use a pretty significant amount of data. For that, it is very expensive. For example, if you take OLTP-based databases in the current scenario, such as ClickHouse or Iceberg, you can do it on 4GB RAM also. Elastic Search is for analytical records. You have to do the analytics on it. According to me, as far as I have seen, people will start moving from Elastic Search sooner or later. Why? Because it is expensive. Another thing is that there is an open source available for that, such as ClickHouse. Around 2014 and 2012, there was only one competitor at that time, which was Solr. But now, not only is Solr there, but you can take ClickHouse and you have Iceberg also. How are we going to compete with them? There is also a fork of Elastic Search that is OpenSearch. As far as I have seen in lots of articles I am reading, users are using it as the ELK stack for logs and analyzing logs. That is not the exact use case. It can do more than that if used correctly. But as it involves lots of cost, people are shifting from Elastic Search to other sources. When I am talking about pricing, it is not only the server pricing. It is the amount of memory it is using. The pricing is basically the heap Java, which is taking memory. That is the major problem happening here. If we have to run an MVP, a client comes to me and says, "Anurag, we need to do a proof of concept. Can we do it if I can pay a 4GB or 16GB expense?" How can I suggest to them that a minimum of 16GB is needed for Elastic Search so that your proof of concept will be proved? In that case, what I have to suggest from the beginning is to go with Cassandra or at the initial stage, go with PostgreSQL. The problem is the memory it is taking. That is the only thing.
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

"The solution has good security features. I have been happy with the dashboards and interface."
"The UI is very nice, and performance wise it's quite good too."
"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."
"From a technical point of view, there are no significant issues recalled as Elastic Search has been absolutely awesome for this use case and covers 100% of the needs."
"The most valuable feature of Elastic Enterprise Search is the Discovery option for the visualization of logs on a GPU instead of on the server."
"The machine learning features of Elastic Search are very interesting, including the possibility to include models such as ELSER and different multilingual models that let us fine-tune our searches and use them in our search projects."
"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."
"In the last 18 months Elastic has really caught up and also gone way beyond AWS by putting together all the missing components that make ELK Elasticsearch the most comprehensive stack in the entire Big Data ecosystem."
"It has been the platform for end to end data processing, manipulations, and reporting, greatly improved org's data reporting effort."
"Encapsulates all the components without the requirement to integrate or check compatibility."
"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."
"The interface is really user-friendly."
"I rate Palantir Foundry a ten out of ten."
"The solution provides an end-to-end integrated tech stack that takes care of all utility/infrastructure topics for you."
"I like the data onboarding to Palantir Foundry and ETL creation."
"It's scalable."
 

Cons

"The one area that can use improvement is the automapping of fields."
"While integrating with tools like agents for ingesting data from sources like firewalls is valuable, I believe prioritizing improvements to the core product would be more beneficial."
"New Relic could be more flexible, similar to Elasticsearch."
"Maybe Elastic Search could improve the analytics part of the search so it can be more powerful to the user."
"We'd like more user-friendly integrations."
"There are challenges with performance management and scalability."
"It should be easier to use. It has been getting better because many functions are pre-defined, but it still needs improvement."
"There is an index issue in which the data starts to crash as it increases."
"I rate Palantir Foundry five out of 10. I'm ambivalent."
"The frontend capabilities of Palantir Foundry could be improved."
"The startup pricing is high, causing concern despite being cost-effective in terms of total cost of ownership."
"The workflow could be improved. Although it works rather seamlessly, the workflow is too complicated sometimes."
"It requires a lot of manual work and is very time-consuming to get to a functional point."
"If you want to create new models on specific data sets, computing that is quite costly."
"Cost of this solution is quite high."
"It would be helpful to build applications based on Azure functions or web apps in Palantir Foundry."
 

Pricing and Cost Advice

"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"​The pricing and license model are clear: node-based model."
"To access all the features available you require both the open source license and the production license."
"The price of Elastic Enterprise is very, very competitive."
"The solution is less expensive than Stackdriver and Grafana."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"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."
"Palantir Foundry is an expensive solution."
"It's expensive."
"Palantir Foundry has different pricing models that can be negotiated."
"The solution’s pricing is high."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
886,664 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
14%
Financial Services Firm
10%
Government
8%
University
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business38
Midsize Enterprise11
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?
On the subject of pricing, Elastic Search is very cost-efficient. You can host it on-premises, which would incur zero cost, or take it as a SaaS-based service, where the expenses remain minimal.
What needs improvement with ELK Elasticsearch?
From the UI point of view, we are using most probably Kibana, and I think they can do much better than that. That is something they can fine-tune a little bit, and then it will definitely be a good...
What is your primary use case for ELK Elasticsearch?
Elastic Search use cases for us involve maintaining a huge amount of data per day, around millions of transactions for each record. We are maintaining all this data with Elastic, and Elastic is doi...
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.
886,664 professionals have used our research since 2012.