Robotics · R-02

See every robot. Fix problems before your customer calls.

A fleet console for robot makers and the operators who run their robots: live status and maps, alerts that reach the right person, hooks for remote assist, uptime reports, and role-based views so each customer sees only their own robots.

  • Live statustask, battery, errors, network
  • Alertsrouted by site, robot and severity
  • Remote assisthooks for your operators
  • Customer viewsrole-based, their robots only

Talk to an engineer All robotics lines

What we build

One console for the people who run the fleet

Built on the telemetry your robots already send, in your cloud accounts. Each piece is quoted on its own.

Live status and maps

Every robot on the site map with its task, battery, error state and network link, updated as the robot reports. Filters by site, model and software version.

Alerts that reach a person

Rules per site, robot and severity, sent to the channel your team already watches. Every alert links to the robot's recent logs, so the first look starts with data.

Remote assist hooks

A way for an operator to see what the robot sees and send the commands its software already accepts, such as pause, resume or go to a point. Every command is logged with who sent it.

Uptime and incident reports

Uptime per robot, site and customer, incidents with their cause and fix, and a monthly report you can send to a customer as it is.

Role-based customer views

Your customers sign in and see their own robots, sites and reports, and nothing else. Your support team sees all of them.

Your data, your accounts

Telemetry from MQTT, ROS 2 topics or your own cloud into storage you control, with retention you set. The console runs in your accounts, not ours.

How it is built

From the telemetry you have to a console people use

  1. NDA first. Then a look at what the robots send today, where it lands and who needs to see it
  2. A written design note: the screens, the alerts, the data path and what stays on the robot
  3. A first console on one site in weeks, with weekly demos to the people who will use it
  4. More sites and customer views, then handover with a runbook, or we stay on

What stays on the robot

  • Safety-rated stops and motion control
  • Motor firmware and the robot's own limits
  • Any command the robot's software does not already accept

Questions about the fleet console

Does the console drive the robot?

Only through the commands your robot software already accepts, with every command logged. Safety-rated stops and motion control stay on the robot.

Do we have to replace the fleet tool we use?

No. If it has an API, the console reads from it and adds what is missing. If it does the job, we tell you so.

Where does the data live?

In your cloud accounts, in the region you choose. For robots sold in the US and Canada, that is usually a US or Canadian region.

Can our customers see the console?

Yes, through role-based views that show each customer only their own robots, sites and reports.

Tell us how many robots and where.

Send the fleet size, the sites and what the robots report today. We reply with what we would build first.

Contact us All robotics lines

Reply within one business day