Skip to content
ELEMENT 31

CZAR GRID

Sealed Czar nodes in your rack, serving every robot on the floor, from any vendor. The product a facility buys.

A Czar Grid: a rack of sealed Czar nodes in the facility's equipment room, with the warehouse floor it serves visible through the glass.
CZAR GRIDONE POOL FOR THE FLOOR

HOW IT SERVES A FLOOR

Requests in. Answers back. Nothing leaves the building.

Every machine sends the moments it cannot handle to the pool and gets an answer back over the local network. Its own safety logic never moves.

THE BUILDING · LOCAL NETWORK ONLYMOBILE ROBOTVENDOR APICK ARMVENDOR BMOBILE ROBOTVENDOR AHUMANOIDVENDOR CVISION STATIONVENDOR DPLC / WMSSITE SYSTEMSCZAR GRIDTHE POOL · IN THE FACILITY RACKREQUESTANSWERSAFETY ON THE MACHINE

WHAT IT IS

The compute a fleet needs, in the building instead of on the robot.

Carrying a large model on every robot sizes each one for its worst moment. Sending it to a region answers after the moment has passed. Czar Grid puts the model in the building: the vendor keeps the robot, the site keeps the pool, the data, and the record.

WHAT A FACILITY GETS

One pool, with the rules a floor already has.

Every robot, any vendor

One pool for the floor, whoever made the robot that is asking.

Models a robot cannot carry

The unfamiliar object, the damaged label, the blocked route: answered over the local network, in time.

Safety stays on the robot

Reflexes, stops, and motion limits stay on the machine as the vendor certified them.

The site's data stays on site

Feeds, captures, and the record of every decision stay on hardware the facility holds.

Tasks a safety officer can sign

Bounds, approvals, versions, and a replayable run record, authored in Agency Studio on the Grid.

A bill that sits still

One subscription for the configured pool, fixed for the term. More robots do not move it.

HOW A GRID IS USED

From the first node to a floor that depends on it.

  1. 01

    Place the pool

    Czar nodes go into your rack, on your network. Air-gapped, or connected only to systems you already secure.

  2. 02

    Connect the fleet

    Each vendor's software is pointed at the pool. Its robots and safety logic stay as they are.

  3. 03

    Serve the floor

    Substrate answers every robot inside its latency budget and writes each decision to the record.

  4. 04

    Author the site's tasks

    Set the bounds, name who approves, publish a version. The run record is there the next morning.

  5. 05

    Add a node when the floor grows

    The next fleet joins the pool that is already there. When it is full, add a Czar.

WHAT MAKES IT A PRODUCT

The hardware is the pool. The software is why a site keeps it.

SUBSTRATE

Serves the pool

The serving system: shared models, per-robot latency budgets, signed updates, and the record.

AGENCY STUDIO

Holds the tasks

The task layer: bounds, named approvals, versions, and a replayable run.

CZAR

Is the node

The sealed appliance the pool is made of. One for a small floor, several for a Grid.