Watchkeeper
Multi-Sensor Fusion
New
Sense layer

What if every sensor you own, from every supplier, produced one trusted track instead of five competing alerts?

Many sensors, one track. The fusion layer that makes mixed sensor estates usable.

  • Sensor fusion
  • SAPIENT
  • Counter-drone
  • Feeds Consilium

What it does

System behaviour

Watchkeeper is the fusion layer. It turns many sensor reports into one track per object, so Consilium can orchestrate a single, coordinated response.

Watchkeeper connects to radars, RF detectors, Remote ID receivers, cameras and other sensors through SAPIENT and vendor-specific adapters. It fuses their detections into one track per object, carries the source and confidence of every contribution, and passes the fused picture to Consilium, where playbooks orchestrate the response. It is the fusion that runs behind Espanaro's multi-sensor drone defence demonstration.

Position in the ecosystem: Watchkeeper feeds Consilium with fused tracks, takes sensor health from Pulse Sentinel so a degraded sensor carries less weight, and can protect tracks with ByteHarbour so they are shared by attribute with partners and allies.

Three principles

Fuse once, then orchestrate

Open

Connects through SAPIENT and vendor adapters, so mixed estates can be fused without replacing kit.

Explainable

Every fused track shows which sensors contributed and how confident the picture is.

Orchestration-ready

Fused tracks go straight into Consilium, where playbooks decide and operators act.

The challenge

Sensor estates are now bought from many suppliers. Each sensor raises its own alerts, in its own format, on its own screen.

Operators are left to decide by eye whether three alerts are one drone or three, and which sensor to believe.

Operational value

Watchkeeper delivers:

  • One track per object
  • Source and confidence on every track
  • Open adapters, including SAPIENT
  • Feeds Consilium playbooks
  • Sensor health taken into account
New

Watchkeeper is a new Espanaro product, built and working end to end in the multi-sensor drone defence demonstration, where the sensors and drones are simulated. It is ready to integrate with your sensors and deploy.

Architecture

How it works

Watchkeeper works in four steps, from ingest to publish.

WATCHKEEPER · MULTI-SENSOR FUSION 01 INGEST Detections from every connected sensor 02 ASSOCIATE Reports of the same object linked 03 FUSE One track with source and confidence 04 PUBLISH Track sent to Consilium to orchestrate SENSOR FUSION · SAPIENT · COUNTER-DRONE · FEEDS CONSILIUM
  1. 01IngestDetections from every connected sensor
  2. 02AssociateReports of the same object linked
  3. 03FuseOne track with source and confidence
  4. 04PublishTrack sent to Consilium to orchestrate

Demonstration

Multi-sensor drone defence

Radar, RF detection and Remote ID fused into one track per drone, then orchestrated in Consilium. Sensors and drones are simulated. All demonstrations

Capabilities

What Watchkeeper does

Ingests detections from SAPIENT-connected sensors
Connects non-SAPIENT sensors through vendor adapters
Associates reports of the same object from different sensors
Produces one track per object, with source and confidence
Checks tracks against a register of friendly or authorised objects
Takes sensor health from Pulse Sentinel into account
Publishes fused tracks to Consilium for playbooks and operator decisions
Records the contributing detections behind each track

Use cases

Where Watchkeeper makes the difference

01

Counter-drone

Fuse radar, RF, Remote ID and camera detections into one track per drone.

02

Base and site protection

One picture across the sensors on a base, prison or critical site.

03

Force protection

Fuse a deployed unit's own sensors at the edge.

04

Mixed estates

Bring sensors from different suppliers into one picture without replacing them.

Integration and deployment

How Watchkeeper connects

Watchkeeper sits between the sensors and the orchestration layer.

Works withConsiliumPulse SentinelByteHarbourSAPIENT sensorsVendor adapters
Integration areaSupported approach
SAPIENTTakes detections from sensors that publish SAPIENT messages.
Vendor adaptersAdapters for sensors that use their own interfaces.
ConsiliumPublishes fused tracks for the common picture, playbooks and operator decisions.
Pulse SentinelUses sensor health so a degraded sensor does not weaken the fused picture.
ByteHarbourTracks can be protected and shared by attribute with partners and allies.

Delivered with Espanaro

Built and supported in the UK

Supported by Espanaro capability

The engineering teams behind Watchkeeper also support its integration, deployment and operation.

How to engage

  1. 1
    Discovery

    Map the sensors you have, their interfaces and where they are.

  2. 2
    Integration Workshop

    Shape adapters, fusion rules and the hand-off to Consilium around your estate.

  3. 3
    Deploy

    Connect Watchkeeper to your sensors and move into operational use, with UK support.

Solution datasheet

Download the Watchkeeper Datasheet

A concise technical overview of Watchkeeper: capabilities, use cases, integration and deployment. Fill in your details and the datasheet unlocks immediately.

  • Technical capability summary
  • Operational use cases and deployment context
  • Integration and ecosystem overview
  • PDF, free to download

Access Datasheet

Free to download. We do not sell your details.

Discuss Watchkeeper

Discuss how Watchkeeper can support your mission

Tell us about your operational requirement. We will respond with clarity on how Watchkeeper fits your environment and what deployment looks like.