Announcements

REMINDER: Sign up for the Foundry Newsletter to receive a summary of new products, features, and improvements across the platform directly to your inbox. For more information on how to subscribe, see the Foundry Newsletter and Product Feedback channels announcement.

Share your thoughts about these announcements in our Developer Community Forum ↗.


Ontology SQL and SQL functions are GA

Date published: 2026-11-12

The Ontology SQL capability allows you to query the Ontology through a subset of the Spark SQL dialect. This feature is now generally available on all enrollments as of the week of 9 November.

Key features

  • Ontology SQL is Foundry's SQL engine for querying Ontology object types, interfaces and many-to-many links. Queries execute directly against object storage using an in-memory compute path for fast response times on supported query shapes, with more complex queries automatically routed to Spark.
  • Ontology SQL functions are parameterized SQL queries over the Ontology that you can publish as Foundry functions. Use them across the platform, including in Workshop, Actions, Automate, and the Ontology SDK.

SQL Studio

SQL Studio is Foundry's dedicated application for writing and running SQL queries.

SQL Studio provides an interactive AI-assisted interface for SQL analysis of tabular data and Ontology objects. Screenshot uses notional data.

SQL Studio provides an interactive, AI-assisted interface for SQL analysis of tabular data and Ontology objects. Screenshot uses notional data.

Publish your query as a SQL function, and manage it from Ontology Manager.

Explore your function across its published versions in Ontology Manager.

Explore your function across its published versions in Ontology Manager.

Ontology SQL is also available throughout north-of-Ontology applications such as Workshop, Insight, Quiver, and AIP products.

What's coming next

Ontology SQL is under active development. In the near term, we are looking to:

  • Improve our support for Spark SQL functions
  • Implement execution optimizations to reduce query latency
  • Provide better observability on planning and execution

We want to hear from you

As we continue to develop Ontology SQL and SQL functions, we want to hear about your experiences and welcome your feedback. Share your thoughts with Palantir Support channels or our Developer Community ↗.


Preview SuperRepo applications with live Ontology data using remote preview

Date published: 2026-11-10

You can now use REMOTE_ONLY mode in SuperRepo preview to run your OSDK React application and functions locally against live objects and links in the Ontology. Access is read-only and uses your own permissions.

Before, preview used seed data, requiring you to manually create and maintain realistic synthetic data or copy objects from your Ontology that you would never deploy into production. With remote preview, you can instead develop against live data without the need to maintain files backing seed objects.

Get started using remote preview in SuperRepo

To begin using remote preview, update the Foundry CLI to version 0.351.0 or later with foundry update self. Next, add the following configuration to foundry.yml, replacing the example RID below with your Ontology’s RID:

Copied!
1 2 3 4 preview: ontology: mode: REMOTE_ONLY ontologyRid: ri.ontology.main.ontology.00000000-0000-0000-0000-000000000000

How remote preview works

When in REMOTE_ONLY mode, SuperRepo preview reads live objects from your Ontology without using the embedded Ontology. Instead, SuperRepo routes all object, link, search, aggregation, and object set requests to the Ontology specified in the ontologyRid: block of foundry.yml.

Configure the foundry.yml file in your SuperRepo to run previews against live objects and links in the Ontology.

Configure the foundry.yml file in your SuperRepo to run previews against live objects and links in the Ontology.

SuperRepo makes requests using standard Foundry project and role-based permissions, so remote preview returns only the objects you can access. Additionally, remote preview checks each object type defined or imported in your ONTOLOGY component against the type with the same API name in the target Ontology. If the schemas differ, remote preview reports a Foundry schema mismatch error and serves no data until they match.

Learn more about remote preview by reviewing the SuperRepo documentation.

Share your feedback

Your feedback helps us prioritize what to build next. Share your thoughts through Palantir Support channels or in our Developer Community ↗ using the superrepo ↗ tag.


Test media upload workflows on global branches

Date published: 2026-11-10

Media upload actions can now run on a global branch, allowing you to test changes without affecting main. Previously, workflows that used media upload actions could not be tested end to end because these actions were unsupported on branches.

With global branching, when an action uploads an image, video, audio file, or document, Foundry writes it to the backing media set on your branch. This allows you to validate Workshop and Ontology workflows that use media reference properties while keeping test media isolated from main and other branches.

When an object type that references a media set is first indexed on a global branch, Foundry automatically adds the media set to that branch. The new media set branch starts empty and does not copy media items from main or another branch. For previously indexed object types, open the object type or a referencing action type in Ontology Manager, then select Add media set to branch.

Uploads and other action edits made on a branch are intended for testing and are not merged into main.

Add the media set to the current global branch from Ontology Manager.

Add the media set to the current global branch from Ontology Manager.

Learn more about uploading media on a branch.

Your feedback matters

Share your feedback through Palantir Support or the Developer Community ↗.


Explore complex connections across your Ontology with Search Around V2

Date published: 2026-11-10

Search Around V2 is now generally available in Vertex, bringing more expressive, point-and-click exploration to your Ontology. Build searches across multiple object and link types, follow repeating patterns, and find connections between specific objects, all from the improved Search Around panel.

The Search Around tab in the Vertex workspace.

The Search Around tab in the Vertex workspace.

The improved Search Around capability expands the questions you can answer in a single search. Start from objects of different types, match multiple object types at each step, or use Any Object Type to explore connections without specifying every intermediate type. Repeat individual steps or entire sections to explore relationships across several hops, and add alternate paths that skip intermediate steps. Choose which link types and directions to follow, then narrow your results with filters on objects and object-backed links.

For example, find connecting flights between two airports while restricting flight duration, departure dates, and the number of flight legs. Review the generated query paths before running your search, with results added to the graph as each path completes.

An example Search Around to find connecting flights between two airports.

An example Search Around to find connecting flights between two airports.

Save and reuse Search Arounds

Save your searches to reuse them across graphs and templates, and use parameters to adjust filter values without rebuilding the search. Saved V2 Search Arounds can also be distributed through Marketplace products, subject to the documented packaging limitations.

Migrate existing Search Arounds to the new V2 capability

To get started, select objects on a Vertex graph and open the Search Around tab on the right side of the workspace. Existing V1 Search Arounds remain usable, and graphs and templates continue running their V1 definitions until you explicitly save them in V2. Review the migrated steps, parameters, and filters before saving; see the migration guidance for details.

Tell us what you think

We want to hear about your experiences using Vertex and welcome your feedback. Share your thoughts with Palantir Support channels or our Developer Community ↗, using the vertex ↗ tag .


Lower costs for streaming ingestion with Foundry worker

Date published: 2026-11-05

Foundry worker is the recommended method for accessing external systems and replaces the legacy agent worker.

From November 1, 2026, customers can expect to see a reduction of around 97.5% in compute costs for their streaming ingests when running on Foundry worker compared to what it would have been previously. This is intended to facilitate migration from agent worker to Foundry worker.

This builds on our recent pricing announcement, which announced several Foundry worker data operations available without compute cost, by reducing compute costs for streaming ingests as well.

Next step: Migrate your connectors to Foundry worker

If you are currently using agent worker for streaming ingests, we recommend migrating as soon as possible. Learn about the benefits and migration steps in the Foundry worker vs. agent worker guide.

Your feedback matters

We want to hear about your experiences using Foundry Worker in the Palantir platform and welcome your feedback. Share your thoughts with Palantir Support channels or on our Developer Community ↗ using the data-connection tag ↗ .


Search and review audit logs with Audit Explorer

Date published: 2026-11-05

Audit Explorer is a new governance application for searching and reviewing audit.3 audit logs in the platform. Audit logs are an important tool for oversight and accountability of the platform's use. Audit Explorer is specifically designed to facilitate the review of the platform's audit logs, including for security investigations, compliance reviews, and oversight of platform usage.

Audit Explorers log table showing recent platform activity and enriched metadata about user and resources. All data is notional.

Audit Explorer's log table, showing recent platform activity and enriched metadata about user and resources. All data is notional.

Audit Explorer is now in the beta phase of development and will be available on selected enrollments at the beginning of November.

Key features

  • Search and filter: Filter audit logs by time, user, event type, category, resource, or Ontology resource.
  • Charts: See when matching events occurred and which event types are most frequent.
  • Logs table: View audit logs in a standardized format, with identifiers for users and resources enriched with context from the platform.
  • Log details: See who did what, when, and from where, with readable summaries for events such as Ontology actions and function executions.
  • Sessions: Explore user sessions in the platform. If scoped sessions are enabled, view the marking selected for the session as well as the associated checkpoint justifications if configured.

Get started

Audit Explorer reads audit.3 audit logs from an Iceberg table. Organization administrators can create this table of audit logs in either of the following ways:

  • In the Audit Explorer application, from the Getting started dialog.
  • In Control Panel, by selecting Create Iceberg table on the Audit logs tab.

The Getting started dialog in the Audit Explorer application shows the details for a new Iceberg audit export.

The Getting started dialog in the Audit Explorer application shows the details for a new Iceberg audit export.

Learn more about Audit Explorer in the documentation.

Audit Explorer is designed for compliance and oversight workflows for authorized users. As a privacy best practice, search audit logs only for a defined oversight or compliance purpose, keeping access limited to those who need it and each search proportionate to the question at hand. Audit Explorer records every search, which keeps reviewers accountable for how they use audit data. Review privacy and civil liberties in practice for guidance on purpose limitation, access governance, and accountability. All uses of Audit Explorer must adhere to Palantir's Acceptable Use Policy ↗.

We want to hear from you

We welcome your feedback and invite you to share your thoughts through Palantir Support or our Developer Community ↗ using the security tag ↗.


DeepSeek V4.1 Flash (1017) support in AIP through Fireworks

Date published: 2026-11-03

AIP adds experimental support for DeepSeek V4.1 Flash (1017) through Fireworks on non-georestricted commercial enrollments, with inference hosted in the United States. Availability depends on the required releases reaching your enrollment and the relevant model settings being enabled.

Model overview

DeepSeek V4.1 Flash (1017) ↗ is an open-weight multimodal model designed for coding, reasoning, and agentic workflows. AIP support includes text and image inputs, tool calling, and a 1-million-token context window.

Getting started

To use this model:


Bring public web information into your AIP workflows

Date published: 2026-11-03

Web search lets supported OpenAI models in AIP find information from public web sources and return answers with citations. Use web search to research recent developments, consult documentation, and build applications that draw on information beyond a model’s training data.

Web search is supported through Direct OpenAI and Amazon Bedrock on eligible enrollments. Developers can use it through AIP’s OpenAI-compatible Responses API, sending requests from applications and scripts directly or through an OpenAI SDK.

Learn more about using the provider-compatible APIs.

Getting started

Enrollment administrators can enable web search in Control Panel > AIP settings > Advanced AIP Settings. Turn on Enable web search via Bedrock or Enable web search via Direct OpenAI for the provider you want to use. Complete any required Direct OpenAI agreements and save your changes.

Before using web search:

Your feedback matters

We want to hear about your experiences using language models in the Palantir platform and welcome your questions and feedback. Share them through Palantir Support channels or on our Developer Community ↗ using the language-model-service tag ↗.


Pipeline builder defaults to faster pipelines, now with LLM support

Date published: 2026-11-03

Faster pipelines are now the default in Pipeline Builder, with new support for Use LLM nodes. You can now build large language model (LLM) workflows in faster pipelines using Palantir-provided models or your own registered models.

Faster pipelines by default

When you create a pipeline from the Pipeline Builder landing page or through AI FDE, faster is now the default selection. Faster pipelines are powered by DataFusion ↗, an open-source query engine written in Rust ↗. Compared with standard Spark pipelines, faster pipelines can reduce execution time and compute resource usage.

Faster pipelines are selected by default when creating a pipeline from the Pipeline Builder landing page.

Faster pipelines are selected by default when creating a pipeline from the Pipeline Builder landing page.

Use LLM support in faster pipelines

Faster pipelines now support Use LLM nodes and Text to Embeddings nodes with both Palantir-provided models and your own registered models. Bring LLMs into your pipeline to power critical workflows.

The Use LLM board in a faster pipeline with the model selector open.

The Use LLM board in a faster pipeline with the model selector open.

Tell us what you think

We welcome your feedback. Share your thoughts with Palantir Support channels or our Developer Community ↗ using the pipeline-builder ↗ tag .