GB200 NVL72 Sourcing: 72 Blackwell GPUs in One NVLink Domain

GB200 NVL72 sourcing via GPUSeeker gives mid-market leaders a concierge-level guide to NVIDIA’s liquid-cooled Grace Blackwell rack for AI at scale. We work with teams in Healthcare, Finance, Manufacturing, and Media to see where 36 Grace CPUs and 72 Blackwell GPUs fit their roadmap. We help these organizations find right-sized AI infrastructure ASAP. This page is about the rack, not the building-block superchip alone.

Who this GPU is for

  • Programs targeting trillion-parameter-class training or real-time inference that need a 72-GPU NVLink domain
  • Teams training large models or serving at rack scale, with facility readiness for liquid cooling, high rack power, and Arm-based ops
  • Buyers comparing rack-scale NVL72 against node-scale DGX B200 or HGX B200
  • Leaders who must brief stakeholders on why “a GB200” is not one purchasable card

When to prefer an adjacent option

  • Choose the GB200 Superchip page when you need the 1+2 building block definition first
  • Choose DGX B200 or B200 when an eight-GPU x86 node is enough
  • Stay on H100 / H200 when Hopper meets the workload and rack-scale Blackwell is not required

Key specifications

Spec Value
Manufacturer NVIDIA
Configuration 36 Grace CPUs + 72 Blackwell GPUs (liquid-cooled rack), per NVIDIA Blackwell architecture overview
GPU memory (VRAM) Up to 13.4 TB HBM3E (rack aggregate), per NVIDIA GB200 NVL72 specifications
GPU memory bandwidth Up to 576 TB/s (rack aggregate), per NVIDIA GB200 NVL72 bandwidth specs
NVLink domain bandwidth 130 TB/s, per NVIDIA’s GB200 NVL72 technical overview
CPU 2,592 Arm Neoverse V2 cores (36 Grace CPUs with 72 cores each)
CPU memory Up to 17 TB LPDDR5X · up to 14 TB/s
Building block GB200 Grace Blackwell Superchip (1 Grace + 2 Blackwell)
Form factor / system context Rack-scale liquid-cooled NVL72 — not a discrete GPU card
Typical cluster role Exascale-class AI factory rack; model-parallel training and high-throughput inference

Specs from NVIDIA GB200 NVL72 product page. See Sources below. Partner racks (OEM SuperCluster / GIGAPOD-class) may vary on CDU, networking, and BOM. Verify before procurement.

Sourcing & availability

NVL72 capacity is allocation-heavy and facility-constrained. Mid-market teams rarely “spot rent” a full rack the way they rent an eight-GPU H100 node. Expect conversations about liquid cooling, rack power, networking (InfiniBand or Ethernet fabrics), and multi-quarter planning — without invented lead times from us.

Useful commercial paths:

  • Neocloud sourcing when specialist providers expose NVL72 or partial Grace Blackwell capacity
  • Reserved capacity for planned production windows
  • On-demand only if a verified short-term slice exists — do not assume hourly rack depth
  • GPU advisory to decide rack-scale vs node-scale before RFQ

Share workload, facility constraints, and term preferences. We help to qualify your AI solution’s requirements based on your industry-specific compliance needs and project timelines. We’ll route a warm request to the right Technology Services Distributor (TSD) path for a right-sized proposal.

Recommended workloads & industry fit

Recommended workload: High-Throughput Inference

NVIDIA positions NVL72 strongly for real-time trillion-parameter LLM inference and large MoE workloads, alongside massive-scale training. Mid-market fit concentrates on teams that truly need the 72-GPU NVLink domain — not every fine-tuning job. Industry fit spans Healthcare, Finance, Manufacturing, and Media when the deployment clears diligence.

Regulated-industry readiness comes from the TSD and its providers. The compliance needs you share in a short conversation with an advisor shape which providers the TSD proposes. The TSD then proposes providers that conform.

Executive guidance

GB200 NVL72 decisions fail when AI product teams treat a rack as a card purchase. We all know NVL72 is rack-scale Grace Blackwell in a liquid-cooled NVLink domain. Your job is to decide whether you need the full domain—or a node first.

When GB200 NVL72 rack-scale is the right move

NVL72 is the right move when model parallelism, large inference latency, or rack-scale training topology is real. Keep node-scale Blackwell when facility water, rack power, or Arm ops are not ready. Write GPU and CPU counts, cooling, and fabric in plain numbers.

Dual-track planning for this year and next

Run a dual-track brief. Track one: can node-scale B200 or DGX B200 meet this year’s SLAs? Track two: which workloads truly require the full NVL72 domain? If track one is healthy, treat NVL72 as a controlled program—not an emergency rewrite of facilities.

Map these three facts before you RFQ

Write three facts before any RFQ leaves the building.

  • Rack vs discrete need for the largest training or inference job
  • Fabric / NVLink domain scope you actually operate or consume
  • Facility / power calendar hardness for go-live dates

Soft calendars favor node pilots. Hard rack go-lives need dated cooling and power commitments plus a node-scale fallback.

Adjacent options without a FOMO upgrade

Compare adjacent options with the same brief. B200 covers discrete Blackwell without a rack program. GB200 Superchip is the Grace+dual-GPU building block, not the full domain. DGX B200 is the turnkey eight-GPU node path. Upgrade when the bottleneck is real.

Term shape, utilization, and kill criteria

To right-size a multi-year GPU contract, spot term traps: commitments sized beyond training and production needs, opaque partial allocations labeled as NVL72, and quotes omitting networking, storage, or egress.

  • Pressure-test utilization. A half-idle rack is not a savings story.
  • Prefer reserved floors with documented expansion over on-demand full racks.
  • Set kill criteria: a throughput or latency threshold, and a date that forces a stay on node-scale Blackwell if power or cooling slips.

Leave deeper provider checklists to the FAQ. List configuration, topology, and compliance needs in your requirements for the TSD.

One brokerage note: a loud keynote is not a facilities plan.

When you are ready, talk to a GPU sourcing advisor. Share model targets and facility constraints, and we’ll route a warm request to the right TSD path for a right-sized proposal.

How GPUSeeker helps

  • Clear rack vs Superchip vs discrete Blackwell framing
  • Vendor-neutral NVIDIA + AMD breadth via the GPU architectures archive
  • Neocloud, reserved, and advisory paths without invented capacity
  • Facility and topology questions captured in your requirements so the TSD can size the proposal
  • Help right-sizing your GPU commitment before you sign, so term shape fits your training and production plan

Frequently asked questions

How do we right-size a GB200 NVL72 commitment before we sign?

Treat NVL72 as a planned rack program. Write down GPU and CPU counts, cooling, rack power, and dated windows. Planning early keeps your AI roadmap on schedule. Match the term to the rack program and its expansion plan. Right-size your GPU commitment to your training and production needs before you sign. Share the brief, and we’ll route a warm request to the right TSD path for a right-sized proposal.

Choose NVL72 when you need the 72-GPU NVLink domain and facility readiness exists. Prefer DGX B200 or H100 / H200 when node-scale is enough.

NVIDIA markets both massive-scale training and high-throughput / real-time LLM inference. Our recommended workload default is High-Throughput Inference. Validate against your model and latency targets.

Up to 13.4 TB HBM3E and up to 576 TB/s aggregate GPU memory bandwidth, plus 130 TB/s NVLink domain bandwidth, support very large model-parallel workloads. Confirm figures on the partner rack BOM.

Sometimes, as allocated rack or platform capacity. Use neocloud sourcing and, when procurement structure requires it, the TSD channel. Verify cooling, power, and exact configuration.

Reserved (or committed allocation) fits production rack programs. True on-demand full racks are uncommon. Ask what “on-demand” means on that offer before you plan.

Exact GPU/CPU counts, HBM configuration, NVLink topology, liquid cooling, rack power, networking, dated window, substitution policy, ops model, and provider-owned compliance artifacts.

We give NVIDIA and AMD options equal weight on workload fit. We do not prefer one cloud or OEM. We route your requirements to the right TSD path. The TSD’s providers propose on availability and terms. No live price board.

GB200 NVL72 is a liquid-cooled rack connecting 36 Grace CPUs and 72 Blackwell GPUs in one NVLink domain. Each GB200 Superchip inside pairs one Grace CPU with two Blackwell GPUs. Our B200 vs GB200 guide compares it with eight-GPU B200 and DGX B200 nodes.

GPUSeeker finds the right TSD path for hard-to-source AI infrastructure and routes your requirements as a warm request. The TSD’s solutions engineers build a right-sized proposal, and the TSD and its providers run diligence and contract with you. There’s no charge for the conversation with GPUSeeker. We’re paid a small percentage of the project’s value, only after the TSD deploys it. GPUSeeker never handles your data, holds capacity, quotes prices, or reviews compliance controls.

Next step

Talk to a GPU sourcing advisor — decide rack-scale NVL72 vs node-scale Blackwell before you RFQ. Start a short conversation with an advisor. We’ll route a warm request to the right TSD path for a right-sized proposal.

Sources