In June 2026, AMD confirmed shipping plans for a new device at the San Francisco AI DevDay. This machine, about the size of an Apple Mac mini and equipped with 128GB of unified memory, is officially positioned as a local AI development platform. Just a few months earlier, NVIDIA's DGX Spark had already appeared on developers' desktops – also a palm-sized metal box, also with 128GB of unified memory, also claiming it could run 200-billion-parameter large models locally.
AMD Ryzen AI Halo Developer Platform, featuring the Ryzen AI Max+ 395 Processor
Benchmark reports by Tom's Hardware, based on the HP Z2 Mini G1a, provide a reference price for the AMD camp: $2,949 to $3,999. NVIDIA's official website lists the DGX Spark starting at $3,999, with some OEM versions reportedly discussed for a price increase to $4,679 in February 2026. On price, AMD has a slight edge, but that's only surface-level accounting.
The Same 128GB, Two Different Paths
The heart of the AMD Ryzen AI Halo is a Ryzen AI Max+ 395 processor: 16 Zen 5 cores, 40 RDNA 3.5 architecture GPU compute units, paired with a 50 TOPS XDNA 2 NPU. NVIDIA's official hardware documentation describes the DGX Spark with a different logic: a GB10 Grace Blackwell Superchip, a 20-core ARM CPU paired with a Blackwell architecture GPU, no NPU, but packing a ConnectX-7 200Gbps network card. The AMD device offers a 2.5GbE port and WiFi 7; NVIDIA offers 10GbE plus WiFi 7, plus that valuable high-speed network card.
Memory specs appear similar on the surface. Both use 128GB LPDDR5x. AMD's product page lists memory bandwidth at 256 GB/s, while NVIDIA's official figure is 273 GB/s. A gap of less than 7%, barely perceptible in most inference tasks.
Operating system choices reveal a more fundamental divergence between the two companies. The AMD Ryzen AI Halo comes pre-installed with Windows 11 Pro, with Ubuntu 24.04 as an option. It boots into a standard PC desktop, has Thunderbolt ports, and full support for universal peripherals. The DGX Spark runs DGX OS, a customized Ubuntu, and the first task after booting is configuring the CUDA environment and NVIDIA container toolchain.
A detailed hands-on comparison by The Register in December 2025 concluded: For single-batch large language model inference, the token generation speed of the two machines was very close. However, in the prompt processing stage, the DGX Spark was 2 to 3 times faster. This gap comes from the Blackwell architecture's support for lower-precision computing and NVIDIA's years of optimized code paths for inference pipelines. ServeTheHome's review pointed out another dimension: The ConnectX-7 network card in the DGX Spark retails for over $900 alone, and its potential value in multi-machine cluster scenarios far exceeds that of single-machine inference.
According to Tom's Hardware and other media benchmarks, the Ryzen AI Halo measures 85mm high, 168mm wide, 200mm deep, weighing 2.3 kg, closer to a traditional mini workstation in stature. NVIDIA official documentation shows the DGX Spark is 150mm square, 50.5mm thick, weighing 1.2 kg. One resembles a stacked hard drive enclosure, the other a router.
ROCm's Progress Bar, No Longer Just "Good Enough"
AMD's official release notes show ROCm 7.2 went live in January 2026, with the subsequent 7.2.4 version specifically optimizing the stability and performance of AI inference workloads. Phoronix provided detailed coverage on release day.
For developers in Linux environments, ROCm's installation process has simplified significantly compared to two years ago. In March 2026, technical blogger Kunal Ganglani wrote in a detailed ROCm usage guide that it took him about 30 minutes to go from system configuration to running a PyTorch model on an RX 7900 XTX, "while in 2024, doing the same thing would take half a day." His blog confirms ROCm now supports the four major deep learning frameworks – PyTorch, TensorFlow, JAX, DGL – and inference engines like vLLM, Ollama, and llama.cpp have ROCm backends available.
But this progress can't overcome CUDA's inertia. NVIDIA's software stack has accumulated over 17 years; the number of CUDA-related Q&A posts on Stack Overflow is dozens of times that for ROCm. New versions of cutting-edge libraries like FlashAttention and xFormers typically release CUDA versions first, with ROCm ports following weeks to months later. Any custom CUDA kernel that goes beyond the standard PyTorch API requires manual adaptation on the AMD platform. AMD's official compatibility matrix lists validated framework and GPU combinations, but "validated" and "having enough community discussion posts to search when problems arise" are two different things.
On Reddit's r/LocalLLaMA subreddit, discussion threads about which device to choose haven't stopped since late 2025. A frequently quoted summary comes from the end of Ganglani's blog: "If you need everything to work perfectly on day one, buy NVIDIA. If you're willing to spend an afternoon troubleshooting to save $800, ROCm is ready."
AMD seems well aware of this. Over the past year, the company's moves haven't been about directly replicating NVIDIA's moat but building a separate path outside it.
In August 2024, AMD announced the acquisition of ZT Systems for $4.9 billion. The Wall Street Journal confirmed the transaction's completion in March 2025. ZT Systems' business involves designing and assembling entire rack-scale AI server systems for hyperscale data center customers, including giants like Microsoft and Meta that purchase tens of thousands of GPUs annually. AMD gained system design capabilities from a single GPU to an entire rack.
But AMD soon made a seemingly contradictory decision. According to a Sanmina official announcement in May 2025, AMD spun off ZT Systems' data center manufacturing business to this electronic manufacturing services company, retaining only the design team. The logic is clear: AMD doesn't want to become a competitor to its own OEM customers. If AMD produced AI servers itself, server vendors selling AMD GPUs would immediately become wary. Keeping design capabilities and outsourcing manufacturing balanced capability acquisition with ecosystem relationships.
Two more critical events occurred in the following six months.
In October 2025, an AMD official press release announced a strategic partnership with OpenAI to deploy 6 GW of AMD Instinct GPUs. The first 1 GW was scheduled for shipment in the second half of 2026. A clause was hidden in this agreement: OpenAI had the option to purchase up to a 10% stake in AMD. Reuters and CNBC both highlighted this detail in their coverage that day. The GPUs supplied to OpenAI would be the next-generation Instinct GPUs, with specific models not disclosed by AMD.
In February 2026, AMD issued another official press release announcing an expanded partnership with Meta, also for deploying 6 GW of GPUs. This time the chips were custom MI450 variants for Meta, with shipments planned to begin in the second half of 2026. CNBC's report that day pointed out a detail: Just days before this collaboration was made public, Meta also announced an expanded AI chip procurement agreement with NVIDIA.
The fact that Meta signed long-term orders with both companies simultaneously is more telling than any technical comparison. For companies investing tens of billions of dollars annually in AI infrastructure, putting all their eggs in one basket is an unacceptable risk. AMD doesn't need to surpass NVIDIA in all aspects of performance; it just needs to provide a viable alternative outside of NVIDIA to secure orders under the "dual-supplier" logic. The scale of the two 6 GW contracts suggests that at least OpenAI and Meta have included AMD on their list.
NVIDIA's Concurrent Response Was a Combination of Moves
During the same period, NVIDIA played a combination of moves in the enterprise market. The DGX Spark is positioned as a developer desktop device, but its ConnectX-7 network card dictates it's not an isolated workstation. ServeTheHome's review analyzed the value of this network card in prototyping and distributed training debugging, concluding that while much slower than data center-grade NVLink, it's sufficient for small-scale cluster scenarios. This design anchors the DGX Spark within NVIDIA's larger enterprise product line: developers prototype on Spark, then migrate code to a DGX Station or cloud DGX instance, and finally deploy to server clusters equipped with H200 or B200 GPUs. A toolchain from desktop to data center, with consistent hardware and software, is welded onto CUDA.
NVIDIA also concurrently launched the AI Enterprise software subscription suite, bundling tools like TensorRT, RAPIDS, and the Triton Inference Server, charging per node. NVIDIA's official product page lists the complete tool inventory included in AI Enterprise. This isn't selling hardware; it's turning enterprise deployment and operations into a recurring revenue stream after developers are accustomed to CUDA.
Comparing the two paths, the divergence is clear enough.
NVIDIA has built a full-stack closed loop from chips to systems to software to cloud services. Developers can use optimized tools from their first day in this loop, at the cost of being locked into a single vendor's ecosystem. AMD is taking an open alternative route: using industry-standard x86 architecture, supporting both Windows and Linux, making ROCm an open-source stack compatible with mainstream frameworks, and using lower prices to attract cost-sensitive customers or those who have decided to diversify supplier risk.
The Ryzen AI Halo product itself is the most concise hardware expression of this route. It has no custom network card, no dedicated OS, no low-precision training acceleration units. It's a general-purpose PC that happens to pack unified memory capable of running 200B parameter models and a decent GPU. You can use it for large model inference, or close the terminal and open Photoshop. The $2,949 price for the HP Z2 Mini G1a referenced in Tom's Hardware's report is significantly lower than the DGX Spark's $3,999 starting price; with other OEM versions, the price difference could exceed $1,000.
But the flip side of this flexibility is compromise. The Register's benchmark data already shows that once you move away from single-batch inference into scenarios requiring massive parallel computing, Blackwell's low-precision advantages and years of optimized software stack quickly widen the gap. If you need a desktop box that can run Stable Diffusion for image generation, NVIDIA's CUDA ecosystem has a whole set of ready-to-install tools. AMD's RDNA 3.5 architecture doesn't support FP4 and FP8 low-precision formats, putting it at a performance disadvantage in workloads like image generation – a limitation determined by the RDNA architecture design, not something driver updates can solve.
The Box's Destiny Lies Outside the Box
Bringing the timeline back, AMD's actions over the past year form a fairly clear path.
At the hardware level: Instinct MI300 and MI325X in mass production, MI350 and MI450 progressing according to roadmap, Ryzen AI Max+ 395 evolving from a notebook chip to a desktop APU packed into a development platform. At the system level: Acquiring rack-level design capability through ZT Systems, then spinning off manufacturing while retaining R&D. At the customer level: Securing two 6 GW-level long-term contracts with the world's two largest AI compute consumers, bringing OpenAI onto the shareholder list. At the software level: ROCm iterating at roughly a version per quarter, catching up with mainstream framework support, though porting cutting-edge libraries and building community resources still need time.
Each step isn't isolated. Acquiring ZT Systems was to gain the ability to design the kind of hyperscale AI clusters OpenAI and Meta need, not just sell GPUs to server vendors. ROCm's rapid iteration is to ensure that customers signing 6 GW contracts have a usable software stack upon deployment, not just bare metal delivery. Launching the Ryzen AI Halo is to extend the same ROCm ecosystem to the desktop, allowing developers to use a $3,000 machine for local debugging before deploying models to a cloud-based MI450 cluster.
But this doesn't mean AMD has caught up with NVIDIA. The two 6 GW contracts are future deployment commitments; the energy capacity measured in gigawatts reflects infrastructure planning scale, not chips already shipped. The specific specifications of the MI450 remain undisclosed; the chip's actual performance, yield, and stability after large-scale deployment are unknowns. ROCm is "usable" on mainstream frameworks, but the state of "the community can help you when problems arise" requires more time to accumulate. And 17 years of CUDA accumulation can't be erased by a few quarters of rapid iteration.
NVIDIA's moat isn't just in software either. The ConnectX-7 network card in the DGX Spark hints at another dimension of competition: While AMD competes for developers with cost-effectiveness and openness, NVIDIA locks in teams needing distributed training and large inference pipelines with cluster expansion capabilities. Buying one DGX Spark costs $3,999; buying two plus a network cable lets you run distributed prototypes. In this scenario, ROCm's parity in single-machine inference is neutralized.
When the divergence between the two companies in AI finally lands on this palm-sized box, it becomes a concrete choice. You open AMD's box, get a familiar PC environment, install PyTorch with almost the same commands, load a model, start inference – the process is smooth until you need to use a library that only has a CUDA backend. You open NVIDIA's box, get a dedicated environment optimized from hardware to drivers to container toolchains, where everything works as expected upon startup, just with an extra thousand dollars on the bill, and the migration cost of switching suppliers in the future is already pre-locked.
AMD isn't directly challenging NVIDIA's full-stack empire. It chose a more pragmatic path: being a good-enough alternative when NVIDIA's pricing and supply chain delivery capacity can't meet all customer demand. The two 6 GW contracts are the strongest evidence of this strategy so far. The Ryzen AI Halo is an extension of this strategy to the desktop – not following the trend of making small AI boxes, but taking a step forward along the line of "using an open ecosystem and cost advantage to attract developers who don't want to be locked in."
