Skip to content

Can you build on an air-gapped site?

Yes. Air-gapped work is built air-gapped, on the air-gapped side of the site, on your Czar. Nothing about the practice depends on reaching out of the building.

· 3 min read

IN SHORT

Yes. Air-gapped work is built air-gapped. E31 Consulting engineers work on the air-gapped side of the site, on the customer's Czar, and the use case never connects to anything outside. Retrieval, adaptation, evaluation, and the run record all run on the appliance, declared routes reach only systems inside the gap, and the handoff leaves nothing to close because nothing was ever open.

Yes. Air-gapped work is built air-gapped. E31 Consulting engineers work on the air-gapped side of the site, on the customer's Czar, and the use case never has a connection to anything outside. Nothing about the practice depends on reaching out of the building, so an air gap takes nothing away from what can be built.

What changes on an air-gapped site

Less than customers expect. The engineers are forward-deployed in the ordinary sense: inside the segment, sitting with the desk, building on Substrate and Agency, publishing versions as they go. The corpus is assembled from the site's own documents, which are already inside. Retrieval, memory, adaptation on the site's material, evaluation, and the run record all run on the appliance.

What changes is logistics. Anything the engineers need to bring in comes in by whatever means the site already uses for its air-gapped systems, under the site's own controls. Anything the engineers produce stays in. There is no exception made for the practice.

What the engineers cannot do, and do not try to

They cannot reach a vendor's cloud for a model, a tool, or a reference, and they do not build anything that would want to. They cannot take the run record out for analysis elsewhere; they read it where it is. They cannot keep a copy of what they built, which on an air-gapped site is not a policy but a physical fact.

Certification includes being assessed on working inside sovereign sites, so an engineer does not arrive expecting the conveniences of a connected build and then ask for them. The forward-deployed form is described in forward-deployed.

Routes on an air-gapped site

Declared routes still exist, but they reach only systems inside the air-gapped segment. If the use case has to land a result in the plant's own system of record, that system is on the same side of the gap, and the route is declared to it. The run record shows every call, and IT can see that every call stayed inside.

Mixed estates

Many customers have one site or one hall air-gapped and others connected to systems they already secure. The practice builds for each segment in its own posture and does not ask the air-gapped side to become connected for the sake of consistency. A version built for the air-gapped hall is its own version with its own routes. A mixed estate stays a mixed estate.

Handoff on an air-gapped site

The handoff is the same: the published version, the notes, the site team making each change in scope with their own hands, IT reviewing the operating picture, engineer access withdrawn. The difference is that there is nothing to close down afterward, because nothing was ever open. What the site keeps is set out in what the customer keeps.

Questions this raises

Do the engineers need to bring anything in from outside?
Whatever is needed comes in by the means the site already uses for its air-gapped systems, under the site's own controls. The practice does not ask for an exception, and nothing the engineers produce goes back out.
Can the run record be analysed off site?
No. The record stays on the appliance and is read there. The engineers read it where it is during the work, and the site team reads it there afterward. That is a physical fact of the posture, not just a policy.
What if some of our sites are connected and some are not?
The practice builds for each segment in its own posture. The air-gapped hall gets its own version with routes that stay inside; the connected hall uses the systems the customer already secures. Neither is asked to change for the other.

KEEP READING