AIC Constellation: intelligence software for the work your team needs to do

Intelligence teams need to answer questions, explain their judgements and deliver useful work within a budget. The software should support that chain of responsibility. A larger platform is only useful when its capabilities match the task and can operate in the environment where the team works.

AIC Intelligence Constellation brings together six specialist products: CORTEX, NERVE, GTK 2.0, PAL.NET, PULSE and LINC. All are available for customer demonstrations. Each has a defined role, so a discussion can start with the capability you need and the evidence that would justify buying it.

Choose the intelligence job first

Start with a specific problem. An analyst may need to reconstruct the evidence behind a report. A data owner may need to make approved records searchable without exposing restricted holdings. A geospatial team may need to exploit imagery where connectivity is unreliable. An engineering team may need typed access to an existing Palantir environment.

These tasks have different users, dependencies and costs. A government department, a deployed team and an international security organisation may also have different hosting, identity and release requirements. Constellation makes the product responsibilities explicit. The ecosystem architecture provides the starting point for deciding which interfaces a proposed workflow needs.

CORTEX: keep the question and the report connected

CORTEX intelligence lifecycle software connects requirements, collection activity, evidence references, analysis, review and controlled release. The practical question is whether a reviewer can understand how an intelligence product answers the original requirement and which sources support its conclusions.

That record remains available when an assessment changes. Earlier reports, their supporting evidence and their release decisions stay linked to the versions used at the time. Optional drafting assistance prepares material for the analyst to review; people retain judgement, approval and release authority.

The CORTEX lifecycle walkthrough gives buyers a concrete process to examine. In a demonstration, bring an approved question and ask the team to follow it through to a reviewed report, including one challenged judgement and one changed source.

NERVE: recover the source behind the answer

NERVE preserves the information beneath the assessment. It commits accepted originals before extraction, records each transformation and supports governed discovery through exact source locators. An extracted passage, message or search result retains a route back to the material from which it came.

NERVE applies access rules before producing search results, counts and facets. This matters when teams share infrastructure but have different authority to inspect its holdings. Include a user denied access to one source in the demonstration and inspect what that user can discover.

The NERVE mixed-source scenario illustrates the distinction between source records and derived content. Check your actual formats and connectors, then test whether earlier citations remain usable after a new processing run.

GTK 2.0: work through geospatial evidence locally

GTK 2.0 connects collection tasking, multi-threaded ingest, imagery viewing, analyst review and reporting. Teams can inspect incoming imagery while ingest continues and retain source metadata alongside reviewed observations. Connected, intermittent and disconnected profiles support work in different operating environments.

A useful demonstration uses representative collection sizes, coordinate systems and target hardware. Inspect whether metadata survives processing, which dependencies remain local and how an analyst reviews assisted outputs. The result should establish the workload that the proposed configuration can handle.

The disconnected GEOINT scenario explains a possible contribution from GTK, NERVE and CORTEX. It is an illustrative workflow. The exchange formats and receiving interfaces still need to be agreed for the proposed installation.

PAL.NET: connect .NET applications to Palantir

PAL.NET serves software engineers building applications against supported Palantir Foundry, AIP and customer Ontology services. It provides a licensed .NET access layer with typed contracts and a compatibility approach that can be checked against the application’s required operations.

The cost question is concrete: how much application code will the team otherwise need to write, maintain and retest as services or models change? Compare that work with the SDK’s supported surface, licence and upgrade arrangements.

The PAL.NET integration walkthrough explains the developer workflow. Bring the operations, model and target framework to the demonstration. Platform access and permissions remain part of the customer’s application environment.

PULSE and LINC: assessments and accountable exchange

PULSE is the recurring area-assessment service. A watch defines a place, intelligence questions and a publication cadence. Dated editions are structured around those requirements, with sources, judgements, an outlook and analyst review. Security, travel-risk and crisis teams can assess whether this delivers the recurring intelligence product their decisions require.

LINC addresses the exchange between systems. Its responsibilities cover message contracts, routing and transfer state while each product retains authority over its own information and decisions. A demonstration should examine what happens when policy is unavailable, a recipient’s permission changes or a link returns after an interruption.

The PULSE assessment evaluation follows a recurring assessment through source review and successive editions. The LINC exchange evaluation examines message authority, interruption and acknowledgement. Both provide illustrative exercises to use when planning a customer demonstration.

Engineering, simulation and collection across AIC

The wider AIC product portfolio supports the systems around intelligence production. FOUNDRY supplies reusable .NET engineering capability, while FOUNDATION supplies project templates and delivery scaffolding. SYNAPSE connects VBS4 to external systems; the VBS terrain products provide national coverage and detailed training-area content.

AeroGuard addresses drone command security and telemetry, and NAUTILUS supports maritime autonomy. These products can be demonstrated against their own requirements. Where a workflow combines products, define the interfaces, permissions and responsibilities for the information exchanged.

Supporting engineering records cover SHACE protected transport, SIGIL classification metadata for .NET and CITADEL software licensing and offline activation. The Constellation architecture also describes MARKER for classification-aware marking and information-flow policy. These component and project records explain how particular engineering responsibilities are addressed within a proposed system; the application scope, supported interfaces and commercial arrangements are agreed with AIC.

AIC products for commercial operations

AIC also offers products for other operational teams. LETO supports property operations, Ezilo manages ANPR parking workflows, eCases organises legal matters, and Stafr coordinates event staffing and crew bookings. Each has its own product scope and customer demonstration. The AIC product catalogue provides the full route into the portfolio.

Compare the whole cost of a usable capability

AIC’s proposition is to scope the purchase around the intelligence problem. Select the required products, define the interfaces and price the work needed to make the capability usable. Include licences, installation, infrastructure, integration, training, support and future changes in the comparison.

The intelligence software cost guide explains how to compare those commitments. A saving should come from a like-for-like evaluation and quotation that covers the same workload and acceptance criteria.

For a focused demonstration, send AIC’s commercial team the task, relevant product, operating environment and a proposed success criterion, or contact AIC. A non-sensitive outline is enough to arrange the first discussion.