Alibaba just showed Nvidia its own playbook

Alibaba just showed Nvidia its own playbook

Good morning ๐Ÿ‘‹ Alibaba spent one Hangzhou keynote telling Nvidia it doesn't need it anymore: a new chip, a 10-trillion-parameter model roadmap, and 20GW of data centers to run it all on.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


๐Ÿ”ญ THE ONE THING

โšก Alibaba just showed Nvidia its own playbook

At Apsara in Hangzhou today, CEO Eddie Wu laid out the full stack: a new Zhenwu V900 chip claiming 3x the throughput of its predecessor and clusters scaling to 500,000 cards when it hits commercial production in Q1 2027. On the model side, Qwen 4 is training now, with Qwen 4.5 and 5 targeted at 5 to 10 trillion parameters, backed by a pledge to hit 20GW of global data-center capacity by 2032. The market bought it: Hong Kong shares gained about 5% overnight. Treat the 3x number as a vendor claim until someone independently reproduces it, but the 500,000-card cluster figure is the one that matters, because that's the first time a Chinese chip-to-agent stack has been pitched as a real Nvidia alternative instead of a stopgap. If Alibaba can actually deliver clusters at that scale, training runs that used to require a Nvidia allocation just got a second supplier.


๐Ÿง  MODELS & RELEASES


๐Ÿ›๏ธ POLICY & REGULATION


๐Ÿ› ๏ธ TRY THIS

Test-drive a quantized Qwen checkpoint before Alibaba's giant ones show up

Apsara talk of 5 to 10 trillion parameter Qwen models isn't running on your laptop, or anyone's. But Hugging Face just made it trivial to load the current Qwen3.5 and Qwen3.8 GGUF quants straight through Transformers, no llama.cpp conversion step required. Good week to find out if a small Qwen already covers what you need before the roadmap ships something you can't self-host.

1. Grab a Q4_K_M or Q5_K_M Qwen3.5 GGUF from Unsloth or bartowski on Hugging Face.

2. Load it with AutoModelForCausalLM.from_pretrained(model_id, gguf_file=filename). No conversion, no separate llama.cpp runtime.

3. Run your actual prompts against it, not a benchmark set. Log latency and where the answers diverge from whatever's in production now.

4. If it holds up, you've cut a dependency and a cost line. If it doesn't, you know that before the 10T-parameter version ships and someone asks why you're not on it.

Prompt: Run these 15 [your domain] prompts against the quantized Qwen3.5 checkpoint and the model currently in production. Flag any answer where they disagree on a factual claim, and log latency for each.

Worth a look


๐Ÿ”— QUICK LINKS


See you tomorrow.

Pradeep Perugu

Get inovAIte in your inbox.