Palantir has made Pilot generally available. Pilot is Foundry's tool for building React applications on the Ontology SDK from natural-language prompts. Palantir's October 2026 announcements list the release with a publication date of October 29, 2026.

Palantir describes Pilot as an application builder that creates frontends backed by the Ontology. The company says it "brings application development, Ontology modeling, and deployment into one workspace."

What changed and who it is for

Pilot moves from beta to general availability. Palantir's March 5 Pilot announcement said Pilot would be available in beta "for enrollments with AIP enabled starting the week of March 9." That entry now carries its own update note: "As of the week of October 26, 2026, Pilot is now generally available." Palantir published the general-availability announcement on October 29.

Access depends on configuration. The Pilot overview requires "a Foundry enrollment with Pilot enabled." It also requires permission to create repositories, "typically granted by the Editor role," plus further Ontology, application and domain permissions to deploy. The getting-started guide says Ontology write permissions "are needed only for the definitions you create or modify."

Teams can start from an existing data model. They can also ask Pilot to propose "the object types, relationships, and actions needed to support a new workflow." Users find Pilot by searching for it from the Foundry application menu.

How it works

Pilot builds two kinds of front end, both using the OSDK and React. Standalone applications are deployed through Developer Console and hosted at a subdomain. Custom widgets are sandboxed, publish to the Widget Registry and embed inside a Workshop application.

A build starts with a prompt. Users can supply existing object types and actions as context, or attach documents and images to show requirements and design ideas. They then choose an application or a custom widget.

They also pick a theme: Blueprint components for a Foundry-style interface, or Custom components for a custom visual style. Before building, users set whether Pilot may modify existing entities or create new ones.

"Pilot generates a React application that uses the Ontology SDK and displays it in a live preview," the announcement says. Follow-up prompts refine the interface and behavior. Generated sample data lets users explore how the app behaves.

The workspace has four tabs. Preview shows the live app, and Ontology shows an interactive graph of the object types, action types and relationships Pilot created. Code holds the full source in an embedded editor, and Changes shows code differences and proposals.

Palantir says the code "remains available for developers to inspect and edit as the application evolves."

For a standalone app, Pilot creates a Developer Console application tied to the project. It requests a subdomain and sets application restrictions to include the required ontology entities. "Users authorize through OAuth and can immediately use the application with real data," the overview says.

Build checks are mandatory. "CI checks run and must pass before you can tag and release a version," according to the overview. After deployment, users can return to Pilot's Editor to make changes and release new versions.

Review, permissions and data

Pilot keeps code and Ontology changes on separate tracks. "Code branches contain repository changes," the branches and proposals page says. "They are separate from the Foundry branches used to deploy Ontology definitions."

On the code side, teams can work on separate branches and review changes through proposals. They can ask Pilot to address review feedback or help resolve conflicts, then inspect the changes before merging. A policy "can require an approval, prohibit merging with rejected reviews, or invalidate approvals after new commits."

"A protected branch requires changes to arrive through a proposal," the docs say. Pilot restricts direct editing and Ontology-permission changes on that branch.

On the Ontology side, new or modified definitions can be reviewed and tested through Global Branching before merge. The overview says entities "are promoted to the main ontology through Global Branching and proposals." The Work with data page says that Foundry branch proposal "is separate from the code proposal shown in Pilot's Changes view."

The Ontology permissions setting has a narrow scope. It "does not grant access to real records, authorize an action, or grant permission to deploy a change," the same page says.

Pilot works in an isolated container for application code and local ontology definitions. Even so, actions run while the preview uses production data "can create, modify, or delete real objects," including on a separate code branch. Seed data is not published as production Ontology data when the frontend is deployed.

Where Pilot sits

Pilot arrives alongside related OSDK tooling. On October 15, Developer Console added Global Branching, so teams can test OSDK React app changes "alongside Ontology changes on the same global branch." The `@osdk/react` library, which supplies React hooks for OSDK applications, became generally available the week of May 11.

SuperRepo, described in Palantir's August 2026 announcements, lets teams import existing Ontology entities instead of redefining them in code.

Palantir's announcement and documentation do not specify whether generated code can be exported or maintained outside Pilot. They also do not state supported React and OSDK versions, availability on sovereign or air-gapped enrollments, or Pilot-specific pricing and compute charges.

The Foundry News take and what to watch

In Foundry News's view, Pilot pushes further toward treating the Ontology as the codebase. One tool now covers Ontology modeling, front-end generation and deployment. The object types and actions an app needs are proposed in the same conversation that writes the interface.

Governance sits inside that path. Teams scope whether Pilot may touch existing definitions before it builds. Every release must pass CI checks and carry a release tag, and protected branches force changes through proposals.

For builders, the practical consequence is a two-track review. Code proposals cover the repository, while Global Branching proposals cover the Ontology. Teams adopting Pilot will need to coordinate both, so that a generated app and the definitions it depends on are approved together.

For buyers, the generated code staying open to inspection and editing means reviewers can apply their own engineering standards to it. In Foundry News's view, Pilot complements Workshop, through embedded custom widgets, and SuperRepo rather than replacing either. Palantir's documentation does not describe it as replacing any Workshop capability.

The first thing to watch is whether Palantir documents the open details. Those are code export, supported versions, sovereign and air-gapped availability, and Pilot-specific cost.

The second is how Pilot's code proposals and Developer Console's Global Branching support line up in practice. That will shape how generated apps move from preview to production.