Skip to content

Overview

What Rover Nexus is and the problem it solves — for anyone evaluating the platform.

The problem: managing the job, not just the robot

Real worksites rarely run one robot from one vendor. They run mixed fleets — different makes, models, and capabilities — each with its own console. That makes a single job (cover this field, haul from A to B, patrol this site) hard to plan and supervise across machines.

Most systems manage individual robots. Rover Nexus manages the job. It orchestrates missions and multi-step operations across heterogeneous, multi-vendor fleets — without vendor lock-in.

What Rover Nexus does

  • Monitor your whole fleet live: location, heading, battery or fuel, status, and faults.
  • Plan work on a map: import or draw boundaries, then generate coverage paths.
  • Dispatch reusable mission templates to a specific robot or any capable robot, now or on a schedule.
  • Orchestrate multi-step operations (such as haul jobs, spraying fields or patrol routes) across several robots with live feedback.
  • Teleoperate a robot directly with live video and a gamepad when a human needs to take over.
  • Govern access with organizations, roles, and cross-org fleet sharing.

The two pieces

1. The Fleet Manager web app (cloud) The operator console in your browser. It includes Fleet monitoring, PathLab planning, Teleop, and account, organization, and permission management.

2. The robot agent (rover-agent) A small binary program installed on each robot. It handles onboarding via the bootstrap command, then telemetry, mission scheduling, video streaming, and messaging to the cloud. All robot-to-cloud traffic uses mutual TLS (mTLS).

How robots connect

Robots integrate over Zenoh (primary), ROS 2 (via a bridge), and a REST API (coming soon). Zenoh is the native surface — robot software exchanges messages with the agent over local Zenoh, the most direct path and what custom integrations use. ROS 2 robots connect through an external bridge that translates ROS 2 (DDS) to and from the Zenoh messaging, and a REST API is planned. See Capabilities and Limitations and the robot integration overview.

Who this is for

Operators, developers and integrators, robotics startups, and OEMs across construction, mining, agriculture, forestry, solar, and industrial sites. See Use Cases.

Next steps