CUDA is NVIDIA's parallel computing platform and programming interface, first released in 2007, that lets developers write general-purpose code that runs directly on a GPU's thousands of small parallel cores, rather than only through the fixed graphics pipeline a GPU was originally built around.

That unlock mattered because a GPU's core design — many simple cores working on many pieces of data at once — turns out to be exactly the shape of computation machine learning needs: the same matrix multiplication, repeated over and over across huge amounts of data. That's a completely different workload than rendering a 3D scene, but it runs on the same underlying hardware.

It matters specifically for AI development because the major deep learning frameworks — PyTorch, TensorFlow — were built with CUDA as their primary accelerated backend, and a large share of the training and inference code the AI ecosystem has published over the past decade assumes CUDA is available. That's a real, practical reason NVIDIA GPUs remain the default recommendation for local AI development, separate from any raw hardware advantage on its own.

That dependency runs deep enough that moving a training pipeline built around CUDA-specific code to a different platform is rarely a drop-in change — it often means rewriting or re-validating the lower-level operations the framework was relying on CUDA to accelerate, which is a real switching cost, not just a preference.

CUDA isn't the only option — AMD's ROCm platform targets the same general-purpose GPU computing goal on AMD hardware, and Apple's Metal does the same on Apple Silicon — but neither currently matches CUDA's depth of existing framework support and pre-built tooling, which is the practical reason "does this run on CUDA" is still often the first compatibility question a developer asks before choosing a GPU for AI work.