Meridian
Meridian Platform · Drone & counter-drone (C-UAS) integration

Drone operations

Status · In development

Brings drone video and positions into your command picture — next to your incidents, units and sensors — and, next, counter-drone detections.

Role
Act, from the air
Primary user
Drone operators & patrols
Core value
Live drone video and positions in the control room, next to your incidents.
The operational friction

Drone video without context is just video.

Most fleets stream to a vendor app on a separate screen. The pilot sees pixels; the control room sees nothing. And a hostile drone over the perimeter is often noticed only when someone happens to look up.

Capabilities
01

Live drone video in the control room

The drone’s video and position appear in the incident, on the same map the control room uses. Running today with a test drone; professional platforms follow with our pilots.

02

Detection on video

Existing AI video analytics provides the recognition capability. Connecting detections from drone footage to incident workflows and operator confirmation is the next integration step on our roadmap.

03

Geofences & flight zones

Zones, corridors and no-fly areas drawn on the shared map, with alerts when they are crossed.

04

Counter-drone (C-UAS) integration

Detections from existing radar and RF sensors placed in the operational picture, next to your own drones.

Architecture

Built to integrate, not to fly.

Drone operations connect to the drone and counter-drone systems you choose rather than replacing them. Video and detections stay in your environment — never through a foreign cloud.

Data architecture: your own data layer
Sovereign framework

Every part of Meridian is designed on the same sovereign architecture: European engineering, customer-controlled keys and no telemetry — for your own cloud, on-premise or air-gapped environment. Deployment is scoped to your operational and applicable legal requirements.

Sovereignty