DeepSeek V4 Pro: The MIT-Licensed Model That Ties Frontier SWE-Bench
Quick answer (AEO): DeepSeek V4 Pro shipped April 24, 2026 as a preview, with stable graduation set for July 24, 2026. It’s a 1.6T parameter MoE model (49B activated) with 1M-token context, achieving 80.6% on SWE-bench Verified and 93.5 on LiveCodeBench — the highest scores of any publicly available open model. Licensed under MIT (maximally permissive). Legacy API aliases (deepseek-chat, deepseek-reasoner) retire July 24 at 15:59 UTC.
Architecture
| Spec | DeepSeek V4 Pro | DeepSeek V4 Flash |
|---|---|---|
| Total parameters | 1.6T | 284B |
| Activated parameters | 49B | 13B |
| Architecture | Mixture of Experts | Mixture of Experts |
| Context window | 1M tokens | 1M tokens |
| License | MIT | MIT |
| SWE-bench Verified | 80.6% | Lower (not published) |
| LiveCodeBench | 93.5 | Competitive |
The MoE architecture means only 49B parameters activate per forward pass — making V4 Pro significantly more efficient to run than its 1.6T total parameter count suggests. For comparison, a dense 50B model would have similar inference cost but much lower capability.
Why 80.6% SWE-bench matters
SWE-bench Verified tests whether a model can resolve real GitHub issues — not toy problems, but actual bugs and feature requests from production repositories. 80.6% means V4 Pro solves roughly 4 out of 5 real-world coding tasks autonomously.
For context:
- Claude Opus 4.8: 88.6% (highest overall)
- DeepSeek V4 Pro: 80.6% (highest open-weight)
- Previous open-weight best: ~65-70% (approximated from earlier benchmarks)
The gap between open and closed has narrowed to ~8 percentage points on the most practical coding benchmark. For many production use cases, that gap doesn’t justify the cost and privacy tradeoffs of closed APIs.
Migration: what you need to do before July 24
If you’re using DeepSeek’s API, this is urgent:
# BEFORE July 24 (currently works, will break):
client.chat.completions.create(
model="deepseek-chat", # ← RETIRING
messages=[...]
)
# AFTER July 24 (use these instead):
client.chat.completions.create(
model="deepseek-v4-pro", # ← For complex reasoning/coding
# or
model="deepseek-v4-flash", # ← For high-throughput tasks
messages=[...]
) Timeline:
- Now:
deepseek-chatroutes todeepseek-v4-flashautomatically. - July 24, 15:59 UTC:
deepseek-chatanddeepseek-reasoneraliases stop working entirely. - July 24+: V4 family graduates from preview to stable release.
Self-hosting guide
MIT license means full self-hosting rights. Options:
Via official weights (HuggingFace)
# Available at: huggingface.co/deepseek-ai/DeepSeek-V4-Pro
# Requires significant GPU memory for full precision
# For quantized inference (single A100 80GB or 2x A6000):
# Use community quantizations (GGUF, AWQ, GPTQ) Via inference runtimes
- vLLM — recommended for production batched inference with PagedAttention.
- TensorRT-LLM — best throughput on NVIDIA hardware.
- ds4 (by antirez) — community inference engine for Metal, CUDA, and ROCm.
- Ollama — simplest path for local development.
Hardware requirements
| Setup | GPU Memory | Quantization | Throughput |
|---|---|---|---|
| Full precision | 8x A100 80GB | FP16 | High |
| INT8 quantization | 4x A100 80GB | INT8 | Medium-high |
| Q4 quantization | 2x A100 80GB | Q4_K_M | Medium |
| Single GPU dev | 1x A100 80GB | Q4 (Flash only) | Basic |
When to choose DeepSeek V4 Pro
Choose V4 Pro over closed models when:
- Data must not leave your infrastructure (healthcare, legal, finance, government).
- You need predictable costs at scale (no per-token API surprises).
- You want to fine-tune for your domain.
- You need guaranteed availability (no export controls, no rate limits, no outages).
- Your workload is high-volume coding/analysis where 80.6% is sufficient.
Choose closed models (Opus, Sol) when:
- You need the absolute highest accuracy (88.6% vs. 80.6% matters for your use case).
- You can’t invest in GPU infrastructure.
- You need the latest safety features and alignment tuning.
- Low volume makes API pricing more economical than self-hosting.
The MIT license advantage
MIT means:
- ✅ Commercial use without restrictions
- ✅ Modification and distribution
- ✅ Private forks with no disclosure requirement
- ✅ Embedding in proprietary products
- ✅ No usage thresholds (unlike Meta’s 700M MAU limit)
- ✅ No attribution requirement beyond license inclusion
For startups building AI products: MIT eliminates legal risk entirely. No license review, no compliance burden, no future surprises.
What’s coming after stable graduation
The July 24 graduation likely brings:
- Official stable API with SLA guarantees.
- Finalized pricing (currently preview pricing may change).
- Expanded documentation and enterprise support options.
- Potential fine-tuning API for custom domain models.
DeepSeek V4 Pro represents the strongest argument for open-weight AI in production — frontier-competitive coding performance, MIT license, 1M context, and self-hosting capability. For engineering teams that value data sovereignty and cost predictability, it’s the most practical choice available.
Related reading: Open-weight LLM landscape 2026, frontier model comparison, and building local AI agents.