DeepSeek V4.1-Flash Review: MIT Weights, 1M Context, and $0.15 per Million Tokens (2026)

Introduction

DeepSeek shipped V4.1-Flash on September 10, 2026, and it is not a routine model refresh. Three things make it notable at once: a genuinely different architecture, MIT-licensed weights, and pricing that resets the floor for long-context agentic workloads.

The architecture is the part worth understanding. Previous "Flash" tiers were smaller, cheaper variants of a bigger sibling. V4.1-Flash is something else — a new structural family whose smallest member already outscores DeepSeek's previous flagship on the company's own benchmarks.

The Architecture: Encoder and Decoder, Split

V4.1-Flash runs 40 transformer layers split into a 20-layer causal encoder followed by a 20-layer decoder. The decoder's global KV cache is projected from the encoder's final hidden states rather than being built up layer by layer. That single design choice produces the model's signature characteristic: asymmetric activation.

On top of the 552B backbone sits a 196B Engram conditional memory (sparsely accessed), plus a vision encoder trained from scratch. The Hugging Face checkpoint reports higher totals once those modules are counted.

The KV cache compression is the other headline. DeepSeek reports a global KV footprint of roughly 890 bytes per token — about one quarter of V4-Flash — using FP4 caching (E2M1 with one E4M3 scale per 16 channels) and a sliding-window bounded replay that avoids writing the recent-window KV state to disk. DeepSeek's summary: HBM requirements down to roughly 1/4 and SSD storage to roughly 1/8 versus the prior generation.

Pricing: The Number That Changes Infrastructure Math

Peak hours are 01:00–04:00 and 06:00–10:00 UTC, Monday–Friday. Everything else — including all weekend hours — is off-peak.

Two comparisons put this in perspective:

• Against frontier models: Claude Opus 5 is listed at $5.00 input / $25.00 output, GPT-5.6 Sol at $4.00 / $20.00, Kimi K3 at $3.00 / $15.00. At off-peak rates, V4.1-Flash output costs roughly 40 times less than Opus 5.
• Cache economics: take a 500,000-token reusable prefix (system instructions, tool definitions, a repository context) read across 100 requests — 50 million cached input tokens. On V4.1-Flash off-peak that is about $0.15. The same cache reads would be roughly $15 on Kimi K3, $20 on GPT-5.6 Sol, and $25 on Claude Opus 5, before cache-write charges.

If your agent re-reads the same context on every turn — which most coding agents do — the cache-hit rate is the number that matters most, and $0.003 per million is close to free.

Benchmarks

DeepSeek published an extensive set. Treat these as vendor numbers: independent testers have not fully reproduced them, which is normal at launch and worth stating plainly.

Artificial Analysis put the model's Intelligence Index at 40, placing it above DeepSeek V4 Pro 0813 — the previous flagship — despite the "Flash" name.

Open Weights, Real Hardware

The weights are on Hugging Face under MIT, ungated. That matters more than the benchmark table for a specific class of buyer: MIT means commercial use, redistribution, and fine-tuning without revenue thresholds or enterprise agreements, and it lets teams keep sensitive workloads entirely on their own hardware.

The catch is the hardware floor:

• Checkpoint size: roughly 510GB
• Minimum practical self-hosting: 8x H100 (FP8 build)
• FP4 quantization: ~385GiB; a single B200 covers the native FP4+FP8 build
• Serving: SGLang ships a V4.1 preview with an option to keep Engram memory tables in host RAM; vLLM support is in progress

For most teams the API is the realistic path. Self-hosting makes sense when data residency or volume economics justify the GPU bill.

What DeepSeek Says Is Untested

DeepSeek acknowledged in its own documentation that the new architecture introduces robustness limits it has not fully characterized:

• sparse-selection errors
• approximate state reconstruction

Both could degrade capability in edge cases — specifically sparse retrieval over very long contexts and cache-resumption boundaries. Additional stress testing is planned. If your workload depends on retrieving precisely from a 1M-token context or resuming long sessions, schedule your own regression tests rather than assuming parity.

Migration: Handle the Model Name Carefully

The API model name is now deepseek-flash. The previous names — deepseek-v4-flash and deepseek-v4-flash-vision-exp — are retired but temporarily aliased.

Then there is the V4 Pro question, which changed twice in two days:

1. September 10: DeepSeek said all deepseek-v4-pro requests would route to V4.1-Flash from September 14 at Flash rates.
2. September 11: the pricing page and changelog gained a footnote saying V4 Pro continues after September 14 with unchanged billing, and further notice would come before any change. The original launch post still carries the earlier sentence.

Two official pages, one day apart, saying different things. Check the pricing page yourself before migrating. If your evaluation suite or prompt regression tests pin the old endpoint names, rerun them — a different model answering the same request changes output, latency, and formatting in ways your tracked metrics will not explain.

Who Should Use It

Summary

V4.1-Flash is the most consequential thing DeepSeek has shipped this year: a new architecture that makes long-context caching cheap, MIT weights that make it deployable in places previous releases were not, and pricing that forces every other provider to justify its per-token rate.

The honest caveats are equally clear. Vendor benchmarks are not yet independently reproduced, DeepSeek itself flags untested robustness limits in the areas that matter most for agentic work, and the V4 Pro migration messaging was inconsistent enough that you should verify rather than trust. For teams running re-read-heavy agents, though, the cache-hit economics alone justify a test.

For the previous generation, see our DeepSeek V4 Flash review; for the competitive picture, compare against Kimi K3 and our best Chinese AI models roundup.

Related Articles

• DeepSeek V4 Flash
• DeepSeek V4 API Price Increase
• Kimi K3 Review
• Best Chinese AI Models 2026