HOW TO BUY
The Grid underneath never changes. What changes is who signs the subscription, who installs it, and whose name the facility sees.
HOW TO READ THIS
One pool. Two routes.
Both routes deliver the same Grid. They differ in who buys it and whose name is on it, and either one takes the next vendor’s robots when the site adds them.
A single team can also subscribe to one Czar on its own: the same appliance and the same subscription, for a team’s documents, code, models, and tasks, joining a Grid later if the floor grows. For technology and AI teams, that Czar is Czar Forge. An organization with a server room and a hundred or more people to serve takes the Grid in one chassis, Czar Keep, on the same subscription.
Facility Direct.
The building buys the pool.
BEST FOR
Operators of warehouses, plants, and terminals running robots from more than one vendor.
The building subscribes to one Grid in its own rack, and every vendor's fleet connects to it. Element 31 engineers install the pool with the operator's integrator and leave the site's tasks published in Agency Studio. The operator owns the record; the vendors keep their robots.
WHAT IT INCLUDES
- A Czar Grid sized to the building, in the operator's rack
- Substrate serving every vendor's software, with safety left on the robot
- Agency Studio for the site's tasks: versions, bounds, approvals, record
- Signed updates and attestation, including by media
- Element 31 engineers on the installation
ONE POOL, EVERY VENDOR
New robots connect to the pool that is already there.
THE SITE'S DATA STAYS
Feeds, captures, and the record stay on the operator's hardware.
A BILL THAT SITS STILL
One subscription for the configured Grid, fixed for the term.
Czar Chassis.
Your fleet ships with its pool.
BEST FOR
Humanoid, mobile-robot, and arm vendors, and the integrators who install them.
Czar Chassis is the Grid carried under the vendor's name: the same nodes, serving system, and task layer, delivered as part of the vendor's deployment. To the facility it is the vendor's system. Underneath, a pool that will also serve the next vendor's robots. Element 31 sustains it; the vendor keeps the customer.
WHAT IT INCLUDES
- The Czar Grid delivered with the vendor's deployment, under their name
- Substrate serving the vendor's fleet first, and any fleet the site adds
- Agency Studio for the vendor's site tasks, with the site's approvers
- Signed updates carrying the vendor's releases
- Element 31 sustainment and attestation underneath
NO SERVER COMPANY TO BUILD
Ship the compute a fleet needs without hardware, a serving team, or a signing chain.
YOUR NAME FORWARD
The customer sees your fleet and your system.
A SITE THAT STAYS YOURS
Your fleet is already on the pool when the next one arrives.
SIDE BY SIDE
The same question, two answers.
Read down the column that matches who you are.
| ROUTE 01Facility Direct | ROUTE 02Czar Chassis | |
|---|---|---|
| WHO SUBSCRIBES | The facility operator | The robot vendor or integrator, for their customer's site |
| WHOSE NAME IS ON IT | Element 31, in the operator's rack | The vendor's, with Element 31 underneath |
| WHO INSTALLS | Element 31 engineers with the operator's integrator | The vendor's deployment team, trained and supported by Element 31 |
| WHICH ROBOTS IT SERVES | Every vendor's fleet on the floor | The vendor's fleet first, and any fleet the site adds |
| TYPICAL BUYER | Warehouse, plant, and terminal operators with mixed fleets | Humanoid, mobile-robot, and arm vendors; robotics integrators |