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 ↗.

---

Introducing SQL Studio, Foundry's dedicated SQL application

Date published: 2026-05-07

SQL Studio, Foundry's dedicated application for writing and running SQL queries, is now available in beta. SQL Studio brings interactive SQL analysis to Foundry across both tabular data and ontology object types, backed by purpose-built SQL engines and AI-assisted query writing.

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

SQL Studio builds on the contextual SQL console embedded in applications such as Dataset Preview, Data Lineage, and Ontology Manager, now providing a dedicated application with read and write SQL support for tabular data, read support for ontology object types, and the ability to publish reusable Ontology SQL functions.

Powered by Ontology SQL and Furnace

SQL Studio is built on two Foundry SQL engines that share a common Spark SQL dialect: Ontology SQL for querying ontology object types, and Furnace for querying tabular data.

Ontology SQL is Foundry's SQL engine for querying ontology object types 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.

Furnace is Foundry's SQL engine for tabular data. It dynamically routes queries between Trino and Spark, delivering meaningfully faster query times for the right workloads. Furnace supports both read and write operations.

Key features

SQL Studio brings together a complete SQL analysis experience in one place:

• Unified data and object querying: Query tabular data and ontology object types from a single application, switching between data mode and object mode, while using a common Spark SQL dialect.
• Low-latency, interactive analysis: SQL Studio is built for iterative, interactive development workflows. Queries are dynamically routed to the most appropriate compute engine, including faster non-Spark options for supported query shapes, and run on warm, fully managed compute.
• AI-assisted code generation: A conversational AIP side panel helps you write, explain, and debug queries. It understands Foundry's supported SQL dialect and has visibility into your editor, including the current code and schemas for any referenced datasets, tables, object types.
• Preview results as tables or charts: View query results as tabular output or visualize them with built-in line and bar charts. Result limits are configurable, with the option to return up to 10,000 rows per query rather than the default 1,000-row preview for users with the appropriate permissions.
• Save and share SQL worksheets: Use the scratchpad for one-off analyses, or save your work as a SQL worksheet. Worksheets can be saved privately for personal reuse or in a project to share with colleagues. Saving creates a new version that you can review and restore later; unsaved changes are auto-staged so a user’s in-progress work persists between sessions.
• Read and write support: In addition to SELECT queries, SQL Studio supports CREATE TABLE operations on datasets and CREATE, INSERT, UPDATE, and DELETE operations on Iceberg tables.
• Ontology SQL functions (Beta): Define reusable, parameterized SQL queries over object types and publish them as SQL functions. Supported query shapes can execute with low latency on the same in-memory path as Ontology SQL queries. Use them across Foundry, including in Workshop, Actions, Automate, and the Ontology SDK. SQL functions are experimental and are not enabled on all Foundry environments, contact your Palantir representative to enroll.

Getting started

To get started with SQL Studio, Foundry administrators should enable the application from the Application access page of Control Panel. Once enabled, SQL Studio is directly accessible from the Applications menu.

For information about SQL Studio features, see the SQL Studio documentation. For syntax guidance, refer to the SQL dialect documentation. To learn more about the underlying engines, see the Furnace and Ontology SQL overviews.

What's coming next

SQL Studio is under active development, and several capabilities are on the near-term roadmap, including:

• Global branching and Marketplace packaging support for SQL worksheets.
• Application usability improvements, such as multiple editor tabs, improved query history, and more chart type options.
• Integration with Foundry's production pipeline tooling and Git-based CI/CD development workflows.

We want to hear from you

As we continue to develop SQL Studio, we want to hear about your experiences and welcome your feedback, both about the SQL Studio application and the broader SQL experience in Foundry. Share your thoughts with Palantir Support channels or our Developer Community ↗.

---

Replace language models used by AIP Logic functions in bulk from Workflow Lineage

Date published: 2026-05-07

You can now replace a language model used by multiple AIP Logic functions in a single action from Workflow Lineage instead of opening each function and updating the model individually. The ability to bulk replace models is now generally available across Foundry enrollments, making it easier to migrate workflows off deprecated models and evaluate new models across an entire workflow.

Choose an existing language model node on a Workflow Lineage graph to swap models in multiple AIP Logic functions.

Follow the instructions in the Workflow Lineage documentation to bulk replace models backing your AIP Logic functions with any model provided by Palantir. Support for bulk model replacement with additional resource types beyond AIP Logic functions is in development.

To migrate off deprecated models, review the model deprecation guide.

Your feedback matters

We want to hear about your experience using the Replace model feature in Workflow Lineage. Share your thoughts with Palantir Support channels or on our Developer Community ↗ using the workflow-lineage tag ↗.

---

GPT-5.5 is now available in AIP

Date published: 2026-05-05

GPT-5.5 is now available from Azure on US and EU georestricted, and non-georestricted enrollments. The model is available from OpenAI on US georestricted and non-georestricted enrollments.

Model overview

GPT-5.5 is OpenAI's newest model, excelling at agentic coding, debugging, research, tool calling, and a wide range of other tasks. For more information, review OpenAI's model documentation ↗.

• Context window: 1,050,000 tokens
• Knowledge cutoff: December 1, 2025
• Modalities: Text, image
• Capabilities: Reasoning tokens, function calling, structured outputs

Getting started

To use this model:

• Confirm that your enrollment administrator has enabled the relevant model family.
• Review token costs and pricing.
• See the complete list of all available models in AIP.

Your feedback matters

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

---

Global Branching is generally available May 18: branch, test, and merge across applications

Date published: 2026-05-05

Starting the week of May 18, 2026, Global Branching (formerly Foundry Branching) will be generally available to all users on all enrollments. Global Branching provides a shared workflow to make changes across multiple applications on a single branch, test those changes end-to-end without disrupting production workflows, and merge them back into Main. Consult the Global Branching documentation to learn more.

Reviewing main branch updates and resource check status in Ontology Manager.

Supported applications and workflows

Global Branching is available for transforms and TypeScript v1 functions repositories, Pipeline Builder, the Ontology, Workshop, AIP Logic, and Object Views.

A proposal overview showing resources, approval status, and the "Do not merge proposal" setting.

For these applications, the following workflows are supported:

• Branch and modify resources: Create or access a branch, and make changes to resources without affecting the Main branch.
• Remove resources: Remove a resource from a branch to reset it to its state on the Main branch.
• Include new updates from Main and resolve conflicts: Rebase your branched resource to update it with the latest changes from the Main branch. If conflicts exist, you will be redirected to the appropriate application to resolve them.
• Protect resources: Resource owners can protect resources so that changes must go through a branch and receive approval before merging.
• Define approval policies: Project owners define approval policies specifying eligible reviewers, required approvals, and whether contributors can self-approve. For Code Repositories and Pipeline Builder, you define policies within the resource itself.
• View branched resources: Use Data Lineage to inspect the branched state of your resources and trace how changes propagate.
• Clear all checks and merge changes: When a proposal is created, the system runs checks on each resource to surface issues such as conflicts or missing approvals. Once all checks pass, you can merge your proposal.

Updated security model and branch lifecycle

When Global Branching is GA, the security model and branch lifecycle will feature:

• Simplified merge permissions: Previously, merging required a dedicated branch role. Going forward, any user who can view a proposal can merge it once all approvals and checks are satisfied. A new Do not merge setting allows branch owners to block merges until they are ready.
• Revamped branch lifecycle: Inactive branches will have ontology resources de-indexed and data eventually deleted, but all logic is preserved. Branches will no longer be auto-closed. Instead, branches can be manually archived and restored at any time.

Restricted Views, Automate, and what's ahead

Restricted Views and Automate are now available in beta. The core branching workflow is functional, but some GA-level features — such as approval integration and removing a resource from a branch — are not yet available. Contact Palantir Support to enable, and consult the application-specific documentation to learn more about each application's current scope.

Beyond these two applications, we are actively working to expand branching support across the Palantir platform, starting with OSDK, TypeScript v2 and Python functions, and Developer Console.

Your feedback matters

Have thoughts on Global Branching? Let us know through Palantir Support channels and our Developer Community using the global-branching tag ↗.