The standard $NVDA short thesis goes: AMD ships MI300X, then MI350X, then MI400 over 2024-2027, the hardware gap closes, NVIDIA's 75% gross margins compress, the stock derates. The thesis has been around since 2023. AMD has, in fact, shipped each of those parts roughly on schedule. NVIDIA's gross margins are still ~75%. AMD's data-center GPU revenue is roughly one-tenth of NVIDIA's despite shipping silicon that benchmarks competitive on raw FLOPs.
The bear thesis got the hardware right and missed everything else. The actual moat - the one you're long when you're long NVDA - is CUDA: a 19-year-old software ecosystem that turns NVIDIA's chips into the default substrate every AI model is written against, not just on. This article is what that moat looks like at the technical level, why migrating off it costs more than the chips, and what would actually break it.
The TL;DR. CUDA is not "drivers." It's a compiler (nvcc), a hand-tuned library stack (cuDNN, NCCL, cuBLAS, cuFFT, CUTLASS), a kernel language (CUDA C++, Triton), a debugger and profiler suite, and the de facto target every major ML framework optimizes against. AMD's ROCm covers maybe 60-70% of that surface on the parts where it works. Hyperscalers buy hardware on TCO; TCO includes the eight-figure engineering bill to revalidate the model zoo against a new substrate. NVIDIA's pricing power is not the silicon - it's the migration cost on the other side.
What CUDA actually is
When someone says "CUDA" in trader conversation they usually mean "the API NVIDIA's GPUs run." That's wrong by about three layers. CUDA is a stack:
Layer 1 - the driver and runtime. The low-level OS interface that lets a process talk to GPU memory and submit compute kernels. AMD has a working equivalent (ROCm runtime, formerly HSA). This layer is solved.
Layer 2 - the kernel language and compiler. CUDA C++ is the language; nvcc compiles it down to PTX (NVIDIA's intermediate representation) and then to SASS (machine code). Triton is a higher-level Python-embedded kernel language that NVIDIA acquired indirectly via OpenAI's open-source release and integrated. AMD has HIP (a CUDA-source-compatible language) and a HIP→ROCm compiler. The compatibility is source-level but not always behavior-level - performance regressions of 20-40% on identical kernels are routine when porting from CUDA to HIP.
Layer 3 - the hand-tuned library stack. This is where the moat actually lives:
- cuDNN - NVIDIA's hand-optimized convolution and attention primitives. Every major framework calls cuDNN for the inner loops of every transformer, every diffusion model, every recommendation system.
- NCCL - multi-GPU collective communication. The library that makes 8 GPUs in a server, then 8 servers in a rack, then 32 racks in a pod look like one machine to PyTorch. NCCL has been optimized against NVIDIA's interconnect (NVLink, NVSwitch, InfiniBand) for a decade. AMD's RCCL is functional but materially slower on the same fabric topology.
- cuBLAS - dense linear algebra. The GEMM (matrix multiply) primitives that drive the inner loop of attention, MLPs, and convolution kernels. cuBLAS has been tuned per-architecture (Volta, Turing, Ampere, Hopper, Blackwell) by a team that does nothing else.
- CUTLASS - open-source CUDA template library for GEMM and conv kernels. The reference implementation for "how do I write a custom kernel that hits 95% of peak on a given NVIDIA arch."
- cuFFT, cuSPARSE, cuRAND, cuSOLVER, Thrust - and 15 more domain-specific libraries that have no equivalent on the AMD side at all, or have equivalents three years behind.
Layer 4 - the framework integrations. PyTorch, JAX, TensorFlow, vLLM, TensorRT-LLM, DeepSpeed, Megatron-LM, FlashAttention, xFormers, BitsAndBytes - every framework or kernel library you've heard of is CUDA-first. The AMD/ROCm path is a port maintained by a smaller team, often a release behind, sometimes broken on the latest model release.
Layer 5 - the tooling. Nsight Systems, Nsight Compute, CUDA-GDB, the profiler suite. The tools an ML engineer uses to figure out why their kernel is 30% slower than peak and fix it. AMD has equivalents (rocprof, ROCm-GDB) that work but lag in capability.
Layer 6 - the ecosystem. Eighteen years of Stack Overflow answers, GitHub issues, NVIDIA developer forums, university CUDA courses, NVIDIA's own GTC tutorials. When a graduate student joining a research lab in 2026 learns GPU programming, they learn CUDA. ROCm is a footnote in the same curriculum if it appears at all.
When AMD or Google or Amazon competes on hardware, they compete with Layer 1 and (mostly) Layer 2. The moat is Layers 3-6.
Why the migration cost matters more than the chip price
A hyperscaler buying a $30,000 H100 isn't paying $30,000 for silicon. They're paying $30,000 because the rest of their stack - the training framework, the inference runtime, the model checkpoint format, the kernel library, the monitoring tooling, the team that knows how to debug a CUDA kernel - is all in CUDA. The migration cost of swapping NVIDIA out of the data center is:
1. Re-validate the model zoo. A hyperscaler is running hundreds of internal models - search, ads, recommendations, content moderation, generative - each tuned to run optimally on H100/H200/B200. Porting each to ROCm or to a custom ASIC means revalidating numerical equivalence (does the model produce the same output bit-equivalent? if not, does the divergence matter for the metric?), rerunning A/B tests, and accepting some non-zero risk of regression on a production system. The engineering cost per major model is multi-quarter.
2. Rewrite custom kernels. Every hyperscaler has internal-only fused-attention or MoE-routing kernels written in CUDA. Porting them to HIP works in theory; in practice the performance regression on the port is large enough that the team rewrites from scratch against AMD's CDNA architecture, which has different SIMD widths, cache hierarchy, and synchronization primitives. Senior CUDA kernel engineers are a 4-figure-globally talent pool. AMD-side equivalents are smaller.
3. Retool the inference stack. TensorRT-LLM is NVIDIA's optimized inference runtime - quantization-aware, kernel-fused, batching-aware. The ROCm equivalent (MIGraphX, vLLM-ROCm) is functional but behind. Migrating production inference latency budgets to AMD means accepting (initially) higher tail latency or running more silicon to compensate.
4. Train the team. ML platform engineers know CUDA. Moving to ROCm or custom-ASIC means a 6-12 month learning curve per engineer plus a hiring market where AMD-experienced talent commands a premium and is harder to find.
The cumulative cost is in the mid-9 figures for a top-5 hyperscaler to fully migrate off CUDA, with a 2-3 year project timeline. That's if the destination is fully ready, which on ROCm it's typically not. It's why hyperscalers' AMD purchases are concentrated in specific workloads where the migration cost has already been paid (inference for specific OSS models, certain HPC simulations) rather than across the board.
When NVIDIA prices H100/H200/B200 at 70-80% gross margin, they're pricing against the migration cost on the other side, not against AMD's per-chip BOM. As long as the migration cost stays north of "buy more NVIDIA chips at premium pricing," the moat holds.
What's actually narrowing the moat
The CUDA moat is real but not eternal. Three things are actively eroding it:
1. PyTorch 2.x and torch.compile. PyTorch is the framework most ML work happens in. Historically PyTorch was tightly bound to CUDA via the C++ extension layer. PyTorch 2.0 (released 2023) introduced torch.compile, a JIT compiler that targets multiple backends (Inductor → Triton → CUDA, but also → ROCm, also → custom IRs). The architectural shift is that the user writes pure PyTorch and the compiler emits backend-specific code. As torch.compile matures and the Inductor backend gets battle-tested on ROCm and AMD silicon, the framework-level lock-in to CUDA weakens. This is a 2-4 year process.
2. vLLM and the inference standardization. vLLM emerged as the de facto open-source inference runtime in 2023-2024 for LLM serving. It supports CUDA, ROCm, and custom ASICs via a plugin architecture. As more hyperscaler inference moves to vLLM-style runtimes (which is happening), the inference side of CUDA's framework dependency erodes. Training is still locked to CUDA-first frameworks; inference is incrementally portable.
3. Triton. OpenAI released Triton in 2021 as a higher-level Python-embedded kernel language. The promise: write a kernel once in Triton, compile to CUDA or ROCm or other backends. In practice Triton's CUDA backend is excellent, the ROCm backend is real but lags, and other backends are experimental. NVIDIA has co-opted Triton into the CUDA stack (it's now a CUDA-first project even though it's notionally portable). If Triton stays multi-backend in practice, kernel-level lock-in weakens. If NVIDIA fully captures it, Triton becomes another CUDA library.
The combined effect: the migration cost for a hyperscaler to swap NVIDIA out is going down ~10-20% per year on a base of mid-9 figures. The moat is corroding from the top (framework layer) toward the bottom (kernel layer). Library-layer lock-in (cuDNN, NCCL) is the hardest to erode - that's still 5+ years from genuine parity.
What this means for the NVDA bear case
The bear case has three traditional legs:
- Hardware competition - AMD and ASICs ship better silicon, margins compress.
- Customer concentration - top 5 customers are ~50% of revenue; one of them in-houses and the multiple compresses.
- HBM supply - Korean memory oligopoly limits the ramp regardless of NVDA's order book.
The CUDA moat directly defends against leg 1 and indirectly delays the impact of leg 2 (because an in-house ASIC still needs to clear the CUDA migration cost, which is a 2-3 year project before it can fully replace NVIDIA spend). It does nothing about leg 3 - see the HBM bottleneck analysis and the memory bubble dashboard for the supply-side dependency that no software moat can fix.
So the actionable bear case on NVDA isn't "AMD will catch up" - that thesis has been wrong for three years and the CUDA moat explains why. The actionable bear cases are:
- HBM supply caps the ramp at a level lower than the order book implies (real but already partially priced)
- Custom ASIC at a single hyperscaler drops their NVIDIA spend by 30%+ within 18 months (Google has done this with TPU for internal workloads; the question is whether Microsoft/AWS/Meta replicate at scale)
- A real PyTorch-level abstraction wins and the migration cost compresses below the chip premium NVIDIA charges (2027-2029 timeline if ever)
The trade-relevant version. Long $NVDA on the CUDA moat is long the next 3-5 years. Short $NVDA on "AMD catches up" has been the wrong trade since 2023 and the CUDA moat is the structural reason. The right short, if you must, is on HBM supply caps or hyperscaler in-housing - not on hardware competition. See the 12 AI bubbles ranked methodology for how memory + compute + custom-silicon trade as separate blocks even though the narrative groups them.
Three things to watch
The CUDA moat is the most important single variable in the NVDA thesis. Three signals that would mean it's eroding faster than priced:
1. PyTorch backend share data. Anonymized PyTorch telemetry (which Meta publishes irregularly) showing what fraction of model training is happening on ROCm vs CUDA vs custom-ASIC backends. If ROCm crosses 10% of PyTorch training compute, the moat is corroding. Currently estimated below 3%.
2. Hyperscaler 10-K language. Microsoft, Meta, Google, Amazon disclose AI capex but rarely break out NVIDIA vs custom share. Watch for language shifts in 10-Ks and earnings calls - "diversifying our AI compute substrate" is the leading indicator. When two of the top four say it in the same quarter, the moat is visibly eroding.
3. AMD MI400 or Instinct successor benchmarks on real models. AMD's MI300X benchmarks great on synthetic workloads, less great on the model zoo hyperscalers actually run. If MI400 (expected late 2026) ships with a real PyTorch story - meaning Meta, Microsoft, or Anthropic publish papers training large models on it at near-NVIDIA throughput - the bear thesis on hardware finally has teeth. To date, no such paper exists.
Bottom line
CUDA is not a library. It's eighteen years of compounding investment across compilers, libraries, frameworks, tooling, and the careers of every ML platform engineer in the field. AMD has shipped competitive silicon since 2023 and has captured roughly 10% of the data-center GPU revenue pool - not because the chips are bad, but because the migration cost of CUDA → ROCm exceeds the chip price differential at every hyperscaler that has actually run the math.
The right short on NVDA is supply-constrained (HBM, see the memory bubble) or customer-concentration-driven (custom ASIC at one of the top-5 buyers). The wrong short - the one that's been wrong for three years - is "AMD will catch up on hardware." On hardware they have. On the moat they haven't.
Live NVDA dashboard on QuantAbundance - the thesis panel with current technicals, fundamentals, and the bubble mapping.
The 12 AI bubbles ranked by empirical reality - the taxonomy that splits compute, memory, custom-silicon, and networking into separate blocks.
CXMT and the DRAM bubble - the memory-supply side of the NVDA constraint that the CUDA moat cannot fix.
To trade $NVDA from a US-retail or LLC account, see /stack/ibkr. Rule-based alerts on $NVDA and the AMD share-shift names are part of /pro.
