Private AI compute,
engineered to specification.
GPU Smith specifies, procures, integrates and validates private AI infrastructure, from a single inference node to a multi-megawatt hall. Every engagement is delivered against written acceptance criteria and an as-built documentation set.
Fixed-scope assessment · reference design in weeks · credited against the build
| Parameter | Value | Note |
|---|---|---|
| Accelerators | 64 × NVIDIA Blackwell | per pod |
| Aggregate HBM | 12.2 TB HBM3e | ±0 |
| Fabric | 400G InfiniBand NDR | rail-optimized |
| IT load | ≈ 100 kW | liquid-ready |
| Precision | FP8 / FP4 | open weights |
| Serving stack | TensorRT-LLM · vLLM | K8s / Slurm |
Six disciplines. One statement of work.
Hardware integration & commissioning
HGX, DGX and NVL72 systems specified, procured, rack-integrated, cabled and burned in. InfiniBand and Spectrum-X fabrics validated port by port against a link budget.
Cluster architecture & sizing
Topology, node count and serving stack derived from workload models and throughput targets. TensorRT-LLM, vLLM and Triton configured to measured requirements.
Inference build-out
Turnkey delivery from empty rack to first validated token. Procurement at a disclosed margin, integration on site, handover on acceptance.
Serving optimization
Quantization, batching, KV-cache and scheduler tuning to reduce cost per token and raise sustained utilization on installed hardware.
Datacenter operations
Capacity planning, telemetry, failure-mode analysis and operating procedures for existing facilities and colocation.
Sovereign & air-gapped systems
Disconnected deployments engineered to a defined constraint set, with local model registry and offline update paths.
NOTE — Electrical, mechanical and thermal engineering are delivered through vetted partner firms under GPU Smith coordination and a single statement of work.
Owned compute is a capital decision, not a belief.
At sustained load, per-token cloud pricing exceeds the amortized cost of owned hardware. The crossover is a calculation, not an opinion. GPU Smith locates it for a defined workload and states the result in writing.
- Weights, prompts and telemetry remain within the client boundary
- Amortized capital cost falls below per-token pricing at sustained load
- No rate limits, deprecation schedules or policy dependencies in the serving path
- Air-gap capable for regulated and classified environments
Engineered for environments where data cannot leave the boundary.
Air-gap capable
Clusters engineered to operate fully disconnected: local model registry, offline update path, no external dependency in the serving loop.
Data residency
Weights, prompts and telemetry remain on client-owned hardware, in the jurisdiction specified.
Chain of custody
Documented custody from procurement through installation, with serialized inventory and acceptance records.
Export-control assessed
International deliveries planned with export-control requirements evaluated at assessment, not after purchase.
As-built documentation
Architecture records, port maps, operating procedures and acceptance reports issued as standard, written for audit as much as operation.
Structural independence
No reseller quota, no cloud of our own. The engineering recommendation is the only product.
A defined sequence. Verification at every stage.
Assessment
Fixed scope. Workload modelling, total cost of ownership against cloud and API baselines, reference architecture, and a documented recommendation. Credited against the build.
Specification & procurement
The controlled build sheet: part numbers, link budget, lead times and pricing. Procurement executed through our channel at a disclosed margin.
Integration & validation
Rack integration, fabric bring-up, burn-in and acceptance testing on site or in colocation, against the written criteria.
Optimization & handover
Serving stack tuned to the utilization target, operating procedures issued, and the as-built documentation package delivered.
Every build begins with a written assessment.
A fixed-scope engagement that resolves a single question: build or do not build, and to what specification. Deliverables are yours regardless of outcome. The fee is credited in full against the build if it proceeds.
Request the assessmentFixed scope, defined in one call · typically three weeks
- 01Workload characterization: models, context length, tokens per day
- 02Total cost of ownership: owned hardware, cloud GPU and API baselines
- 03Reference architecture with itemized bill of materials
- 04Power, space, cooling and network requirement schedule
- 05Procurement plan with lead times and quoted pricing
- 06Build / no-build recommendation, issued in writing
Three mandates. One requirement: control of the compute.
Bounded inference
Healthcare, finance, legal, defence and public bodies that cannot transmit data to a third-party API. Frontier-class open weights, operated within the client boundary.
Post-cloud economics
Teams whose API and rented-GPU expenditure has passed the ownership crossover. The point is located, then the system is built to it.
Technical due diligence
Independent review of AI datacenter and GPU-cloud investments: architecture assessment, vendor-quote verification, and a capital plan reconciled with physical reality.
The parts we specify, documented as datasheets.
Engineering references for every part that reaches our bills of materials: measured specifications, facility requirement schedules, procurement realities. Each sheet cites its sources and carries a verification date.
GPUs & accelerators
Datacenter GPU modules and PCIe accelerators: compute, memory, interconnect, power and procurement, stated per part.
Systems & racks
HGX and DGX platforms and rack-scale NVL systems: node-level specifications and the facility requirements they impose.
Networking & fabrics
InfiniBand and Spectrum-X Ethernet switches, adapters and DPUs: the fabric layer of a validated cluster.
Describe the workload. Receive a written engineering assessment.
Build or do not build, and to what specification. Stated in writing, with an itemized bill of materials and a costed comparison against cloud and API baselines.