After three months of preview access, DeepSeek V4 GA went live on July 20, 2026. If you are choosing an open-source LLM for production coding or still calling legacy deepseek-chat endpoints, this article gives you the full picture: release timeline, CSA+HCA architecture, benchmark scores against GPT-5.6 Sol and Claude Fable 5, peak-valley pricing, and the July 24 migration deadline. Bottom line: V4 does not beat closed-source flagships on every benchmark, but it delivers the strongest open-source performance at roughly 1/10 to 1/100 the cost — with new scheduling complexity from time-of-day billing.
SECTION 01 Three risks when DeepSeek V4 GA lands in your production stack
- Legacy endpoints shut down July 24:
deepseek-chatanddeepseek-reasonerstop responding after July 24, 2026 at 15:59 UTC. Unmigrated services break immediately. - Peak-valley pricing is new: Weekday Beijing hours 09:00–12:00 and 14:00–18:00 double all rates. A 24/7 pipeline with no scheduling can blow past budget.
- Cloud APIs do not replace native compile chains: V4-Pro cannot run Xcode signing or Metal shader debugging inside virtualized macOS reliably — the same gap discussed in our Mac Mini M4 rent vs buy analysis.
- Preview vs GA expectations: GA adds Agent, math, and code improvements on the same architecture. Re-evaluate on new pricing and benchmarks, not April preview scores alone.
SECTION 02 DeepSeek V4 release timeline: preview to GA in three months
| Date | Event |
|---|---|
| 2026-04-24 | V4 preview + MIT open weights — V4-Pro (1.6T) and V4-Flash (284B) |
| 2026-05 | Production-tuned V4-Flash and V4-Pro; API generally available |
| 2026-06 | V4-Pro output price cut 75% permanently to $0.87/M tokens |
| 2026-06-29 | Email to all API users announcing mid-July GA and first disclosure of peak-valley billing |
| 2026-07-19 | Gray-test access for selected developers; media reports GA imminent |
| 2026-07-20 | GA release — full production version live |
| 2026-07-24 | deepseek-chat and deepseek-reasoner permanently deprecated |
The preview was already strong. GA layers targeted gains in Agent workflows, mathematical reasoning, and code generation — plus a formal commercial billing model that moves DeepSeek from near-free tiers toward disciplined peak-valley pricing.
SECTION 03 V4-Pro vs V4-Flash: CSA architecture and three inference modes
| Spec | V4-Pro | V4-Flash |
|---|---|---|
| Total parameters | 1.6 trillion (1.6T) | 284 billion (284B) |
| Active params per token | 49 billion (49B) | 13 billion (13B) |
| Transformer layers | 61 | 43 |
| Context window | 1,000,000 tokens | 1,000,000 tokens |
| Max output | 384K tokens | 384K tokens |
| Precision | FP4 (expert weights) + FP8 (rest) | FP4 + FP8 mixed |
| Pre-training tokens | 33T+ | 32T+ |
| License | MIT | MIT |
DeepSeek V4 drops the MLA design from V2/V3 in favor of a hybrid of Compressed Sparse Attention (CSA) and Heavily Compressed Attention (HCA). CSA applies Softmax-gated pooling to compress the KV sequence 4×, then uses an FP4 "lightning indexer" for top-k sparse selection — top-1024 on Pro, top-512 on Flash — while keeping a 128-token sliding window for recent context. HCA compresses tokens 128× for global dense attention, complementing CSA's local sparsity.
At 1M context, V4 needs only 27% of the inference FLOPs compared to V3.2, with KV cache memory at 10% of V3.2 (Flash as low as 7%). Manifold-constrained Hyper-Connections (mHC) stabilize the 61-layer stack via 4-channel residual flows and doubly-stochastic matrix constraints. Training uses the Muon optimizer (Newton-Schulz orthogonalized gradients) instead of AdamW for faster, more stable convergence.
| Mode | Behavior | Best for |
|---|---|---|
| Non-think | No chain-of-thought; fastest latency | Simple Q&A, routing, classification |
| Think High | Explicit reasoning with thinking tags | Medium-complexity tasks, code debugging |
| Think Max | Maximum reasoning depth; needs 384K+ context | Hard math, long-horizon agents |
Recommended sampling for all modes: temperature=1.0, top_p=1.0.
SECTION 04 Benchmarks: open-source leader on SWE-bench, leader on cost per point
| Benchmark | DeepSeek V4-Pro | Claude Fable 5 | GPT-5.6 Sol | Claude Opus 4.8 |
|---|---|---|---|---|
| SWE-bench Verified | 80.6% | 96.0% | Not separately published | ~69% |
| SWE-bench Pro | 55.4% | 80.3% | 78.1% | 69.2% |
| LiveCodeBench (Pass@1) | 93.5% | 88.1% | 87.4% | 83.2% |
| Codeforces Elo | 3,206 | — | — | — |
| Terminal-Bench 2.1 | 83.9% | 88.0% | 85.1% | 82.7% |
SWE-bench Verified measures real GitHub bug fixes. At 80.6%, V4-Pro holds the open-source record, tied with Gemini 3.1 Pro. Claude Fable 5 still leads overall, but cost tells a different story: on Artificial Analysis Strategy & Ops index tasks, Fable 5 costs $3.48 per 50 points while V4-Pro costs $0.03 per 38 points — roughly 116× cheaper for a score only ~31% lower.
SECTION 05 V4 vs GPT-5.6 Sol vs Claude Fable 5 — and peak-valley pricing explained
| Dimension | DeepSeek V4-Pro | GPT-5.6 Sol | Claude Fable 5 |
|---|---|---|---|
| Open source / self-hostable | Yes — MIT | No | No |
| Context window | 1M tokens | Not disclosed | 1M tokens |
| Off-peak output price | $0.87/M | ~$15/M | $50/M |
| Peak output price | $1.74/M | — | — |
| Coding strength | Very strong (near Fable 5) | Very strong | Strongest |
| Data privacy | Private deployment possible | Cloud only | Cloud only |
Scene selection: Tight budget, high call volume, or private deployment → V4-Pro or V4-Flash. Maximum code quality regardless of cost → Claude Fable 5. Complex algorithms and math → GPT-5.6 Sol / Ultra. Massive log ingestion and routing → V4-Flash (cache-hit input at $0.0028/M). For a head-to-head on another open-weight contender, see our Kimi K3 open-source LLM review.
| Model | Billing item | Off-peak | Peak |
|---|---|---|---|
| V4-Pro | Input (cache hit) | $0.0035 | $0.007 |
| V4-Pro | Input (cache miss) | $0.435 | $0.87 |
| V4-Pro | Output | $0.87 | $1.74 |
| V4-Flash | Input (cache hit) | $0.0028 | $0.0056 |
| V4-Flash | Input (cache miss) | $0.14 | $0.28 |
| V4-Flash | Output | $0.28 | $0.56 |
Cost-saving tips: Schedule non-real-time batch jobs after 18:00 or before 09:00 Beijing time. Maximize prompt cache hit rates on repeated system prompts. Route simple queries to V4-Flash and escalate only hard reasoning to V4-Pro. Even at peak, V4-Pro output at $1.74/M remains 8.6× cheaper than Claude Opus 4.8 ($15/M).
SECTION 06 API migration before July 24: six steps and SDK examples
Hard deadline: deepseek-chat and deepseek-reasoner stop serving requests after July 24, 2026 at 15:59 UTC.
| Legacy model | Replacement | Notes |
|---|---|---|
deepseek-chat |
deepseek-v4-flash (Non-think) |
Fast path for lightweight tasks |
deepseek-reasoner |
deepseek-v4-flash (Think High/Max) |
Or upgrade to deepseek-v4-pro |
- Search your codebase: Grep for
deepseek-chatanddeepseek-reasoneracross repos, CI configs, and environment variables. - Pick the target model: Lightweight chat →
deepseek-v4-flash; complex reasoning and code →deepseek-v4-pro. - Update OpenAI SDK calls: Change only the
modelfield; keepbase_url=https://api.deepseek.com. - Enable thinking mode: Pass
extra_bodywith a thinking config to replace legacydeepseek-reasonerbehavior. - Load-test in staging: Verify latency, token billing, and peak-hour cost against your SLA.
- Canary before July 24: Shift production traffic gradually and monitor error rates. DeepSeek commits to 24-hour email notice before any future billing change.
- Update Anthropic SDK clients: V4 supports Anthropic Messages format — same
base_url, newmodelID only.
from openai import OpenAI
client = OpenAI(
api_key="your-deepseek-api-key",
base_url="https://api.deepseek.com"
)
response = client.chat.completions.create(
model="deepseek-v4-pro",
messages=[{"role": "user", "content": "Hello, DeepSeek V4!"}],
extra_body={"thinking": {"type": "enabled", "budget_tokens": 8000}}
)
import anthropic
client = anthropic.Anthropic(
api_key="your-deepseek-api-key",
base_url="https://api.deepseek.com"
)
message = client.messages.create(
model="deepseek-v4-pro",
max_tokens=4096,
messages=[{"role": "user", "content": "Analyze this repository for security issues."}]
)
SECTION 07 Citable technical data and authoritative sources
- KV cache at 1M context: 10% of V3.2 memory (Flash: 7%)
- Inference FLOPs at 1M: 27% of V3.2
- Cost per task: V4-Pro $0.03 vs Fable 5 $3.48 — 116× gap on Strategy & Ops index
- Peak still cheap: $1.74/M output vs Opus 4.8 at $15/M (8.6× advantage)
- Migration cutoff: 2026-07-24 15:59 UTC
- Sampling defaults: temperature=1.0, top_p=1.0 across all modes
Official and third-party references — re-check links after upstream updates:
DeepSeek API official documentation
arXiv:2606.19348 — DeepSeek V4 technical paper
Artificial Analysis — model cost-efficiency benchmarks
DeepSeek V4 GA is one of 2026's most significant open-source milestones — not because it beats Claude Fable 5 on every score, but because it delivers frontier-class capability at a fraction of the price. Still, no cloud LLM replaces Xcode compilation, Metal debugging, or iOS certificate chains. Virtualized macOS carries EULA risk and 20–40% performance overhead. The efficient stack pairs V4 API for long-context reasoning and agent orchestration with VPSNIX M4/M4 Pro physical nodes for native builds and 24/7 deployment: 100% Apple hardware, full root access, zero hypervisor tax. See the pricing page; if you already read the Kimi K3 review, lock compute into compliant physical infrastructure rather than betting on a single API vendor's pricing curve.
SECTION 08 FAQ
What changed between the V4 preview and GA?
Same architecture; GA adds targeted gains in Agent workflows, math, and code generation plus peak-valley billing. Legacy deepseek-chat and deepseek-reasoner deprecate July 24.
When are peak pricing hours?
Weekdays Beijing time 09:00–12:00 and 14:00–18:00. All rates double during peak; off-peak applies outside those windows and on weekends.
V4-Pro or V4-Flash — which should I use?
Flash for lightweight routing and high-frequency calls (output $0.28/M off-peak). Pro for complex reasoning and code (output $0.87/M, SWE-bench Verified 80.6%).
Can I self-host DeepSeek V4?
Yes — MIT license. V4-Pro at 1.6T parameters needs a large GPU cluster; most teams find the API more economical.