Skip to content

System Requirements

What you need to run the Fleet Manager web app and the robot agent.

Fleet Manager web app

The web app runs in your browser — nothing to install.

  • Browser: A current desktop browser (Chrome, Brave, Edge, Firefox, or Safari). Teleop and live video rely on WebRTC and the Gamepad API.
  • Network: Outbound HTTPS and a secure WebSocket connection for live telemetry. Teleoperation needs WebRTC traffic to reach the robot.
  • Input device: A standard gamepad/controller is required for teleoperation.

Robot agent (rover-agent)

The agent is a single binary installed on each robot.

Platform

  • OS: Debian-based Linux distributions. The agent has been tested with Ubuntu 22 and 24, and Pop!_OS 22 and 24. Full compatibility list coming soon.
  • Architecture: x86 and ARM.

Hardware

  • Cameras: V4L2-compatible camera(s) and shared memory video for video streaming and teleop (the agent supports dual-track, switchable video).
  • Resources: Detailed minimum resource requirements coming soon.

Network

  • Outbound connectivity to the Rover Nexus cloud over mutual TLS (mTLS). All robot-to-cloud traffic is encrypted and mutually authenticated.
  • Specific outbound hosts and ports to allow through firewalls are coming soon.

Dependencies

You don't build the agent or install dependencies yourself. The bootstrap command delivers the agent and everything it needs (including the video components used for teleop) and registers it as a service.

Local storage and configuration

  • The agent keeps local state in an embedded database on the robot.
  • Configuration lives under /etc/rdyn/. See Robot agent configuration.

ROS 2 robots

ROS 2 robots connect through an external bridge that translates ROS 2 topics to and from Rover Nexus. See Set up the ROS 2 bridge.