DeepSeek released a V4 preview on Friday and explicitly framed it against Anthropic, Google, and OpenAI. My read is pretty direct: the heavier signal here is not “open source is catching closed source,” but that DeepSeek is now publicly tying its model roadmap to China’s domestic compute stack, with Huawei compatibility elevated into the first-wave narrative.
The actual information is thin. Parameter count is undisclosed. Benchmarks are undisclosed. Commercial timing is undisclosed. Even the coding improvement claim lacks a metric: no HumanEval, no SWE-bench, no internal task details. So I don’t buy the competitiveness claim on faith. What we can say from the snippet is narrower: DeepSeek sees coding as the front door for agents, and it wants the market to read V4 together with Huawei Ascend.
That context matters. Over the last year, OpenAI pushed Codex back into the workflow conversation, Anthropic turned Claude Code into a serious developer wedge, and Google kept steering Gemini toward code-centric agent use cases. Coding is no longer a prestige benchmark. It is the shortest path to an agent that touches an IDE, edits a repo, runs tests, and loops on tools. DeepSeek leading with coding tells me it is aiming at a practical insertion point: win developer workflow first, then argue broader capability parity later. I think that is the right battlefield. Plenty of teams learned that “better at code” monetizes faster than “better at chat.”
The Huawei line is the more strategic piece. A lot of Chinese model vendors spent the past year talking about domestic chip adaptation, but much of that language stayed at the engineering layer: portable, deployable, some operators adapted, partial stack support. DeepSeek putting compatibility near the center of a V4 preview says something stronger. It suggests the company wants to show that next-gen model progress no longer depends on Nvidia as the only credible substrate, at least not in public positioning. For the China market, that matters a lot. If your best model only runs well on H100, H200, or B200-class Nvidia infrastructure, open weights alone do not solve supply or policy constraints.
I do have a pushback here: “compatible with Huawei” can mean almost nothing, or it can mean a lot. There is a huge gap between a model that runs and a model that runs efficiently enough for real deployment. Throughput, memory efficiency, long-context stability, MoE routing overhead, compiler maturity, inference serving quality, and toolchain reliability decide whether enterprises scale it. The article gives none of that. No tokens per second. No cluster size. No cost curve. No deployment references. Without those numbers, I would not read this as proof that the Chinese stack has closed the gap. It reads as a declaration of direction.
I also think the headline framing risks overstating the wrong part. DeepSeek’s earlier shock effect was never just about raw model quality. It came from the combination of cost claims, open distribution, engineering credibility, and pressure on pricing assumptions. If V4 wants to repeat that, “we can compete with closed models” is not enough. It needs reproducible evidence, release timing, and deployment economics. Meta’s Llama waves spread because developers could get their hands on them quickly and test the claims. If DeepSeek delays weights or benchmark detail for too long, attention will outrun trust.
There is also a domestic comparison that matters more than the US rivalry framing. Alibaba’s Qwen line has been aggressive on open-source distribution, multilingual support, coding, and tool use, and its ecosystem reach is hard to ignore. So if DeepSeek wants V4 to become the default Chinese open model base, the competition is not only OpenAI and Anthropic at the frontier. It is also Qwen and other local stacks with better deployment familiarity and wider integrations.
So I would file this as a strategic positioning update, not confirmed model leadership. The clearest thing V4 has shown so far is not benchmark superiority. It is that DeepSeek is packaging code agents and domestic chips into one story. That story becomes credible only when three missing pieces show up: coding evals, real Ascend-side performance numbers, and a concrete open release schedule. Until then, this is a smart preview, not a settled result.