GB300 NVL72 · HGX B300 · United States

Purpose-built AI clusters, from the ground up.

Alder Compute designs, builds and operates dedicated NVIDIA Blackwell Ultra clusters — liquid-cooled, rail-optimized, handed over burned-in.

One GB300 NVL72 rack

Source: NVIDIA

72

Blackwell Ultra GPUs

in one NVLink domain

20 TB

HBM3e

fast memory per rack

130 TB/s

NVLink bandwidth

all-to-all, per rack

1.1 EF

Dense FP4

per rack

01 — Ground to tokens

One team, from the substation to the scheduler.

We don't resell someone else's cloud. Alder selects the sites, designs the liquid cooling, racks and cables every cluster, and operates it — so there is one accountable owner for every layer.

01 — Firm power first

Site & power

Every deployment starts with megawatts we can stand behind: Tier III and Tier III+ U.S. facilities with utility power and backup generation.

  • Tier III / III+ facilities
  • Concurrently maintainable
  • N+1 or better backup
01Site & power02Facility & liquid cooling03Compute04Fabric05Storage06Platform

02 — Two platforms

Rack-scale or node-scale. Both Blackwell Ultra.

GB300 NVL72 when your model wants one enormous NVLink domain; HGX B300 when you want eight-GPU building blocks you can carve up. We run both, side by side, on the same fabric and storage.

Platform 01

Hover to open

GB300 NVL72

A rack that behaves like one GPU — for frontier training and long-context reasoning.

GPUs72 Blackwell Ultra
CPUs36 Grace (2,592 Arm cores)
GPU memory20 TB HBM3e
Scale-up130 TB/s NVLink · 72-GPU domain
Dense FP4~1.1 exaFLOPS
Networking72 × 800 Gb/s ConnectX-8
Power~132–142 kW per rack
CoolingDirect-to-chip liquid

Best forFrontier pre-training · reasoning & long-context inference · MoE at scale

Platform 02

Hover to open

HGX B300

Eight Blackwell Ultra GPUs per node — the flexible building block for training and serving.

GPUs8 Blackwell Ultra
CPUs2 × x86 (Xeon 6 / EPYC 9005)
GPU memory2.1 TB HBM3e
Scale-up14.4 TB/s NVLink · 8-GPU domain
Dense FP4108 petaFLOPS
Networking8 × 800 Gb/s ConnectX-8
Power~14 kW per node
CoolingLiquid (4U) or air (8–10U)

Best forFine-tuning & post-training · inference fleets · multimodal & physical-AI pipelines

03 — Fabric

Every GPU is one hop from its rail.

Three networks, each doing one job: NVLink inside the rack, a rail-optimized InfiniBand fat tree between racks, and a separate Ethernet fabric for storage.

Rail-optimized, non-blocking.

Every tray’s NIC n lands on rail n. Traffic between GPUs of the same rank stays one switch hop away; everything else crosses the spine — with no oversubscription anywhere. 16 leaves, 8 spines, 1,152 GPUs.

Isolate a rail

Follow a packet

SPINELEAFRACKSSCALABLE UNIT 1 · 576 GPUsSCALABLE UNIT 2 · 576 GPUsNVLINK SWITCHGPUsONE GB300 NVL72 RACK · 18 COMPUTE TRAYS × 4 GPUsSTORAGEETHERNETRACKS

04 — Liquid cooling

Warm water in. Hot water out.

Around 90% of a GB300 rack's heat leaves through cold plates. Drag the supply temperature to see how flow, return temperature and heat rejection trade off.

25 °C45 °C
Flow
89 L/min
Return
54.6 °C
ΔT across rack
19.6 K
Heat to liquid
122 kW

Warmer supply water needs more flow, but the return stays near 55 °C — hot enough to reject heat with dry coolers instead of chillers. That is where the efficiency comes from.

Flow per GB300 NVL72 rack (OEM guidance). Water, ~90% of heat to liquid. Chiller threshold illustrative.

06 — Scalable unit

576 GPUs, cabled and waiting.

Eight GB300 NVL72 racks, two network racks, in-row cooling and four rails of 800G InfiniBand overhead. Open the explorer to walk every rack, tray and cable.

07 — How we deliver

From signed order to first job.

One team owns the whole path — so the schedule we give you is the schedule we keep.

01

Reserve

Tell us the workload, scale and timeline. We propose a platform, fabric and storage design — and a delivery date we can stand behind.

02

Build

We secure power and space, receive and rack the hardware, run the coolant loops and cable every rail ourselves.

03

Burn-in & validate

Every node, link and cold plate is stress-tested. NCCL all-reduce and storage throughput are measured against targets before handover.

04

Operate

Bare metal, Kubernetes or Slurm on day one, with telemetry, health checks and engineers watching the fleet.