DeepSeek V4: The open source model that reached the level of closed ones

For a long time, the divide was clear: proprietary models like GPT and Claude delivered the best performance, while open source ones stayed a step or two behind. In April 2026, DeepSeek V4 made that line hard to see.

What DeepSeek V4 is

Released on April 24, 2026 by the Chinese company DeepSeek, V4 arrived in two versions: V4-Pro, with 1.6 trillion total parameters and 49 billion active per inference, and V4-Flash, with 284 billion total and 13 billion active. Both use a Mixture of Experts architecture, an MIT license, and support a context of 1 million tokens.

An MIT license means: it can be used commercially, modified, redistributed. No royalties. No usage restrictions based on company size. This combination — frontier capability with a fully open license — is what makes V4 different from any previous release.

Architecture: real technical innovations

DeepSeek V4 is not just a bigger model. The team introduced three significant architectural innovations:

The first is the hybrid attention mechanism, combining Compressed Sparse Attention (CSA) and Heavily Compressed Attention (HCA). The practical result: at a context of 1 million tokens, V4-Pro requires only 27% of the single-token inference FLOPs and 10% of the KV cache compared to DeepSeek V3. This matters for those who operate infrastructure — cost and memory drop significantly.

The second is Manifold-Constrained Hyper-Connections (mHC), which replaces conventional residual connections. The goal is to improve signal propagation between layers without sacrificing the model's expressiveness — one of the classic tensions in deep architectures.

The third is the use of the Muon optimizer in training, which provides faster convergence and greater stability. The model was pre-trained on more than 32 trillion tokens.

Benchmarks: numbers that matter

V4-Pro-Max scores 80.6% on SWE-Bench Verified — the software engineering benchmark that tests the model's ability to resolve real GitHub issues. For reference, Claude Opus 4.6 scores 80.8% on the same benchmark. The difference is statistically irrelevant.

On LiveCodeBench, specific to competitive programming, V4-Pro-Max reaches 93.5 — leading all available open models. On GPQA Diamond, an advanced scientific reasoning benchmark, the model reaches 90.1%.

In agentic capabilities — execution of multi-step tasks, tool use, code workflows — V4 leads open source and effectively ties with the leading closed models.

What changes for those who build systems

The combination of closed-level benchmarks, an MIT license, a 1 million token context, and a cost of US$ 0.30 per million input tokens via API changes the calculus for developers and companies.

Until V4, choosing a high-performance open source model meant real quality tradeoffs. Now, for most use cases — coding, analysis, agents — the tradeoff has disappeared. The decision between closed and open becomes a matter of governance and compliance, not technical capability.

For datacenter operations, this has direct implications. Running V4-Flash (284B, 13B active) on your own infrastructure is now a viable option for high-volume workloads where cost per token matters. V4-Pro requires more hardware — but the choice exists.

The geopolitical context

It is impossible to discuss DeepSeek without mentioning the context. The company operates under American export restrictions that limit access to cutting-edge chips. The fact that V4 reaches parity with models trained on far larger hardware budgets is, in itself, a relevant technical data point.

V4's training and inference efficiency is not accidental — it is a direct consequence of operating under restrictions that force architectural innovation. HCA and mHC are ingenious responses to compute limitations, not marketing features.

Open source reached the frontier

DeepSeek V4 is not solely responsible for this change — Llama 4, Qwen 3.5, and Gemma 4 also contribute to the ecosystem. But it is the model that most directly eliminated the quality distinction between open and closed in the benchmarks that matter for production.

In 2024, the question was: "when will open source reach the level of proprietary models?" In 2026, with V4, the question has changed: "why pay for closed when open has already gotten there?"

The answer may exist — enterprise support, SLAs, native integrations, specific use cases. But the answer is no longer technical quality. And that changes the market.