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

Plintir / Products / NEXUS

Plintir NEXUS

Intelligence Data Fabric & Mission Ontology

Every source, one mission model

Intelligence organisations rarely lack data. They lack a single, trustworthy model of what that data means. NEXUS is the foundation the rest of the suite is built on: it ingests from anything, resolves entities, and holds one mission ontology that every analyst, application and model works against.

SOURCESNORMALISEONTOLOGY

PB

Scale of governed mission data

Billions

Objects and relationships served

<2s

Typical entity search response

100%

Records carrying source and marking

Capabilities

What NEXUS does.

Connect anything, keep the markings

Batch, streaming, change-data-capture, message bus, API and file drops. Classification labels, handling caveats and source reliability travel with the record from ingest to briefing slide.

Streaming & batchCDCLegacy adaptersGeospatial formats

Resolve entities, keep the evidence

Candidate matching, scoring and analyst review turn eight records about one vessel into one vessel with eight sources. Every merge is reversible and every split restores the originals.

Probabilistic matchingReversible mergesEvidence per linkConfidence scoring
Plintir · NEXUS · Source registry142 connected sources · 3.4 TB ingested today Synthetic data
SourceClassVolume / dayMarkingLineageHealth
SRC-0118Streaming412 GBU//FOUOCOMPLETE
98%
SRC-0204Imagery1.9 TBCONTROLLEDCOMPLETE
94%
SRC-0311Legacy DB84 GBU//FOUOCOMPLETE
89%
SRC-0356Reporting12 GBCOMPARTMENTEDCOMPLETE
100%
SRC-0402Open source220 GBPUBLICPARTIAL
61%
SRC-0455Sensor feed760 GBU//FOUODEGRADED
34%

Health is about trust, not uptime. SRC-0455 is still delivering, but late and incomplete — so anything derived from it is flagged as degraded rather than quietly presented as current.

One ontology, every application

Entities, observations, tracks, events, reports, relationships, locations, assets, tasks, plans and assessments are modelled once and reused everywhere — no per-application data model drift.

Typed relationshipsTime validityVersioned objectsShared semantics

Lineage that survives audit

Every derived value traces back through each transform to the original source record, so an assessment can be defended line by line months after it was written.

Full lineageImmutable auditData quality gatesCertified data products
Plintir · NEXUS · Entity resolutionReview queue · 28 candidates Synthetic data
Candidate pairMatch basisScoreShared evidenceDecision
VES-4471 ↔ VES-8802Hull, call sign, track
0.91
6 observationsMERGE
PER-3341 ↔ PER-9014Name variant, location
0.58
2 reportsANALYST
ORG-1174 ↔ ORG-2205Address only
0.31
1 recordREJECT
FAC-0093 ↔ FAC-0121Coordinates ±400 m
0.44
3 observationsANALYST
ACC-7712 ↔ ACC-7719Device, behaviour
0.77
9 observationsANALYST

Selected · VES-4471

Merge is reversiblepolicy

Splitting restores both source records untouched.

Downstream products6 affected

Any assessment citing either entity is flagged for review on merge.

Evidence retained6 items

Each contributing observation stays attached to the merged entity.

Authorityanalyst

Automatic merge is disabled above 0.85 by policy configuration.

Nothing merges silently. Even a 0.91 match records who accepted it and what evidence supported it, because a wrong merge quietly contaminates every product built on it afterwards.

Deploys where you work

One platform, every environment.

NEXUS 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 NEXUS 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.