Plintir // Actionable intelligence // Interface visuals use synthetic data

Plintir / Products / OUTPOST

Plintir OUTPOST

Tactical Edge Intelligence

Works when the link does not

Connectivity is a planning assumption that fails exactly when it matters. OUTPOST pre-positions the mission package, runs search, geospatial workflows and local inference on the node itself, and keeps working for days without the enterprise — then rejoins without corrupting the picture it left behind.

LINK DOWN LOCAL INFERENCE

24–72h

Autonomy without core connectivity

0

Auto-merged conflicting edits

On-device

Inference and retrieval

Encrypted

Data at rest with remote revocation

Capabilities

What OUTPOST does.

Days of autonomous operation

A configurable mission profile holds 24 to 72 hours of independent capability using pre-positioned data with a local identity and policy cache, so authorisation still works offline.

24–72h autonomyLocal identity cacheCached policyMission packages

Inference at the node

Compact models run on device for retrieval over the mission package, imagery triage and sensor classification, without a single prompt leaving the node.

On-device modelsLocal retrievalImagery triageNo egress required
Plintir · OUTPOST · Node statusNODE-11 · field analytic profile · disconnected Disconnected

Autonomy

06:41:22

Disconnected · profile limit 72 h

Local identity cache
VALID · 61 h
Policy cache
VALID · 61 h
Mission package
PKG-0442 · 2.1 TB
Local audit
1,284 entries

Local capability

Search over package
ONLINE
Geospatial & timeline
ONLINE
Entity workflows
ONLINE
On-device inference
ONLINE
Cross-domain transfer
BLOCKED
Enterprise graph expand
DEFERRED

Degradation is declared, not disguised.

Store & forward queue

Observations captured
341
Entity updates
28
Imagery chips
17 · sending
Local assessments
6
Conflicts held for review
3

Replay is in provenance order. Conflicts are never auto-merged.

Autonomy is a configured commitment. The mission profile defines exactly which capabilities survive a link outage and for how long, and the node reports honestly against that promise.

Honest degradation

Functions unavailable offline are shown as unavailable. The interface never returns a partial result dressed up as a complete one.

Declared degradationCapability statusStale indicatorsOffline audit

Safe synchronisation

On reconnection the node replays in provenance order. Conflicting edits are held for analyst review with both versions and their sources, never auto-merged.

Provenance-order replayConflict reviewStore and forwardSigned updates
Plintir · OUTPOST · Synchronisation reviewReconnected 00:04:12 ago · 3 conflicts held Synthetic data
ObjectNode versionEnterprise versionDivergenceResolution
ENT-8890Position grid 44SPosition grid 51TBoth observed 1340ZANALYST REVIEW
FAC-0093Status ACTIVEStatus DORMANTNode observed laterANALYST REVIEW
TK-7730Confidence 0.41not presentNew at nodeACCEPTED
OBS-9911341 newnot presentNew at nodeACCEPTED
ASM-0104Draft revisedDraft revisedConcurrent editANALYST REVIEW

Last write does not win. Where the node and the enterprise disagree, both versions are preserved with their sources and an analyst decides — because a silently overwritten observation is an intelligence failure with no audit trail.

Deploys where you work

One platform, every environment.

OUTPOST runs identically in commercial cloud, sovereign cloud, on-premises, high-side and fully air-gapped estates, and degrades predictably at the tactical edge.

Sovereign cloudOn-premisesHigh-side Air-gappedTactical edgeCoalition workspace Zero trustAttribute-based accessImmutable audit

Next step

See OUTPOST against your own mission thread.

We run briefings on a real mission problem you bring, not a scripted demonstration. Bring the question your analysts cannot currently answer.