Government Overview
Private AI from headquarters to the edge, with AIP-adjacent workflows and controlled pilot paths.
What this page is for
Government docs should answer procurement, authorization, mission workflow, and deployment questions. They should not imply authorization status, marketplace availability, or partner certification unless that path is formally complete.
TARX role
TARX is the local-first private AI runtime at the edge of the work: the user device, local files, approved tools, private memory, and mission context.
Government teams can evaluate TARX through:
- local-first mission workflows
- memory and Vault boundaries
- approved tools
- policy-controlled routing
- evidence review
- AIP-adjacent workflow architecture
Palantir AIP framing
TARX is designed to complement Palantir AIP, not replace it. Palantir is the governed operational layer. TARX brings private AI closer to users, devices, local context, and edge workflows.
The integration path is architecture-first: connect local TARX context into governed Palantir AIP workflows only when policy allows.
Readiness posture
Use three status labels:
| Status | Meaning |
|---|---|
| Available now | Product surface exists and can be reviewed. |
| Pilot-ready | Suitable for controlled workflow evaluation. |
| Roadmap / partner-dependent | Requires partner, procurement, authorization, or implementation path. |