MISSION CONTROL · FLEET CONSOLEAvailable

One console for the whole fleet.

Every node in one place, however it is reached. A drone on the local network, one over the cloud relay, one relayed through a ground station, and a flight controller on a direct link all sit in the same fleet. Each carries an honest badge for how it connects, and inline controls that write over that same path.

Mission Control on GitHub Mission Control overview

Available

Usable today. Early access — some pieces run behind a feature flag and APIs may shift between releases.

Console, whole fleet

Reach types

Any

Bearer, one view

REACH TYPES

Every node, however it connects.

A node can be reached five ways. The console shows which one is live, so you always know how you are talking to a drone before you send it a command.

	Data path	Typical use
Local network	Direct over the LAN	Same network, lowest latency
Cloud relay	Through the cloud broker	Remote or across networks
Relayed over the radio	Through a paired ground node	A drone linked by radio, no IP of its own
Direct flight controller	Serial, USB, or a network link	A flight controller with no companion computer
Unreachable	No path right now	Last known state, awaiting reconnection

Local network

Data pathDirect over the LAN

Typical useSame network, lowest latency

Cloud relay

Data pathThrough the cloud broker

Typical useRemote or across networks

Relayed over the radio

Data pathThrough a paired ground node

Typical useA drone linked by radio, no IP of its own

Direct flight controller

Data pathSerial, USB, or a network link

Typical useA flight controller with no companion computer

Unreachable

Data pathNo path right now

Typical useLast known state, awaiting reconnection

MESH & REACH GRAPH

Not a flat list. A reach graph.

The console draws the fleet by how it connects. A ground station relaying to its linked drones reads as a branch, so a relayed drone sits under the node that carries it, not as one more equal dot in a row.

Fleet as a graph

Mission Control reaches a ground node, which in turn carries two relayed drones. A third drone is paired directly. Relay streams flow up the branch and the graph shows the real path, not a flattened star.

CONTROLS

Act on one node, a group, or the whole fleet.

The same actions work at any scale. Set a flight mode, request a return, change a setting, or move a node onto a different reach path, from a single node up to the entire fleet.

One node

Act on a single node

Open a node and set its flight mode, request a return, restart a service, or change how it is reached. The action writes over whichever path currently reaches that node.

A group

Act on a selection

Select several nodes and apply one action across all of them. Send a group home, change a shared setting, or move a set of nodes onto a different reach path in one step.

The whole fleet

Act fleet-wide

A header action reaches every node at once. Fleet-wide commands run against each node over whatever bearer currently connects it, so the reach differences stay out of your way.

Every control writes over whichever bearer currently reaches the node, so a command to a drone on the local network and a command to one over the cloud relay start from the same place in the console. Reach differences stay a detail the console handles, not a set of separate tools you have to learn.

Take it further.

OverviewShipping

Fleet dashboard, flight control, configurationLearn more →

CockpitShipping

Immersive game-like cockpit with Skills, hotkeys, and gamepadLearn more →

ExtensionsShipping

Custom panels and overlays in sandboxed iframesLearn more →

See the whole fleet, act on any of it.

Fleet management runs inside the open-source Mission Control. Read the code and run it yourself.

Mission Control on GitHub