How Zequent works

Everything in Zequent follows one chain: your devices report what they can do, you combine those abilities into Skills and Applications, and triggers start them when something happens. This page explains each link of that chain once, so the rest of the documentation reads easily.

Devices and adapters

A device — the platform calls it an asset — is anything you connect: a dock with its drone, a radar, a jammer, a camera. Devices do not talk to the platform directly. An adapter runs next to them and translates the vendor's protocol into the platform's, so a DJI dock and a MAVLink drone look the same to everything above. A dock and the drone inside it are one asset with a sub-asset; see Assets & sub-assets.

Capabilities: what a device can do

Every adapter reports the capabilities of its devices: each command it supports, with the parameters it takes. The platform keeps this list live — when a device goes offline, its commands are no longer offered. You never type command names from memory: the console shows exactly what your connected devices can do. See Connect your devices.

Skills and Applications: your responses

A Skill is one response, drawn as a graph: take off, fly to the alarm, point the camera, wait for an operator's approval, return home. An Application bundles the Skills that belong together — for example everything for protecting one site — and says which devices may run them. Both are versioned, so what ran yesterday can be reproduced. See Build a Skill and Combine Skills into an Application; the full model is in Applications & Skills.

Triggers: when a response starts

A response starts by hand from the console, on a schedule, or automatically through an event trigger — a radar detection, a telemetry threshold, a device changing status, a webhook, or a message from a connected system via the Integration Hub. When two responses want the same drone, priority decides: an alarm takes a drone off routine work, never off equally important work. See Start a response when something happens.

Watching it happen

Every run of a Skill is an execution you can follow step by step, with live video, the map and the approvals it waits for. See Watch your fleet and Follow a run.