Skip to content

System Overview

Rover Nexus has two halves: a cloud Fleet Manager and an agent that runs on each robot. Together they let you plan work in the cloud, send it to robots, and watch the results come back in real time.

Components

  • Fleet Manager (cloud) — the web application and supporting services where you manage organizations, fleets, and robots; build and schedule missions; and view live and historical telemetry. This is where operators do their work.
  • Robot agent — software running on each robot. It connects to the cloud, receives commands and missions, runs them on the robot, and reports telemetry back. The agent works with both native robots and ROS 2 robots (through an external bridge).
  • Real-time channel — a live streaming path the web application uses to receive telemetry and status as robots operate, separate from the request and response REST APIs.

How a job flows

A typical mission moves through the system like this:

  Operator
     │  plan / schedule / dispatch
     ▼
  Fleet Manager (cloud)
     │  command sent to robot
     ▼
  Robot agent
     │  runs mission on the robot
     ▼
  Robot agent
     │  telemetry + run status
     ▼
  Fleet Manager (cloud)  ──► real-time channel ──► Operator's view
  1. An operator plans a mission in the Fleet Manager and dispatches or schedules it to one or more robots.
  2. The cloud sends the mission to the targeted robots.
  3. Each robot's agent receives the mission and runs it on the robot.
  4. As the robot works, its agent reports telemetry (position, heading, battery, mode, health) and run status.
  5. The cloud receives those updates and pushes them to the operator's view over the real-time channel, so progress appears live.

Connectivity

Robots connect outbound to the cloud over a secure channel, and the web application receives live updates and video through dedicated channels. For details on how those connections work at a high level, see Connectivity.