When AI workloads have to run on infrastructure you own or control, public cloud pricing models break. We assess the site, the power, the cooling, the network fabric, the model footprint and the three year run-cost before you sign a hardware contract.
Five layers, one boundary, and a single controlled channel out of it. The assessment establishes what you already have at each layer and what has to be designed.
Training, fine tuning and inference behave nothing alike, and sizing for the wrong one is the most expensive mistake in this whole exercise. We profile the real demand curve rather than the peak somebody quoted.
Which rules actually bind you, what they require of data at rest, in transit and in the model, and where your current estate already crosses the line without anyone noticing.
Accelerator racks draw many times what a typical enterprise rack does. We walk the floor and establish whether the building can carry the design, or what has to change first, before anything is ordered.
A sized, vendor-neutral bill of materials with the network fabric that actually feeds it. Written so you can put it out to tender rather than back to the vendor who suggested it.
Hardware amortisation, power, cooling, network, licences, spares and the operations team, modelled year by year and compared honestly against staying on public cloud.
Cost per million tokens and energy per result, measured on a representative workload and stated against published standards so a third party can reproduce the figure.
The quote you were shown covers the first block below. The assessment covers all seven, then divides the total by the work the system does.
Three minutes inside a site assessment: rack density, cooling method, power headroom, and the constraints that decide the design before anything is ordered.
The design allows exactly one channel out of the sovereign boundary, and it carries telemetry only. This is the drawing that settles the argument with a regulator.
Every tier answers the same two questions: Will your AI and data architecture survive your regulator, and what does it actually cost to run.
Sometimes, and we have. If the workload is small, bursty or short-lived, public cloud usually wins on cost and we will show you the crossover point rather than talk around it.
A firm connected to us can execute builds, and that is disclosed on page one of every report. The assessor takes no part in the build and no part of their pay depends on the recommendation. The design is written so any competent integrator can deliver it.
Bring it. A large part of what we do is testing a vendor design against the workload and the building it has to live in. If it holds up we will say so, which is worth knowing before you sign a multi-year commitment.
Only if the channel carries telemetry and no customer data, and only if your regulator accepts that split. We establish which of those is true for you rather than assuming, and design the boundary accordingly.
Thirty minutes is usually enough to scope it, and we will be honest if public cloud is the better answer.