Independent referenceSource-traced · reviewed 10 September 2026

Systems map

The NVIDIA platform, layer by layer

“The platform” is useful only when its layers stay visible. Compatibility and availability failures often happen at the boundary between them.

Reviewed 10 September 2026How we verify claims

The software path

A version printed at one layer cannot by itself establish the version or support state of every other layer.

[5][32][34][35]

The physical integration path

[13][18][23]

Use the map to diagnose the claim

If a press release says a platform is “available,” ask: which GPU or system, through which provider or channel, in which region, with which software version? If a workload fails, ask: is the issue hardware feature support, driver capability, toolkit installation, a library matrix, or application packaging?

The map turns a vague product question into a sequence of checkable claims.

[23][32][31]

Evidence trail

Sources used on this page

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

  1. CUDA C++ Programming Guide, archived 12.6

    NVIDIA Documentation · 2024

    Official documentation
  2. CUDA compatibility

    NVIDIA Documentation · Current documentation

    Official documentation
  3. TensorRT support matrix

    NVIDIA Documentation · Current documentation

    Official support matrix
  4. cuDNN support matrix

    NVIDIA Documentation · Current documentation

    Official support matrix
  5. NVIDIA completes acquisition of Mellanox

    NVIDIA Newsroom · 2020-04-27

    Company statement
  6. NVIDIA announces Hopper architecture

    NVIDIA Newsroom · 2022-03-22

    Company statement
  7. NVIDIA Blackwell platform announcement

    NVIDIA Newsroom · 2024-03-18

    Company statement
  8. CUDA Toolkit release notes

    NVIDIA Documentation · Current documentation

    Official documentation

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