Welcome to Zequent 2.0

Zequent connects your drones, docks, sensors and effectors to one platform, lets you describe how they should respond — as Skills and Applications — and starts those responses by itself when something happens. This page shows you where to begin, depending on what you came to do.

Using the console?

The guides walk you through every console screen, step by step: connect your devices, build responses, and run your fleet day to day. Start with the Quickstart: a complete radar-to-drone response with simulated devices, no hardware needed.

These docs cover building on the platform with code: the SDKs, adapters, the API reference and the concepts behind them.

Choose your path

Operators

Run the fleet day to day from the console: watch, command, approve.

  1. 1Find your way around the console
  2. 2Watch your fleet
  3. 3Follow a run

Solution builders

Design automated responses and decide when they start.

  1. 1How Zequent works
  2. 2Build a Skill
  3. 3Combine Skills into an Application
  4. 4Start a response when something happens

Integrators

Connect your own software and third-party systems to the platform.

  1. 1Applications & Skills (concepts)
  2. 2Client SDK quick start
  3. 3Integration Hub
  4. 4Migrating from 1.3

Administrators

Set up organizations, users, sign-in and devices.

  1. 1Organizations & single sign-on
  2. 2Connect your devices
  3. 3Practice with simulated devices

What changed in 2.0

2.0 replaces missions and tasks with Applications and Skills: reusable, versioned responses built from the commands your devices offer, started by hand, on a schedule, or automatically by an event. The full list of changes — and the exact version of every component in each release — is in the changelog. Coming from 1.3? Start with the migration guide.

Was this page helpful?