Skip to content

[ AUTONOMOUS FIRE SUPPRESSION ]

Fire moves fast.
We move first.

A swarm of 5 to 15 aircraft. Ember maps the fire, Cinder takes the interior, Vulcan takes the wildfire, and one operator commands all of it through AD.OS.

10–15min

Detection-to-response

[TARGET]

8–12min

Full suppression cycle

[SIMULATED]

5–15UAS

Coordinated per swarm

[DESIGN]

16L

Vulcan tank capacity

[SPEC]

Live · Active wildfires · California

ACQUIRING FEED…

The fleet

[ 3 AIRFRAMES · DETECTION · CONSOLE ]

[ GROUND CONTROL SYSTEM ]

AD.OS

The console that commands the swarm. Fire Watch common operating picture, peer-to-peer tasking, airspace guard, TAK & SITREP out.

See the console

One continuous response

01

Detect

Detections arrive from CAL FIRE incident feeds, ALERTCalifornia cameras, or a Watchtower of your own on a nearby roof. However it starts, it lands in AD.OS as a verified track.

02

Deploy

Ember launches first and maps the fire. Five to fifteen aircraft then allocate themselves peer-to-peer, with no central controller, while the operator watches one console.

03

Suppress

Cinder takes the interior and the spot fires. Vulcan takes the head fire and draws the containment line. Refill, relaunch, repeat.

[ INTEROPERABILITY ]

No new sensors required.

CAL FIRE DATA · ALERTCALIFORNIA CAMERAS · FIRIS PERIMETERS ·ADS-B AWARENESS · TAK / CoT OUT · SITREP EXPORT

Inside the fire ecosystem

[ JANUARY · PACIFIC PALISADES ]

"Watching helicopters grounded by weather while the fire ran, one question became impossible to ignore: why aren't autonomous drones fighting these fires?"

Why we build