CZAR
The sealed Element 31 appliance. One serves a team or a small floor on its own; several, joined, are a Czar Grid.
- WHAT IT IS
- The sealed appliance a Czar Grid is made of
- ALONE
- One appliance for one team, or a pool for a small floor
- JOINED
- One node of a Czar Grid
- POSTURE
- Air-gapped, or connected only to what the site secures
- UPDATES
- Signed; by media or by the site's own network
- BOUGHT
- On its own subscription, or as part of a Grid
WHAT A NODE DOES
One team's AI. A pool for a small floor. A building block for a large one.
Most Czars start with a team: documents, code, models, and the everyday tasks around them. The same node serves a floor of robots when there is one.
Answer from the team's documents
Contracts, drawings, manuals, and records the team holds, questioned in place, with the passage the answer came from.
Help write and review code
Coding assistants on open-weight models, with the repository and the history staying on the node.
Run the models the team chooses
Language, code, vision, and perception models the team or site hosts. Nothing goes to a vendor's cloud.
Keep the team's material on the node
Documents, code, captures, and records stay on the appliance. Models adapt on them, in place.
Run the team's tasks as agents
Agency Studio runs on the node: agents for the desk and the floor, with bounds, approvals, versions, and a replayable record.
Serve the robots on a floor
One Czar is a pool for a small floor, serving the models its robots cannot carry.
CZAR FOR A TEAM
One Czar, one team, one subscription.
Czar is sold on its own. A single team subscribes to a single appliance in its own rack and gets the whole platform on it, without waiting for a building-wide Grid. The same node joins a Grid later if the floor grows.
- WHO
- A single team: an engineering group, a lab, a department, or a small site with its own models, documents, and tasks.
- WHAT YOU GET
- One sealed Czar in your rack running Substrate and Agency Studio: the models you choose, your material kept on the node, and a replayable record.
- HOW IT IS BOUGHT
- The same subscription as a Grid, for one configured appliance: hardware, platform license, and sustainment in one line, fixed for the term.
- LATER
- Join it to other Czars as a Grid when the floor grows. Nothing is replaced.
ANY DEPLOYMENT
Sovereign, connected, or both.
The posture is a choice you make for a site, not a different appliance.
SOVEREIGN
Air-gapped
No path out. Updates arrive signed, on media you carry in, when you decide.
CONNECTED
Only the systems the site secures
Fleet software, the warehouse system, the PLCs: only what the site declared. A connection is a decision, not a default.
MIXED
Any estate
Some sites sealed, some attached. Same node, same way of running it.
PROPERTIES OF THE NODE
Sovereign is something the machine is, not a market it is sold to.
SEALED
The enclosure and the software image are both sealed. Interference leaves a mark that can be found.
ATTESTED
Each node proves what it is running before it joins a Grid or accepts a task.
PROVENANCE ON RECORD
Integration, sealing, and software load are recorded for every node. A record, not a reassurance.
FROM A NODE TO A GRID
Czar Grid, Czar Keep, or Czar Chassis.
Czar Grid is several Czars joined into one pool. Czar Keep is that Grid in one chassis, for a data center. Czar Chassis is the Grid shipped by a vendor under its own name. All of them are this appliance.
- Substrate is what the node runs: the serving system, signed updates, and the record.
- Agency Studio is how a site authors, bounds, approves, and records the tasks its robots run.
- E31 Consulting puts the engineers who install the pool on your site.