DeepSeek-V4-Pro Production Release – Performance Closing in on Fable 5 at 1/60th the Price
Overview
Late on August 12, 2026, DeepSeek quietly upgraded the V4 Pro model from preview to production. The update arrived without a formal launch event or release notes – the only indication was an update to the model version identifier in the API pricing page, now showing DeepSeek-V4-Pro-0813. The model name deepseek-v4-pro remains unchanged, so existing users can start using the new version without any code changes.
Earlier that same day, Elon Musk’s xAI also officially released Grok 4.6, which scored 1753 Elo on the GDPVal-AA v2 leaderboard, surpassing Fable 5. The simultaneous release of two high‑value flagship models drew widespread industry attention.
This article analyses the V4 Pro production upgrade across several dimensions: performance gains, benchmark results, cost‑effectiveness, and selection guidance between Flash and Pro. It should be noted that as of the time of writing (August 13, 2026), DeepSeek has not yet published a complete changelog for V4-Pro-0813. Benchmark data in this article comes primarily from community sources and unofficial channels – official figures should be awaited for confirmation.
V4 Series Parameter Recap
To better understand where this upgrade fits, here’s a quick recap of the V4 series specifications:
| Specification | V4-Pro Preview | V4-Pro Production (0813) | V4-Flash Production (0731) |
|---|---|---|---|
| Total Params | 1.6T | 1.6T (unchanged) | 284B |
| Active Params | 49B | 49B (unchanged) | 13B |
| Architecture | MoE | MoE | MoE |
| Context | 1M tokens | 1M tokens | 1M tokens |
| Max Output | 384K tokens | 384K tokens | 384K tokens |
| Release Date | 2026‑04‑24 | 2026‑08‑13 | 2026‑07‑31 |
Key takeaway: The model architecture has not changed. 1.6T total parameters, 49B active parameters, MoE architecture, 1M context window, and 384K max output length – all these hardware‑level specs have remained unchanged since the April 24 preview release. Similar to the Flash production release on July 31, the Pro production performance gains come primarily from extensive post‑training tuning.
In other words: the Preview version was the April baseline, Flash production was the July‑tuned lightweight version, and this Pro production release is the August‑tuned flagship version. Flash production had previously surpassed Pro Preview on Agent benchmarks; with Pro now receiving the same post‑training treatment, the performance gap has been corrected.
Ten Benchmark Comparisons: Preview vs Production
The following table shows cross‑verified benchmark comparisons. Note that Preview numbers are official scores from the April release, while Production numbers are from leaked community sources for the 0813 version – no independent third‑party reproduction results are available yet.
| Benchmark | V4-Pro Preview | V4-Pro Production (0813) | Improvement |
|---|---|---|---|
| Terminal Bench 2.1 | 72.1 | 87.9 | +21.9% |
| NL2Repo | 38.5 | 61.5 | +59.7% |
| Cybergym | 52.7 | 83.3 | +58.1% |
| DeepSWE | 12.8 | 62.7 | +389.8% |
| Toolathlon Verified | 55.9 | 74.1 | +32.6% |
| Agent Last Exam | 16.5 | 25.7 | +55.8% |
| Automation Bench (Public) | 12.8 | 31.8 | +148.4% |
| DSBench-FullStack | 41.8 | 71.1 | +70.1% |
| DSBench-Hard | 31.1 | 67.2 | +116.1% |
| HLE (w/ tools) | 48.2 | 60.0 | +24.5% |
Key highlights:
- DeepSWE jumped nearly 5× (12.8 → 62.7). This is DeepSeek’s in‑house software engineering benchmark, evaluating the model’s ability to modify code and fix bugs in real‑world engineering scenarios. The Preview’s 12.8 was low; the Production’s 62.7 surpasses Anthropic’s previous‑generation flagship Opus 4.8 at 58.0 – a qualitative leap.
- Terminal Bench 2.1 hit 87.9. This widely cited Agent benchmark evaluates the model’s ability to execute terminal commands, modify configurations, and fix issues. The Production score of 87.9 is just 0.1 points behind the top‑ranked Fable 5 at 88.0.
- Cybergym surpassed Fable 5: 83.3 vs 83.1. This benchmark tests cybersecurity attack/defence capabilities – surpassing the closed‑source leader in this domain is a significant milestone.
- Automation Bench and DSBench series doubled: automation workflows and full‑stack development capabilities both saw multiplicative gains – a generational leap.
Overall, the performance gap between Preview and Production is substantial.
Horizontal Comparison: Against Flash Production and Competitors
The following table shows leaked cross‑benchmark comparisons for the 0813 release against mainstream flagship models including Fable 5, Opus 4.8, GLM‑5.2, and Kimi K3:
| Benchmark | V4 Pro Production | V4 Flash Production | GLM‑5.2 | Kimi‑K3 | Opus‑4.8 | Fable 5 |
|---|---|---|---|---|---|---|
| HLE (w/ tools) | 60.0 | — | 54.7 | 56.0 | 57.9 | 63.0 |
| Terminal Bench 2.1 | 87.9 | 82.7 | 81.0 | 88.3 | 85.0 | 88.0 |
| NL2Repo | 61.5 | 54.2 | 48.9 | — | 69.7 | — |
| Cybergym | 83.3 | 76.7 | — | 80.0 | 78.3 | 83.1 |
| DeepSWE | 62.7 | 54.4 | 46.2 | 67.5 | 58.0 | 70.0 |
| Toolathlon‑Verified | 74.1 | 70.3 | 59.9 | 76.5 | 76.2 | 77.9 |
| Agent Last Exam | 25.7 | 25.2 | 23.8 | 27.6 | 25.7 | — |
| AutomationBench | 31.8 | 25.1 | 12.9 | 30.8 | 27.2 | 29.1 |
| DSBench‑FullStack | 71.1 | 68.7 | 61.8 | 73.7 | 71.6 | 77.2 |
| DSBench‑Hard | 67.2 | 59.6 | 54.5 | 63.0 | 71.7 | 68.3 |
The data shows a clear profile for Pro Production – it may not top every single benchmark, but it sits firmly in the top tier across all of them. It trails Kimi K3 by just 0.4 points on Terminal Bench (88.3 vs 87.9) but leads Opus‑4.8 (85.0) by 3 points; it takes first place on Cybergym at 83.3; both DeepSWE and NL2Repo are among the top; DSBench‑Hard at 67.2 is second only to Opus‑4.8’s 71.7.
“No obvious weak spots” is a core competitive advantage for Agent models. Agent tasks aren’t single‑turn Q&A – they involve multi‑step long‑chain execution: terminal operations, code modification, tool calls, data parsing, environment setup, and more. A deficiency in any single capability can cause the entire chain to fail. The Preview’s weak performance on long‑code tasks like DeepSWE (12.8, indicating a high failure rate) was a significant limitation; with that gap now addressed, the model’s real‑world Agent usability has improved dramatically.
It’s also worth noting that the performance gap between Flash Production and Pro Production has returned to “Pro slightly ahead” – about 5–10 points across benchmarks. Despite having a fraction of Pro’s parameters (284B vs 1.6T total, 13B vs 49B active), Flash remains exceptional value.
The Technical Path Behind the Performance Gains
Consistent with the Flash production upgrade, Pro’s performance gains come primarily from post‑training optimisation.
DeepSeek hasn’t published a technical report for Pro Production yet, but based on Flash’s changelog, it’s reasonable to assume the same upgrade strategy was applied – the model architecture, parameter count, and active parameter count were all left untouched, while the post‑training pipeline was thoroughly reworked. To use an analogy: it’s the same engine, but the transmission, ECU calibration, and suspension have been retuned – delivering better performance without hardware changes.
This suggests that under the MoE + post‑training technical roadmap, there’s still significant room to push the performance ceiling. Especially for long‑chain Agent scenarios, the model architecture itself is already capable – the bottleneck lies more in large‑scale post‑training tailored to code toolchains, terminal operations, and multi‑step reasoning. Training data quality and tuning strategies may have a greater impact on final performance than simply adding more parameters.
For context, here’s a quick recap of V4’s core architecture:
- MoE (Mixture of Experts): The 1.6T parameters are split into thousands of “expert sub‑models”; each forward pass activates only 64 experts (totalling 49B parameters) – meaning the model has the knowledge capacity of 1.6T but the inference compute cost of a 49B model.
- Hybrid attention (CSA + DSA + mHC): Reduces computational overhead in long‑context scenarios – at 1M tokens, per‑token inference cost drops to about 10% of V3.2, and KV Cache usage is significantly lower.
- Engram memory technology: Improves long‑context precision recall – better at retrieving details from large codebases and long documents.
New Capabilities: Multimodal Support, Responses API, and Codex Integration
The Preview was text‑only; Production natively supports image reasoning for the first time. According to 36Kr’s hands‑on testing, the DeepThink engine can analyse screenshots, interpret images, and process mixed text‑image documents within a single reasoning flow. For example, submitting an error screenshot allows the model to directly read the code, error messages, and stack trace from the image and propose a fix – eliminating the need for separate OCR preprocessing in development workflows.
On the API side, Pro Production shares the same interface capabilities as Flash Production:
- Native Responses API (OpenAI‑compatible) support – Codex tools (Codex CLI, ChatGPT desktop, VS Code Codex plugin) can be integrated by simply changing the base_url, with the same automated setup script as Flash
- Also supports Anthropic API format – Agent tools like Claude Code and OpenCode can switch backends by changing just one line of code
- Thinking mode toggle (enabled by default), JSON Output, Tool Calls, conversational prefix completion (Beta), and FIM completion (Beta, non‑thinking mode only) are all supported
In short, if you already have code calling Flash, migrating to Pro is as simple as changing the model parameter from deepseek-v4-flash to deepseek-v4-pro.
Pricing & Concurrency: 6 CNY/MT Output, Three Times Flash
The following pricing is from the official pricing page as of August 13, 2026:
| Pricing Item | V4 Pro Production (Off‑Peak) | V4 Flash Production (Off‑Peak) | Ratio |
|---|---|---|---|
| Input (cache hit) | 0.025 CNY | 0.02 CNY | 1.25x |
| Input (cache miss) | 3 CNY | 1 CNY | 3x |
| Output | 6 CNY | 2 CNY | 3x |
| Concurrency Limit | 500 | 2500 | 1/5 |
Pro is priced at about three times Flash – input cache miss rises from 1 CNY to 3 CNY, output from 2 CNY to 6 CNY, with cache‑hit pricing much closer. The concurrency difference is even more pronounced: Flash at 2500 vs Pro at 500 – consistent with their positioning (Flash for high‑volume requests, Pro for high‑value long tasks).
Peak‑hour pricing doubles (the time‑of‑use mechanism applies to Pro as well): 9:00‑12:00 and 14:00‑18:00 Beijing time (7 hours per weekday) – all pricing items double, meaning Pro output during peak hours is 12 CNY per million tokens.
International competitor pricing comparison (converted to USD):
| Model | Input (USD / MT) | Output (USD / MT) |
|---|---|---|
| DeepSeek V4 Pro | 0.435 | 0.87 |
| Claude Opus 4.8 | 5.00 | 25.00 |
| GPT‑5.5 | 5.00 | 30.00 |
| Fable 5 | 10.00 | 50.00 |
V4 Pro’s output price is about 1/28 of Opus 4.8 and 1/57 of Fable 5 – roughly on par with Grok 4.6’s output price ($6). Combined with its Terminal Bench 2.1 score just 0.1 points behind Fable 5, the claim of “performance closing in on Fable 5 at one‑sixtieth the price” is well grounded.
Two additional points:
- DeepSeek has already posted a price increase notice on the pricing page: “We plan to raise DeepSeek API pricing in the near future, with a significant increase expected – please plan your usage accordingly.” The current pricing window may be limited.
- The SWE‑bench Verified 80.6% figure has not been included in the main analysis, as it has only appeared in encyclopaedia entries and third‑party articles without official confirmation – treat it as unofficial until formally published.
Flash vs Pro – Selection Guide
| Use Case | Recommendation | Reasoning |
|---|---|---|
| Daily chat, light coding, content generation, Q&A | Flash | Flash Production already surpasses Pro Preview in performance, at 1/3 the cost |
| Large codebase refactoring, multi‑step terminal ops, complex Agent tasks | Pro | Clear advantages on long‑chain benchmarks like DeepSWE and Terminal Bench |
| Data analysis / data science (DSBench‑type tasks) | Leans Pro | DSBench‑Hard/FullStack show a performance gap; better completion rates on complex data tasks |
| High‑concurrency, low‑latency API services | Flash | 5× the concurrency limit (2500 vs 500) at 1/3 the cost |
| Ultra‑long context (entire books / large codebases) | Either; Pro if budget allows | Both support 1M context; Pro has better recall and reasoning stability in long‑chain tasks |
| Security / red‑team scenarios | Pro | Cybergym 83.3 vs 76.7 – a clear edge |
| Budget‑sensitive / individual developers | Flash primarily; switch to Pro for complex tasks | Flash handles most tasks well; significantly better cost efficiency |
Bottom line: For 95% of daily tasks, Flash Production is more than sufficient. Pro’s 3× price doesn’t translate to a 3× experience improvement in most scenarios. Pro’s strengths are concentrated in long‑chain Agent tasks, high‑difficulty coding, and complex data science – and for many users, the “small difference” they perceive is simply because their tasks aren’t demanding enough to reveal the 5‑point gap.
Additionally, according to 36Kr’s hands‑on testing, there are two practical considerations:
- In large‑scale code generation, Thinking mode can consume 80%+ of output tokens on reasoning, compressing the actual content. In BFS/DFS/A* visualisation tests, Thinking mode truncated output to about half, while disabling it allowed full execution in 54 seconds.
- Third‑party intelligence scores show divergence: Artificial Analysis gives V4‑Pro‑0813 an intelligence index of 53, only 1 point above Flash‑0731’s 52 – reinforcing the view that “the gap isn’t noticeable in everyday scenarios.”
Also worth watching is the DeepSeek Harness inference framework, currently in closed beta. The Harness team opened beta signups on August 1, with early testers reporting strong results. The framework’s impact on model performance may be larger than expected – whether the benchmark scores above are boosted by Harness optimisation is currently unconfirmed. Once Harness is publicly released, Pro’s practical performance may have further room to improve.
Concurrency, API Migration, and Practical Tips
Concurrency Limits
500 concurrent requests is plenty for most applications, but it’s important to understand the positioning difference from Flash’s 2500. Pro is designed for high‑value long tasks – using it for bulk text processing, data cleaning, etc., may hit concurrency bottlenecks, and peak‑hour costs double, making it less economical. Batch processing is best scheduled during off‑peak hours (nights/weekends) to halve costs; for non‑latency‑sensitive tasks, Flash reduces cost by about two‑thirds and eliminates concurrency concerns.
API Migration Guide
If you’re already using DeepSeek API, switching to Pro is as simple as changing the model name:
from openai import OpenAI
client = OpenAI(api_key="<your_api_key>", base_url="https://api.deepseek.com")
# Original Flash callresponse = client.chat.completions.create( model="deepseek-v4-flash", messages=[{"role":"user","content":"Write a quicksort implementation"}], temperature=1.0,)
# Switch to Pro – all other parameters stay the sameresponse = client.chat.completions.create( model="deepseek-v4-pro", messages=[{"role":"user","content":"Write a quicksort implementation"}], temperature=1.0,)For Anthropic‑format integration, simply change the base_url to https://api.deepseek.com/anthropic.
Codex Integration
Pro also supports Codex integration with the same setup as Flash – use the automated PowerShell script:
irm https://cdn.deepseek.com/api-docs/codex-deepseek-setup-en.ps1 | iexThe script backs up existing configs, writes to models.json, modifies config.toml, and validates syntax – aborting if anything goes wrong.
Cost Optimisation Tips
- Schedule batch tasks during off‑peak hours (12:00‑14:00, 18:00‑09:00, weekends/holidays) to halve costs.
- Place fixed system prompts and knowledge‑base prefixes at the very start of the messages array to maximise cache hit rates. Pro’s cache‑hit input pricing is 0.025 CNY per million tokens – about 120× cheaper than cache‑miss at 3 CNY.
- Route tasks by complexity – simple intent classification, categorisation, and summarisation can use Flash at 1/3 the output cost, saving significantly over time.
Pricing Trends and Industry Context
The “significant API price increase” notice on the pricing page is worth paying attention to. DeepSeek posted a related announcement on August 6, and the Pro production release didn’t coincide with a price adjustment – the length of this low‑price window is uncertain. DeepSeek has recently raised substantial funding at a high valuation, but compute costs remain a core constraint – V4 Flash alone has surpassed 4.66 trillion tokens in weekly calls on OpenRouter, topping the global charts for several consecutive weeks. The pressure behind such massive usage at consistently low prices is real.
Time‑of‑use pricing is essentially resource scheduling via price signals: when compute is scarce during weekday daytime hours, prices rise, shifting non‑urgent batch workloads to off‑peak periods to ensure stability for finance, development, and real‑time Agent scenarios. For developers, rather than worrying about price fluctuations, it’s better to build tiered routing and caching optimisation into your architecture – even if prices rise later, well‑prepared users can still keep costs under control.
Summary
V4 Pro Production represents a substantive generational leap, not a minor iteration: DeepSWE improved nearly 5×, Terminal Bench hit 87.9 (just 0.1 points behind Fable 5), Cybergym surpassed Fable 5, and multimodal and Codex support have been added. Combined with the 6 CNY per million tokens output price, it’s one of the most cost‑effective flagship‑class Agent models available today – far cheaper than comparable overseas models.
But Pro isn’t the best choice for every scenario: For everyday tasks, Flash Production already outperforms Pro Preview, at one‑third the cost and five times the concurrency. If Flash already meets your needs, don’t pay extra just for benchmark numbers. Only when you encounter long‑chain Agent tasks where Flash frequently fails should you consider switching to Pro.
A final note: this article was written on August 13, 2026. Some data comes from community sources and third‑party reports – DeepSeek has not yet published a complete changelog. Treat benchmark numbers as references, and validate performance against your own use cases.
With Pro Production now live, the V4 series product matrix is largely complete – Flash offers extreme cost‑effectiveness, Pro delivers flagship performance, with output pricing ranging from 2 to 6 CNY per million tokens, further lowering the global AI API pricing bar. For developers, this trend is broadly positive.
References
Information compiled from the following public sources. These are from the internet and not guaranteed to be fully accurate – for reference only. Prices, policies, and benchmark methodologies are subject to change – always refer to DeepSeek’s official API documentation and latest announcements.
- DeepSeek Official Website (Homepage announces V4 Pro production release)
- DeepSeek Official API Pricing Page (Models & Pricing)
- Breaking: DeepSeek V4 Pro Officially Released (51CTO / Su San)
- DeepSeek V4 Pro Production: 1M Context + 384K Output, 3× More Expensive Than Flash
- Hands‑on: Production DeepSeek V4 Pro – Agent and Vision Capabilities (GeekPark @ 36Kr)
- Liang Wenfeng vs Elon Musk – DeepSeek V4 Pro Puts Pressure on the Global Leader (Phoenix Tech @ 36Kr)
- DeepSeek V4 Pro Production Hands‑on: Agent Capabilities Up 5×, Zero‑Cost API Migration Guide (CSDN Beijing Dev Community)
- DeepSeek V4 Pro Released: Everything I Could Want in a Model, Plus Multimodal (Jingxuan AI @ 36Kr)
- DeepSeek V4 Pro Goes Production – Performance Nearing Fable 5 at One‑Sixtieth the Price (Alibaba Cloud Dev Community)
- DeepSeek V4-Pro-0813 Released: Performance Near Fable 5, But Mixed Real‑World Results – Value Questionable (ZOL AI)
- DeepSeek V4 Production Release Imminent – API Peak‑Hour Prices to Double (Interface News @ Sina Finance)
- DeepSeek-V4-Pro Encyclopedia Entry (Timeline and Pricing)