What the robot control and monitoring webserver actually gives an integrator, and what it doesn't

"Robot fleet monitoring" is a common search, and the honest answer for this specific offering is that it isn't one: it's a single-robot interface, and worth understanding as exactly that before assuming otherwise.

The interface is served from the robot's own onboard computer, not a central server watching a fleet.

There is nothing to install on a customer's own machines, and nobody needs ROS 2 knowledge to operate it, but the data lives on that one robot, not in a dashboard aggregating several. A site running multiple platforms gets one browser tab per robot, not one screen for all of them.

What one screen actually shows is real diagnostic depth, not a summary.

The robot's own URDF model, drawn with every joint, sits beside live camera and LiDAR streams, with the raw ROS 2 topic data underneath for anyone who needs it. That is closer to an engineer's diagnostic tool than a manager's status board, and it is worth knowing which of the two a specific integration actually needs.

Control goes beyond viewing, on the platforms built to support it.

Waypoints can be set against the robot's existing SLAM map with actions attached, arm-equipped platforms get tool-centre-point control through the inverse kinematics solver, and every onboard service, camera, navigation, audio, the web server itself, can be started and stopped from the same interface. Teleoperation is supported and switched off by default until specifically enabled.

What is on this screen depends on what has actually been built for that robot, not on a general feature list.

Outdoor SLAM navigation, arm teleoperation and speech interaction appear here only where they have been built and deployed for that specific machine; this is a front end onto systems that already exist, not a universal capability every platform gets by default. Ongoing support, customisation and further development are billed by the hour, the same as the rest of the site's engineering work.

Ask specifically whether a fleet-wide dashboard is what the project needs, because this product answers a narrower and, for most integrations, more useful question: what does this one robot's own onboard computer already know, right now.