Five apps.Or one console.

Control robots from any maker in one place, and teach them together. A skill taught on one robot runs on every robot equipped for it.

Drag the divider to compare

Left: five separate maker apps, each with its own controls, errors and data formats. Right: one DextorOS console listing every robot with its connection and current skill.

Works with robots from every maker

Maker names and logos are shown for compatibility reference only and imply no partnership or endorsement.

A fleet from five makers runs on five apps, five control languages and five datasets.

Whatever one robot learns stays inside its maker’s software. DextorOS gives the whole fleet one control surface and one shared brain.

How a skill spreads

You show one robot how it is done

An operator guides ARM-02 through a pick. DextorOS keeps the motion as a skill, not a script.

It goes out to every robot that can use it

The skill travels to each robot with the right hardware. Nobody rewrites it for another maker.

Wheels, legs and joints each work it out

Every body maps the same skill onto its own motors and sensors.

Then the rest of the floor picks it up

One lesson reaches every capable robot on the floor.

  1. Teach

  2. Share

  3. Adapt

  4. Scale

Which robots can actually run it?

Before a skill goes out, DextorOS checks each robot for the hardware it needs. Hold to teach and watch the fleet update.

Skill

Needs arm, gripper and depth camera

Skill version v4

Robots that can run Pick and place
RobotArmGripDepthLidarWheelLegs
ARM-02Has armHas gripperHas depth cameraNo LiDARNo wheeled baseNo legs
AMR-11No armNo gripperHas depth cameraHas LiDARHas wheeled baseNo legs
QDR-04No armNo gripperHas depth cameraHas LiDARNo wheeled baseHas legs
MM-01Has armHas gripperHas depth cameraHas LiDARHas wheeled baseNo legs
HUM-03Has armHas gripperHas depth cameraNo LiDARNo wheeled baseHas legs
DLT-07Has armHas gripperNo depth cameraNo LiDARNo wheeled baseNo legs
Press and hold to record a demonstration on the teacher robot, then share it with every capable robot.

Checking the fleet

One console for arms, rovers and quadrupeds

Live telemetry, commands and the full event history for each machine, whatever the maker. Type help to see what a robot accepts.

Fleet

AMR-11

Warehouse AMR

Streaming telemetry

Battery
64%
Speed
1.1 m/s
Location
Bay B5
Latency
42 ms

Link latency, last 48 s

  1. 09:36:02eventPicked up tote at bay A4
  2. 09:41:15cmd> move_to B3
  3. 09:41:15ackMoving to bay B3. Accepted in 38 ms

Every practice run makes the skill better

Compatible robots add their episodes to one shared dataset. When a training run finishes, the new version goes back to all of them.

Shared dataset
1,186 ep
Session success rate
0.0%
Skill version
v4

Simulated session

Pick and place

Ready

  • ARM-02

    6-axis arm

    0 ep
  • ARM-09

    7-axis arm

    0 ep
  • MM-01

    Mobile manipulator

    0 ep
  • HUM-03

    Humanoid

    0 ep
  1. Pick and place v4 is live on 4 robots

Connecting a robot takes one command

Each robot gets its own connector with its endpoint and pairing key filled in. It talks to DextorOS over ROS 2, MQTT, WebSocket or a serial link.

Generate

Files and endpoints use amr-11

Transport

dextoros-connector.yaml

# DextorOS connector for amr-11robot: amr-11platform: warehouse-amrtransport: websocketendpoint: wss://fleet.example.com/robots/amr-11pairing_key: dxk_test_dktJhHjpQ77edj3hacVrHu5preport:  - capabilities  - telemetry  - events

Install

Run this once on the robot’s onboard computer.

curl -fsSL https://fleet.example.com/install/amr-11.sh | sh

Pair

Waiting for first connection

Warehouse AMR reports these on first connection

  • Wheeled base
  • LiDAR
  • Depth camera

Playground values. Your workspace fills in its own endpoint and key.

Rules that apply to every robot, not one brand

Set a rule once and it acts on any robot that reports the signal.

Automations

Drag a trigger and an action into the rule, or tap one. Rules act on every robot that reports the signal, whatever the maker.

when
Battery below threshold
then
Send to dock
Or

Rule: When battery below threshold, send to dock.

20%
  • AMR-1164%Keeps working
  • QDR-0424%Keeps working
  • MM-0138%Keeps working
  • AMR-1417%Docks now

1 of 4 robots would dock

Who runs mixed fleets on it

Warehouse and logistics
AMRs from different vendors follow the same dock-and-charge rule.
Research labs
Every arm in the lab adds episodes to the same dataset.
Integrators
Hand each client one console, whatever hardware they bought.
Individual builders
Your arm and your rover finally share one app.

Also included: a fleet dashboard, full history for every robot, a searchable activity log, team roles, a demo fleet you can remove in one click, and an app you can install on your phone.

Put your first robot on DextorOS

Start with the demo fleet. Connect a real machine when you are ready.