MISSION CONTROL · FLEET CONSOLE

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 flight controls that write over that same path when a command can reach it.
command.altnautica.com
Demo data
1
Console, whole fleet
4
Reach types
Any
Bearer, one view

REACH TYPES

Every node, however it connects.

A node can be reached four 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. When none of the four applies, the node shows as unreachable.

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 (state)

Data pathNone of the four paths is live
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 Controlground nodedrone (relayed)drone (relayed)drone (direct)
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.

Nodes, grouped by how they connect

The fleet view lists every node with its reach path, so a relayed drone sits under the ground node that carries it.

Fleet view listing nodes with their reach pathsFleet view listing nodes with their reach paths

One node, opened

Open any node for its live state and the controls that write over its current path.

A single node's overview with live state and controlsA single node's overview with live state and controls

CONTROLS

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

Flight actions work at any scale, from a single node up to the entire fleet. Settings and mesh-role changes stay per node.

Return the whole fleet

Return all, from the header, sends every node home at once. It runs against each node over whatever bearer currently connects it and skips nodes that cannot fly an autonomous return.

Demo data

Act on a single node

Open a node to set its flight mode, request a return, or restart a service. Flight commands go over whichever path reaches that node; a ground station's mesh role is set through its local agent.

Act on a selection

Select several nodes and apply one flight action across all of them. The bar says how many can take it before you confirm. Arming stays a per-node decision.

Every flight command writes over whichever bearer currently reaches the node, so a command to a drone on the local network and one over the cloud relay start from the same place in the console. Over the cloud the console shows a delivery receipt, not the vehicle's own acknowledgement.

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
Get Early Access