AI detection & inference
Multi-model weighted-box-fusion ensemble — open-vocabulary, grounding, thermal, C-UAS, pose and behaviour — with motion gating and a global tile budget.
The core loop
↻ Closed loop · operator retains acknowledge, launch and abort at every stage
One frame, one decision
Multi-model detection over a single feed, the alert grading it raises, the policy that decides whether a response is warranted, and the dispatch that gets written down. Four beats, in order.

Policy
Level 2 in a monitored sector, cooldown clear — a response is warranted
Dispatch
Nearest available drone routed to the camera’s GPS position · operator retains acknowledge, launch and abort
An illustration of the ICCS loop — detect, classify, decide, dispatch — drawn over a stock aerial photograph. Not a live feed, not a customer deployment, and not a screenshot of the product.
Capability inventory · 11 domains
Detection, sensors, drones, mapping, recording and access control are one system with one audit log — because in an accreditation review, five vendors is five arguments.
Detection, sensors, drones, mapping, recording and access control are one system with one audit log — because in an accreditation review, five vendors is five arguments.
Engineering detail
Numbers from the running system, not a benchmark sheet.
At a glance
80 configured cameras on a single GPU node, with roughly 15–20 concurrently active 1440p streams — CPU-bound, not GPU-bound. Up to four autonomous drones over MAVLink and ArduPilot.
AI model stack
Weighted Box Fusion across a primary detector, a transformer detector, open-vocabulary and grounding models, thermal and sliced-tile inference, plus a counter-UAS tracker. Approximately 28 GB VRAM for the full stack.
Security & deployment
Three-role RBAC, JWT authentication, a tamper-resistant audit log, dormant TOTP MFA and encrypted camera credentials — the controls an assessor asks for, present before they ask.

Motion gating and a global tile budget keep the ensemble inside the compute envelope — which is why 80 configured cameras run on a single node without the GPU becoming the bottleneck.
Measured, in the field
Figures from the classified perimeter programme this engine was proven on. The client cannot be named; the numbers can.
Deployment targets