PLATFORM ACCESS LAYER FOR .NET
PAL
One strongly typed .NET surface for Palantir Foundry, AIP and your own Ontology.
PAL.NET is the Platform Access Layer for .NET: a closed-source, licensed SDK that gives .NET teams one coherent, strongly typed way to work with Palantir Foundry, AIP and their own customer Ontology.
Product Type
Developer SDK
Product Code
AIC-PAL
Deployment
Distributed through authenticated private NuGet feeds or licensed offline bundles for disconnected and restricted environments.
Key Differentiator
A licensed, strongly typed .NET 10 SDK that treats the platform API surface and the customer Ontology as first-class, versioned contracts rather than hand-rolled HTTP calls.
The Platform Access Layer for .NET
PAL.NET is a closed-source, licensed software development kit that gives .NET teams a single coherent way to work with Palantir Foundry, Palantir AIP and their own customer Ontology. It targets .NET 10 and is built for engineers who want to write application code, not HTTP plumbing.
The SDK exposes two related surfaces. The platform surface covers the services teams use to move, inspect and operate on data. The Ontology surface covers the customer’s own object and link model, available either as generated strongly typed C# contracts or through dynamic, metadata-driven access when the shape of the model is only known at runtime.
PAL.NET has been in operational use for over a year. It is now being publicised and made available more widely. Product information is available at pal.aic.io.
The Challenge
Teams integrating with a data platform of this scale usually start by hand-writing HTTP clients. It works for the first endpoint and degrades from there. Request and response shapes drift, error handling is inconsistent between modules, cancellation is an afterthought, and the Ontology, the part most specific to the customer, ends up represented as untyped dictionaries.
The cost is rarely the initial build. It appears later, when the platform moves. Without a stated compatibility contract, every upstream change becomes an investigation rather than a planned upgrade, and teams in restricted environments cannot easily tell which version of the SDK is safe to deploy.
The Capability
PAL.NET presents the platform through strongly typed, async-first contracts. Payloads are immutable records, operations accept cancellation tokens, and capabilities are registered modularly so an application takes a dependency only on the parts it actually uses. Connectivity, datasets, filesystem, data health, streams, SQL queries, functions, orchestration, media sets, map rendering, models, the LLM proxy, AIP agents, admin, audit, checkpoints and the sensitive data scanner are all addressed through the same conventions.
The Ontology surface is treated with the same seriousness as the platform surface. Generated contracts give compile-time safety where the model is known, and the dynamic path covers the cases where it is not, including specialised Ontology data access. Both sit on the same runtime, so a team can move between them without changing how it authenticates, handles errors or cancels work.
Compatibility is published rather than implied. An API Compatibility Manifest records what the SDK supports, and release gates are tied to it, so an upgrade is a decision with evidence behind it. PAL.NET reuses the existing AIC.Foundry and AIC.Foundation libraries, which keeps its internals consistent with the rest of the AIC .NET estate.
What It Changes
Connecting becomes a configuration task rather than a project. A developer registers the capability groups the application needs, supplies credentials, and starts calling typed methods. Adding a second or third capability later does not require revisiting the integration layer, because the conventions do not change between them.
PAL.NET is designed to add no more than five milliseconds of SDK overhead at the 95th percentile for payloads up to 64 KiB, measured excluding network time. The intent is that the access layer stays out of the way of the performance characteristics of the platform itself.
Licensing and Distribution
PAL.NET is closed source and licensed. It is distributed through authenticated private NuGet feeds, or as licensed offline bundles for disconnected and restricted environments. Entitlement checks are fail-closed: without a valid licence the SDK does not operate.
The SDK runs inside the customer’s own application estate and introduces no separate data store of its own. Credential handling and transport security follow the host platform and the customer’s deployment policy.
Capabilities
Datasets; Filesystem; Connectivity; Data Health; Streams; SQL Queries; Functions; Orchestration; AIP Agents; Models; LLM proxy; Media Sets; Map Rendering; Notepad; Workbench; Admin; Audit; Checkpoints; Sensitive Data Scanner; Ontology runtime and specialised Ontology data access
Integrations
Palantir Foundry; Palantir AIP; customer Ontologies; AIC.Foundry; AIC.Foundation; authenticated private NuGet feeds; licensed offline bundles
Identity Support
Platform-native authentication, with fail-closed licence entitlement checks at runtime.
Data Residency
PAL runs inside the customer’s own application estate and does not introduce a separate data store.
Encryption
Transport security and credential handling follow the host platform and deployment policy.
Other Products
Explore More Products
Browse the wider AIC product portfolio and see how each capability supports secure, mission-focused operations.
