Rows of unattended control-room consoles, their panels lit in a darkened room
Release v1.25.2 · 27 June 2026

ICCS.
Integrated Command & Control System

AI-driven perimeter security fusing multi-model video detection, multi-sensor ingest, an autonomous drone-response fleet and operator command — in one air-gapped platform. Detect, alert, decide, dispatch, operate: the entire loop, on hardware you own, with no path to the internet.

80cams
On a single GPU node
4UAS
Autonomous response drones
11
Capability domains
8+
Fused AI detection models
100%
Offline / air-gapped capable

Photograph: control-room consoles. Illustrative of the environment ICCS is built for — not an Artikate installation.

The core loop

Detect, alert, decide, dispatch, operate — the entire loop, on hardware you own.

  1. 01

    Detect

    Motion-gated AI ensemble across every configured feed.

  2. 02

    Alert

    Three-level grading, persisted and broadcast in 50 ms batches.

  3. 03

    Policy

    Sector map and cooldown decide whether a response is warranted.

  4. 04

    Dispatch

    Best available drone routed to the camera’s GPS position.

  5. 05

    Operate

    Live feed with acknowledge, launch and abort under operator command.

↻ Closed loop · operator retains acknowledge, launch and abort at every stage

One frame, one decision

The loop, drawn.

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.

An urban road intersection photographed from directly overhead, with buses queued on one approach
DetectAlertPolicyDispatch
11 objects · one feed

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

Every domain shipped, not roadmapped.

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.

One platform, not five integrations

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

Sized, measured and deployable on hardware you already own.

Numbers from the running system, not a benchmark sheet.

At a glance

Scale and response

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.

  • Store · PostgreSQL 16 with SQLite as native development fallback
  • Stack · Python / FastAPI · React / Vite · Ultralytics YOLO

AI model stack

Eight models, fused

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

Built for the accreditation review

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.

  • Deploy · Native · Docker (CPU and GPU) · Windows via WSL2 · offline and air-gapped · systemd service
A row of accelerator cards seated in a rack chassis, status LEDs lit
Accelerator cards in a rack chassis. ICCS is sized to run its eight-model ensemble on one node of hardware the customer owns.

Weighted Box Fusion across eight models

≈28 GB VRAM for the full stack
PrimaryTransformerOpen-vocabGroundingThermal / IRSliced-tileC-UASPose

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

What the detection stack actually returns.

Figures from the classified perimeter programme this engine was proven on. The client cannot be named; the numbers can.

97.8%
Detection accuracy
ARGUS, air-gapped
0.18%
False positive rate
Below the alert-fatigue floor
100%
Offline capable
Tested with the NIC down
94.3%
Acoustic accuracy at −5 dB
SENTINEL, sub-50 ms

The reference implementation

Why this one is the reference.

ICCS is the hardest version of every constraint we work under at once: real-time AI under a compute budget, physical actuation with safety consequences, an operator who cannot be retrained, an auditor who will read the log, and no network to fall back on. Everything else we build is a subset of that problem.

Deployment targets

Native, Docker — CPU, Docker — GPU, Windows via WSL2, Offline / air-gapped, systemd service, PostgreSQL 16, SQLite dev fallback, MAVLink, ArduPilot, ONVIF, MQTT, WebRTC, HLS fallback