[ GROUND CONTROL SYSTEM ]
AD.OS
One operator. One console.
The whole response.
AD.OS is the console that commands the fleet, from Watchtower's first detection through Ember's mapping to Cinder and Vulcan's suppression. Built on a decentralized architecture: the swarm coordinates peer-to-peer, and the console commands intent, not joysticks.
CONSOLE CAPTURE · PENDING
[ HERO-LOOP ]
The console
[ 8 SYSTEMS · 1 SCREEN ]
↳ 01 // FIRE-WATCH
Fire Watch
The common operating picture: live fire perimeters, fleet positions, detections, and intel layers on one map. It is the single screen an operator actually needs.
↳ 02 // TASKING
Swarm tasking
Five to fifteen aircraft allocate themselves peer-to-peer, with no central controller and no single point of failure. The operator sets intent; the swarm settles the assignments.
↳ 03 // DETECTION
Thermal detection
Onboard machine-learning detection turns thermal signatures into verified fire tracks, alongside cues pulled from CAL FIRE incident feeds and ALERTCalifornia cameras. No Veridis-owned sensor is required to start a response.
↳ 04 // AIRSPACE
Airspace guard
ADS-B awareness with closest-point-of-approach alerting. When crewed fire aviation enters the airspace, the swarm knows, and yields.
↳ 05 // TAK
TAK / CoT out
Every track publishes as Cursor-on-Target to TAK and ATAK: the picture your agency already runs, fed automatically.
↳ 06 // FIRIS
FIRIS ingest
Live incident perimeters from the FIRIS aircraft feed render directly in Fire Watch alongside the swarm's own mapping.
↳ 07 // CAMERAS
Camera intel
ALERTCalifornia network cameras join the intel picture on demand, giving context for every detection, off by default, opt-in by design.
↳ 08 // SITREP
SITREP export
One action produces a time-stamped situation report of the incident: positions, actions and timeline, ready for command and after-action review.
On screen
CONSOLE CAPTURE · PENDING
[ TASKING ]
CONSOLE CAPTURE · PENDING
[ CPA-ALERT ]
CONSOLE CAPTURE · PENDING
[ FIRIS-LAYER ]
CONSOLE CAPTURE · PENDING
[ SITREP ]
[ ARCHITECTURE ]
COMPANION COMPUTE
NVIDIA Jetson
onboard autonomy & detection
FLIGHT CONTROL
Pixhawk · ArduCopter
proven flight stack
MIDDLEWARE
ROS 2
modular robotics runtime
MESH TRANSPORT
Zenoh
peer-to-peer, no central node
Every aircraft carries the full autonomy stack. Coordination happens over a peer-to-peer mesh. Lose a drone, lose a link, and the swarm re-allocates around the gap. The console is a window into the system, never a single point of failure above it.
1,175+ AUTOMATED TESTS ON THE AUTONOMY CORE · CONTINUOUS INTEGRATION
See it run on a live operation.
A full console demonstration, detection to suppression, on the simulation range, with your scenario.