Robotics

Every episode your robots run, on one timeline

Joint torque, gripper cameras, depth and transforms from the whole fleet — captured losslessly, searchable in seconds, and ready to train on.

Unit 12 / 24 · Bench · episode 4,182Recording
02:47elapsed
5 streamson one clock
3.18Mmessages
6.2 GBon disk
/arm/tracking_error_mm
0.42 mm
/cam/wrist
30 fps
/lidar/points
16k pts
/gripper/force_n
18 N
/cell/place_error_mm
1.1 mm
edge spool · full ratecloud · in sync
hours → minutesEpisode triage
NightlyFleet → training sets
LosslessEvery modality kept
01 / Capabilities

Proprioception and vision, finally in one place

Phloem keeps every modality of an episode on one playhead, so debugging a grasp takes minutes, not an afternoon of file juggling.

01

Scrub the whole episode

Torque, current, wrist camera and depth snap to the same instant. See exactly what the policy saw when the grasp slipped.

02

Find the failure fleet-wide

Query every episode for the same slip signature. One anomaly becomes a labelled set of every occurrence.

03

Curate training data from real runs

Tag episodes, filter by outcome, and export LeRobot-format datasets straight from the timeline.

The scene, not just signals

Depth, detections and masks sit over the camera frame, with the point cloud beside them — an episode reads as a scene, not a folder of files.

02 / Lifecycle

One platform, first prototype to fleet

The record built in development carries into validation and operations — nothing starts from scratch.

DevelopBench & prototype

Connect the first article, name channels once, and start recording at full rate from day one.

ValidateTest & qualify

Run sequences, check redlines as data lands, and hand the review board a traceable report.

OperateField & fleet

Every unit records to a local spool, connected or not, and syncs into one shared record.

LearnQuery & train

Search every run for one signature. Turn one incident into a coverage set or a training set.

03 / Ecosystem

Your stack, one continuous workflow

First-class ingest for the formats, protocols and buses this work already runs on — and the wider ecosystem behind them.

+ anything else with an SDK, a topic, or a recorded log.

04 / Outcomes

What teams get back

hours → minutesEpisode triage

Overnight fleet episodes arrive pre-correlated, so morning review starts at the anomalies instead of at the file system.

NightlyFleet data → training sets

Curated episodes flow from the fleet into training-ready datasets on a schedule, not as a quarterly project.

Get started

Robots that learn from every episode

Bring the whole fleet's data into one place, and turn every grasp — landed or missed — into the next policy.