Skip to content

Security Overview

Security at a glance: how Rover Nexus protects robot connections, access, and your data.

How it fits together

Area What it means for you
Robot identity & enrollment Each robot enrolls once with a single-use token, then proves its identity automatically on every connection. See Enrollment.
Encrypted transport (mTLS) All robot-to-cloud traffic is mutually authenticated and encrypted. Neither side trusts an unverified peer.
Role-based access control People get exactly the access their role grants, at both the organization and fleet level. See Roles and Permissions.
Audit logging Sensitive actions (commands, dispatches, sharing changes) are recorded so you can review who did what. See Auditing.
Teleop session security Live video and remote control use short-lived signaling tokens. See Teleoperation.
Tenant separation Each organization's data is kept separate from every other organization's.

Key points

  • Single-use enrollment. A robot joins with a one-time token; its private key never leaves the device.
  • Mutual TLS everywhere. The robot and cloud verify each other before any data flows.
  • Least privilege by default. Two-level role-based access control, at the organization and fleet level. See Roles and Permissions.
  • Shared fleets stay bounded. Cross-organization sharing is capped by role and can expire. See Fleet Access.
  • Short-lived teleop tokens. Remote-control sessions use short-lived signaling tokens.

Learn more