Independent referenceSource-traced · reviewed 10 September 2026

Product taxonomy

GPU, HGX, DGX, and NVL are not interchangeable

These labels sit at different integration levels. Comparing them as if they were four GPU models produces bad conclusions about capacity, networking, deployment, and price.

Reviewed 10 September 2026How we verify claims

A practical integration ladder

Component

GPU

The processor or an accelerator product built around it. Exact form factor and memory still matter.

Base platform

HGX

A multi-GPU server platform used by system builders; it is not a complete end-user deployment by itself.

System

DGX

An NVIDIA-branded integrated system with a defined hardware and software configuration.

Rack scale

NVL

A tightly integrated multi-system configuration whose claim must name the exact generation and topology.

[18][23]

Four common comparison errors

  • Using total rack memory beside per-GPU memory without labeling units.
  • Comparing an announced rack configuration with a currently shipping accelerator.
  • Treating an architecture family as a single product specification.
  • Ignoring networking, power, cooling, software, and provider constraints.
[23][13]

A claim template that survives scrutiny

As of [observation date], [source owner] describes [exact product or system] at the [component / module / server / rack / cloud] level as [announced / sampling / shipping / generally available] for [named market or provider].

If any bracket is unknown, keep it unknown. Do not fill the gap with a broader marketing label.

Evidence trail

Sources used on this page

Source class describes ownership and form. It is not a reliability score.

  1. NVIDIA announces Hopper architecture

    NVIDIA Newsroom · 2022-03-22

    Company statement
  2. NVIDIA Blackwell platform announcement

    NVIDIA Newsroom · 2024-03-18

    Company statement
  3. NVIDIA completes acquisition of Mellanox

    NVIDIA Newsroom · 2020-04-27

    Company statement

Links reviewed for this local corpus on . An inaccessible link does not erase the claim record; it triggers source maintenance.