Skip to content
ELEMENT 31

Czar Chassis

Czar Chassis is the Czar Grid shipped by a robot vendor or systems integrator under their own name, with their fleet, so their customer receives one system.

· 2 min read

IN SHORT

Czar Chassis is the Czar Grid shipped by a robot vendor or systems integrator under their own name, alongside their fleet, so that their customer receives one system from one supplier. It is not a second machine; the nodes, the serving system, and the posture choices are identical, and Element 31 provides sustainment and attestation beneath the vendor's name.

Czar Chassis is the Czar Grid shipped by a robot vendor or systems integrator under their own name, alongside their fleet, so that their customer receives one system. It is not a second machine; it is the same appliance on a different commercial route.

Why it matters

A robot vendor selling a fleet into a warehouse or plant knows the customer will ask where the perception and decision models run. Pointing to a distant cloud raises questions about latency and data leaving the building. Asking the customer to build their own pool slows the sale and splits responsibility.

Czar Chassis lets the vendor answer with their own name on the box. The fleet and the pool arrive together, configured for that fleet, and the customer has one supplier to call. The integrator who brings several vendors onto one floor can do the same.

For the operator, the result is the same Grid they would get by subscribing directly, with the same posture choices and the same record. The difference is who ships it and whose name is on it.

How it works at Element 31

Underneath, nothing changes. The nodes are Czar. The serving system is Substrate. The task layer is Agency Studio. Each node attests what it is running before it joins the Grid, and provenance for integration, sealing, and software load stays on record regardless of whose name is on the enclosure.

Element 31 provides sustainment and attestation beneath the vendor's name. Signed updates, integrity verification through Watchman, and the provenance record are Element 31's responsibility for the life of the subscription. The vendor owns the relationship and the fleet.

The vendor's customer can choose air-gapped or connected posture per site, just as a Facility Direct customer can. On a connected site, the Grid talks to the vendor's own fleet software because the site declared that route, not because the vendor is the shipper.

The commercial form is the same: one subscription for the configured Grid, hardware, platform license, and sustainment in one line, fixed for the term. How to buy sets out both routes, and the Czar Chassis page describes the vendor's side.

Questions this raises

How is Czar Chassis different from Facility Direct?
Facility Direct is the building subscribing to the Grid itself. Czar Chassis is a robot vendor or integrator shipping the same Grid under their own name with their fleet. The appliance and the subscription form are the same on both routes.
Who supports a Grid delivered as Czar Chassis?
The vendor owns the relationship with their customer. Element 31 provides sustainment and attestation underneath, including signed updates, integrity verification, and the provenance record for every node.
Can a Czar Chassis site be air-gapped?
Yes. Posture is a choice per site regardless of route. The vendor's customer can run the Grid with no path out, or connect it only to systems the site already secures, including the vendor's own fleet software if the site declares that route.

KEEP READING

Related.