Palantir Technologies(PLTR)

Material Event filed 2026-08-03

Use of third party AI model services poses significant risk to your alpha. Without sovereign control over how your data is processed by those services (either the AI Labs or the Hyperscalers, collectively referred to as “Hosted Model Providers”), Hosted Model Providers may extract your alpha (your unique institutional knowledge and tradecraft embodied in data exposed to and generated from your use of AI models) and resell it to the broader market in the form of weights or services. Storage of your data by Hosted Model Providers also increases the attack surface against your alpha in an increasingly cyber-insecure world, and risks your most valuable assets being swept up in the ongoing existential legal battles that many Hosted Model Providers are facing. It is essential to maintain sovereign control of your data so this does not occur. While additional sovereign control might involve making use of neoclouds (providers of which might be more open to more data-protective terms than Hoste

Material Event filed 2026-06-09

Editor’s Note: This is the fourth post in a series exploring how Palantir customizes infrastructure software for reliable operation at scale. The following is a guest contribution to the Foundations series from the Gotham Core Platform organization, which builds and maintains the bedrock for mission-critical applications within the Gotham ecosystem. This blog post by Kevin Liang, a backend developer based in CA, highlights the design considerations and improvements made to the Elasticsearch reindex machinery — which broadly aims to provide an easy-to-use, performant, reliable, and observable way to repair and rebuild search indices for backend applications. The goal of this post is two-fold: share our design decisions and learnings with the broader technical community, and shed light on what a typical project looks like for a systems-leaning backend engineer working in Gotham Core Platform at Palantir. Search is one of the most heavily used workflows across Palantir Gotham. Users are c

Editor’s Note: This blog post was written by Greg Little, Senior Counselor at Palantir , with Aaron Jaffe, Senior Vice President at Palantir. Over 10 years of implementing Enterprise Resource Planning (ERP) systems, I remember one project where the CFO stopped the room cold. It was 11:30 at night during a mock cutover. People were exhausted manually fixing mapping issues that “should” have been automated. The CFO looked up, rubbed his face, and said, “Tell me again why we’re changing everything we do just to keep this system happy?” It was a fair question. From the very first ERP project I ever worked on, the expectation was always the same: fit your processes to the standards defined by the ERP core. Keep the core pristine. Never customize the underlying software. Follow the process exactly as delivered. Don’t deviate. Don’t change anything that might jeopardize upgradeability or introduce delays, cost overruns, or fragility. And to be fair, there were good reasons behind this. The ER