Design robots like you
compose software.
The Builder is a visual canvas where a robot is a component graph: chassis, actuators, sensors, skills and datasets — each one a versioned, on-chain asset with its own authors. Drag, wire, compile.
Component graph
Robots are recipes, not monoliths. Reference any registry component by semver range — wren_scout.chassis@2.1.0, nav_skill@^4 — and the Builder resolves the graph.
Typed sockets
Mechanical, power and data interfaces are typed. A LiDAR that speaks lox.pointcloud/2 only mounts where it fits — incompatibilities surface at design time, not on the bench.
Fork anything
One click forks any public model into your namespace. The upstream royalty split rides along on the lineage, so original authors earn from your improvements.
Versioned everything
Every save is a content-hashed manifest. Roll back, diff two revisions, or pin a fleet to an exact build — the registry remembers all of it.
Compile to manifest
Compiling produces a signed build manifest — the same artifact the simulator validates and LoxOS units verify before flashing. One graph, one truth.
Publish in place
When it's ready, publish straight from the canvas: set a price in $LOX, define the royalty split, and the model is live on the marketplace in one block.
Start with the SDK.
Everything the canvas does is also an API. Publish your first model from TypeScript in about twenty lines.