CZAR KEEP
Four or eight sovereign AI engines in one sealed chassis, running the E31 Substrate, joining a Czar Grid pool or standing alone. For the platform teams that already own the rack.
- WHAT IT IS
- A Grid in one chassis, for a room that already has racks
- ENGINES
- Four or eight, sealed in one chassis
- RUNS
- The E31 Substrate, the organization's agents and applications
- SERVES
- A hundred-plus people, or a floor, from one machine
- JOINS
- A Czar Grid pool, or stands alone
- BOUGHT
- One subscription for one configured appliance
IN THE FAMILY
A Grid in one chassis. Not a bigger Czar.
A Czar for a team, a Grid for a facility, a Keep for the data center, a Forge for the builders, a Chassis for the vendors. Czar Keep is the engines a Grid is made of, in one sealed enclosure for a room that already has racks. It trades the deskside form for density; everything else carries over.
WHAT AN ORGANIZATION GETS
The whole platform, for everyone in the building, on one chassis it holds.
The same seven Substrate services as any Czar, with the room to serve an organization rather than a team. None of it leaves the walls to happen.
Serving for every internal application
The organization's tools and products call models on the Keep over its own network, with no vendor in the path.
Retrieval over the organization's own records
Documents, tickets, policies, and systems indexed on the chassis and questioned in place, with the passage the answer came from.
The organization's agents in Agency Studio
Authored, bounded, approved, versioned, and replayable, for every department the Keep serves.
Memory and the record
What each agent knows and every run it made, written on the Keep and readable by the people the organization names.
Adaptation and evaluation on its own data
Open-weight models tuned on the organization's material and scored against its own test sets before anything is promoted.
A pool for the floor, when it joins a Grid
A Keep joins the Czars already on a floor as one pool, or stands alone for the people in the building.
WHO IT IS FOR
Built for the teams that already own the rack.
Czar Keep is for platform and infrastructure teams with a server room and a hundred or more people to serve from it: a global capability center, a bank’s internal AI group, a laboratory, a government or defense organization. The machine stays inside the walls; the people it serves do not have to.
- WHO
- Platform and infrastructure teams that already own a rack and a server room: global capability centers, banks' internal AI groups, laboratories, government and defense.
- THE JOB
- Serve a hundred-plus people from one machine that never leaves the organization's walls, and join the floor's pool when there is one.
- INSTEAD
- One team on its own runs on Czar; a technology team on Czar Forge; a floor without a server room on a Grid of Czars in its own rack.
- LATER
- Four engines become eight, a second Keep joins the first, or the Keep joins the Czars on the floor. Nothing is rewritten.
THE BOUNDARY
A named person approves. Safety stays on the robot.
A Keep can serve the people in a building and the machines on its floor. Each has its own line, and the Keep holds both.
FOR THE PEOPLE IT SERVES
A named person approves
Agents on a Czar prepare and propose; a named person approves. Nothing client-facing, customer-facing or production-changing leaves the appliance without that approval, and every step of it is on a record the team holds.
FOR THE FLOOR IT SERVES
Safety stays on the robot
Safety, stops and motion stay on the machine as its vendor built them. Czar Grid serves perception, decisions and adaptation over the site's network; it is not a controller and does not sit inside any real-time or safety loop.
INSIDE THE WALLS
The records, the models, and the record stay where the organization is.
SOVEREIGN
No route out
The Keep runs with no connection at all. Updates arrive as signed bundles the organization carries in.
DECLARED
Only the systems the organization names
Identity, the record systems, ticketing, logs, the data stores: declared one by one at commissioning. Local Bridge denies the rest.
KEPT
The material stays
Records, datasets, adapters, evaluations, and the record of every run stay on the chassis the organization holds.
READING
Czar Keep in the library.
THE SAME APPLIANCE
Czar, Czar Grid, Czar Forge, Czar Chassis.
Czar Keep is the Grid in one chassis. Czar is the node. Czar Grid is several Czars joined into one pool for a facility. Czar Forge is Czar for the teams that build. Czar Chassis is the Grid shipped by a vendor under its own name. All of them are this appliance.
- Substrate is what the Keep runs: Inference, Retrieval, Memory, Adaptation, Evaluation, Watchman, and Local Bridge.
- Agency Studio is where the organization authors, bounds, approves, and records its agents.
- E31 Consulting commissions the Keep with your platform team and builds the first agents on it.