SDSignal Desk

Introducing CUDA Rust: Two Tracks for Writing GPU Kernels

Sep 8, 2026, 5:00 AM · NVIDIA Developer

Image: NVIDIA Developer

NVIDIA opens two official Rust paths to native PTX kernels—SIMT via cuda-oxide and Tile via cutile-rs—betting the AI systems stack will keep migrating to Rust.

Why it matters

Rust already shows up in NVIDIA’s own stack—Nova’s Linux driver, Dynamo’s core, NVTX bindings—but GPU kernels have mostly stayed in other languages even when launched from Rust. CUDA Rust aims to close that gap with kernels written in Rust and compiled natively to PTX, not wrapped foreign code.

The company mirrors CUDA’s own dual model: SIMT (thread-centric, familiar from CUDA C++ and numba-cuda) and Tile (data-tile-centric, with the compiler owning mapping). Guidance is explicit: prefer Tile first; drop to SIMT when you need manual control of threads and memory. Inter-language interop with CUDA C++ and Python is planned so a Rust choice does not strand teams.

The Signal Desk read

This is less a finished product launch than a strategic stake in the ground. Both projects are early-stage and, by NVIDIA’s own admission, not production-ready. cuda-oxide is early alpha: a custom rustc codegen backend through Pliron and LLVM, pinned nightly, heavier toolchain. cutile-rs is further along—stable Rust 1.89+, CUDA 13.3, on crates.io, and already used outside NVIDIA in HuggingFace’s Grout inference engine and mistral.rs.

Signal Desk's read: NVIDIA is treating Rust kernel authorship as inevitable for the inference/serving/agent-runtime layer and is buying influence before community toolchains harden around it. The safety pitch is the differentiator worth watching: both tracks try to make classic buffer-aliasing mistakes fail at compile time (DisjointSlice and launch contracts on SIMT; partition ownership on Tile). That is a real systems argument, not just syntax sugar.

What not to overclaim: maturity. Shared memory on the SIMT track still needs unsafe today; APIs will move; coverage is incomplete. The understated risk for NVIDIA is fragmentation—another frontend that teams try and abandon if nightly pins and incomplete coverage persist. Success looks like Tile becoming the default Rust path and SIMT graduating off nightly without losing the safety story.

Context

NVIDIA says it will grow and mature CUDA Rust into 2027 and beyond alongside mature CUDA C++ and Python toolchains. Community precursors (rust-cuda, Rust-GPU, CubeCL, and others) are acknowledged; NVIDIA says it has been working with rust-cuda maintainers. Melih Elibol is presenting “Fearless Concurrency on the GPU” at RustConf 2026 in Montréal.

Who feels it

Rust systems developers
They can prototype native kernels without leaving Rust, with Tile the lower-friction on-ramp and SIMT for fine-grained control.
Inference-engine builders
Early adopters such as Grout and mistral.rs signal where production pressure will push API stability first.
CUDA C++/Python shops
No forced migration; planned interop means Rust can enter incrementally where memory-safety or existing Rust services justify it.

What to watch

  1. Whether cuda-oxide sheds the pinned-nightly requirement.
  2. API stability and feature coverage on cutile-rs as external users file issues.
  3. Concrete interop demos mixing Rust kernels with C++ or Python CUDA code.

Read the original

Continue at the source.

NVIDIA Developer

Companies: NVIDIA