What a robot vendor gets from Czar Chassis

A robot vendor selling into a warehouse or a plant faces a problem its own hardware cannot solve. The models that make the fleet useful on a changing floor are too large to carry on the robot and too urgent to send to a distant cloud. The vendor can host a pool in its own cloud, which means carrying the customer's camera feeds and captures out of the building. Or it can tell the customer to buy compute separately, which means the customer receives two systems and two parties to call. Czar Chassis is a third option, and this article sets out what the vendor gets from it.

A pool for the fleet, inside the customer's building

Under Czar Chassis the vendor ships the Czar Grid under its own name, with its fleet, so the customer receives one system. The pool sits in the customer's rack and serves the vendor's robots over the facility network: the perception models for aisles that change, the decision models for items the on-board model has not seen, the language models that let a supervisor give instructions. Each robot keeps its own on-board model for reflexes and falls back to it when the pool cannot answer within its budget.

The vendor did not have to design this pool, build it, or decide how to keep it attested. It is the same Czar that a facility would subscribe to directly. What the vendor adds is its fleet and its name.

Nothing to host, nothing to carry out

A vendor that serves models from its own cloud becomes the custodian of its customer's feeds, captures, and task records. That is a liability many customers will not accept, especially in a plant or a terminal where the feeds are the site's most sensitive data. With a Chassis Grid, nothing leaves the building. Camera feeds, captures, adapted model weights, and the record of every decision stay on the customer's hardware inside the customer's network.

The vendor therefore sells a fleet whose intelligence stays on site, which is a simpler conversation with the customer's security team and a simpler position for the vendor. Adaptation happens on the pool, on the site's own captures, and the adapted weights stay there. The vendor's fleet gets better on that floor without the vendor ever holding the data that made it better.

Sustainment the vendor does not staff

The part of the arrangement that matters most to a vendor's margin is sustainment. Element 31 provides, underneath the vendor's name, the sealed and signed read-only image, the attestation each node performs before it joins a Grid or accepts a task, the provenance record of integration, sealing, and software load, and the signed updates for the term. Remote sessions are customer-initiated through the portal, and on sovereign sites an uplink window requires the customer's attestation before it is approved.

The vendor holds the customer relationship and takes the support call, because the vendor's name is on the system. But the vendor is not running a compute support desk, signing images, or maintaining an attestation chain. Those are Element 31's for the term, which is what makes it possible for a robot company to offer a facility pool without becoming an infrastructure company. The Czar Chassis page describes this arrangement from the vendor's side.

One line and one relationship

The commercial form is the single subscription for the configured Grid: hardware, platform license, and sustainment in one line, fixed for the term. Under Czar Chassis the vendor holds that line and wraps it with its fleet in whatever way it structures its own offer. More of the vendor's robots on the pool do not move the line, which gives the vendor room to grow a fleet on a floor without the compute cost growing with it.

The customer, meanwhile, sees one party. One agreement for the fleet and the pool that serves it, one number to call, one name on the rack. The vendor becomes the accountable party for the whole system, which is often what the customer wanted from the vendor in the first place.

What the vendor should tell its customer

A vendor shipping under Czar Chassis should be plain about three things. The pool is a Czar Grid, and the record it keeps is the customer's, read by the customer's named roles in Agency Studio. Safety stays on the robot, as the vendor set it, and the pool does not change that. And Element 31 is underneath, providing sustainment and attestation, so the customer can ask where its hardware came from and get an answer from a record. The What does not change for the robot vendor article covers the boundaries in more detail.