How is a Czar Grid priced?

One subscription for the configured Grid. That line covers the hardware in the rack, the platform license for Substrate and Agency Studio, and sustainment for the term, and it is fixed for the term. There is no public price and no published term length, because the line is built from the Grid configured for a particular building rather than from a list. There is no purchase, no lease, and no installment plan. The subscription is the only commercial form.

What the one line covers

The hardware is the Czars installed in the building's own rack, however many the configuration calls for. The platform license is Substrate, the serving system, and Agency Studio, the task layer. Sustainment is the ongoing work that keeps the pool current and attested: signed updates, support through the customer portal, and the remote sessions the customer chooses to initiate.

Those three are not priced separately and then summed on an invoice. They are one line because they are one thing: a pool that serves the building's robots and keeps doing so for the term. An operator does not discover later that the license was extra or that sustainment was a second contract.

What does and does not move it

More robots on the pool do not move the line. A warehouse that adds a second vendor's mobile robots, or a plant that adds more humanoids to the same floor, is drawing from a pool it already subscribes to. There is no per-robot charge. That is deliberate: the operator should be able to grow the fleet without asking what each new machine costs the pool.

What does move the line is the configured Grid itself. If the floor grows to the point where one Czar becomes several, or a second building joins the estate, the configuration has changed and a new proposal is built for it. The subscription follows the pool, not the robots.

Posture does not move it either. An air-gapped Grid and a connected Grid are the same configured appliance with a different decision recorded, so the line is the same.

How a proposal is built

A proposal starts with the building. How many robots, from which vendors, on what kind of floor; what latency budgets those robots need; whether the site will run air-gapped, connected only to declared systems, or both. From that, Element 31 configures the Grid, and the subscription line is built from that configuration.

There are two routes to the same line. Under Facility Direct, the building subscribes. Under Czar Chassis, a robot vendor or systems integrator ships the same Grid under its own name with its own fleet, and the customer receives one system from the vendor with Element 31's sustainment and attestation underneath. Either way, the thing being subscribed to is the configured Grid.

Design-partner intake is not yet open. The How to buy page describes both routes, and the pricing page describes the subscription in the same terms. Can one Czar serve a small floor covers what the smallest configuration looks like.