Across the lifecycle · Business

Your fleet's numbers, straight from the robots

Insaion builds fleet KPIs from the same telemetry your engineers debug with. Incidents, MTTR and any metric your robots publish, by device, site or release. One set of numbers for everyone.

Built for: Engineering leads, operations managers and account teams

Get started free Book a demo

Where fleet reporting falls apart

“How reliable was the fleet last quarter?”

Three spreadsheets, three answers

Engineering, operations and sales each keep their own. They never agree.

“Which release actually made things better?”

Decisions based on anecdotes

No per-release or per-site metrics. The best argument wins.

“The customer wants to see uptime for their site.”

Customer reviews on gut feel

Quarterly reviews with no proof the robots did their job.

Measure what the business asks about

Any metric a robot publishes, grouped the way the business asks.

Custom KPI dashboards

Battery cycles, missions, distance, error counts. Any ROS 2 topic, host metric or OpenTelemetry metric.

Incidents and MTTR

Incidents and mean time to resolution for the last 30 days. Full history behind it.

Compare groups and releases

Devices, sites or versions side by side. Or an alarm when one group drifts.

Per-site views

Devices by customer site, on a map. Alarms scoped per site.

Starter plan and above

Device metadata

Model, firmware, compute and your own fields per robot. Slice the fleet the way the business does.

Read-only seats for stakeholders

Leadership, account managers or a customer's ops lead can look without changing anything.

Per-user roles on Growth

From telemetry to business review

1
Pick the KPIs
Availability, incidents, missions per day, battery health, performance per release.
2
Check the robot already publishes them
Most already are ROS 2 topics or host metrics. Anything else is a few lines of OpenTelemetry.
3
Build the dashboard once
Group by site, model or version. Reuse it for every review.
4
Share it with whoever needs it
Engineering, operations, account teams and customers.

What Insaion does not do yet

There are no public share links, embeddable dashboards or per-customer portals yet. External stakeholders need a Viewer seat, and a Viewer sees the whole workspace.
You can't export data to CSV or schedule PDF reports yet.
Fleet uptime and utilisation are built from metrics your robots publish. Insaion doesn't calculate a ready-made availability score.

Frequently asked questions

What KPIs should a robot fleet track?

Common robot fleet KPIs are availability, incidents per robot, mean time to resolution (MTTR), missions or tasks completed, battery health and performance per software release. Insaion tracks incidents and MTTR automatically and builds the rest from metrics the robots already publish.

Can I show fleet performance to my customers with Insaion?

Yes, by reviewing dashboards with them or giving them a read-only Viewer seat. Insaion doesn't offer public share links or per-customer portals yet, and a Viewer sees the whole workspace, so many teams walk customers through the dashboards in a review meeting.

How do I compare robot performance between software releases?

Store the software version as device metadata or group devices by release, then plot the same metric for each group on one dashboard. A group-comparison alarm can also tell you when one release does worse than another by a set percentage.

Does Insaion replace a BI tool?

No. Insaion is where robot operational metrics come from and where you explore them. Teams with a data warehouse keep using their BI tool for reporting across the whole business.