TechPrufer
Get started
Palantir
Palantir logoPalantir · Feature trail

PFCS Forward Authorization Extension

2 posts · Nov 2025 – Feb 2026

What this trail covers

This post details the evolution of Palantir's authorization model, extending PFCS Forward to cover on-premises and edge environments. This enables a unified 'authorize once, use many' approach across Palantir's software stack (Foundry, Gotham, Apollo, Rubix, AIP) and third-party software deployed via Mission Manager. Key advantages include hardware agnosticism, fostering a multivendor ecosystem, and integrated security across the entire stack. The system leverages Rubix for hardened Kubernetes and Apollo for autonomous deployment, with the Ontology providing granular access controls.

All Palantir trails
  1. Introducing PFCS ForwardThis post introduces PFCS Forward, extending Palantir's IL5/IL6 authorization from cloud to on-premises and edge environments. It details how Rubix (hardened Kubernetes), Apollo (autonomous deployment), and the Ontology (data and access control) enable an 'authorize once, use many' model for the Palantir software stack and third-party software via Mission Manager. This allows for hardware-agnostic deployments, a multivendor ecosystem, and integrated security across the stack, reducing authorization overhead for warfighters.
  2. MediumThis post introduces PFCS Forward, an extension of Palantir's IL5/IL6 authorization model to on-premises and edge environments. It details how this enables a 'authorize once, use many' paradigm for the Palantir software stack and third-party software managed by Mission Manager. The technical contribution lies in the integration of Rubix for hardened Kubernetes and Apollo for autonomous deployment, ensuring hardware agnosticism and a multivendor ecosystem with integrated security.