Alibaba's CUDA alternative opens to outside developers
Alibaba spent its Apsara conference showing off silicon. The more consequential announcement came the day after, when it opened the software that decides whether anyone can actually use it.
T-Head, Alibaba's chip subsidiary, published a fresh round of open-source releases for T-Head SAIL on September 23 — the CUDA-style stack that sits between PyTorch and its homegrown Zhenwu accelerators — one day after unveiling the Zhenwu V900, which Alibaba CEO Wu Yongming called the most compute-capable AI chip in China at three times the performance of the M890 it succeeds. The new code covers PyTorch adaptation, a source-migration tool called sailify, a Triton-based operator toolchain, and acceleration libraries including DeepGEMM-for-sail and FlashAttention-for-sail. TensorFlow and JAX adapters, an in-house inference engine, and the PCCL and DeepEP communication components are still in progress. SAIL — short for Seed of AI Library — was first open-sourced at WAIC in July, and T-Head says the Zhenwu line now serves more than 650 customers across over 20 industries.
The reason to care is that the software layer, not the transistor count, is what keeps AI teams on Nvidia. T-Head's software-ecosystem director Lu Shenghua framed the customer question plainly: the biggest concern is how much migration costs. So the tools target what teams already have — models written for GPUs, operators tuned over years, hard-won performance knowledge — rather than asking them to start over. Ant Group's inference team has adapted major frontier models to run on the Zhenwu 810E and M890, and is still working through quantization, separating prefill from decode, expert-parallel load balancing and sparse attention. XPeng moved autonomous-driving training from GPU platforms onto Zhenwu cloud clusters, then used SAIL's profiling tools to find its bottlenecks. Xiaohongshu went further, building its own model-migration and operator-optimization agent on SAIL's open code to speed up generative-recommendation deployment — the outcome T-Head says it wants, where customers write their business knowledge back into the toolchain.
There is a second, quieter motive. Custom operators are where a customer's algorithmic edge lives, and few teams want to hand those details to a chip vendor so it can tune their code for them. Opening the stack lets companies write kernels against published architecture information and keep the core logic in-house, while contributing the parts they are willing to share upstream to PyTorch, vLLM and Triton — which also trims the maintenance bill of carrying a private fork. Day-one model support comes with it: by September 2026, T-Head had posted 39 quantized models to ModelScope covering the Qwen, DeepSeek and Kimi families, with more than 348,000 cumulative downloads. That is the number that decides whether a new model is testable on domestic silicon at all.
The strategy is coherent. The constraint has not moved: as we argued this week, Alibaba wants to own the whole stack. Memory says no — no toolchain fixes HBM yields, and the V900 needs memory China cannot yet buy in the volume the plan assumes.
What to watch: whether the PyTorch and vLLM contributions clear upstream review rather than living as a private fork, and whether the V900 ships in volume in the first quarter of 2027 as promised.
Would an open toolchain be enough to move your team off CUDA? Tell us in the comments.
Sources: QbitAI · TechNode · The Chosun Daily · Alibaba Cloud
