DeepSeek V4.1 Pro Deep Dive: Release Signals & Specs

DeepSeek V4.1 Pro Early Access Signals: Deep Dive Into the Hidden Slug, the 180 t/s Probe, and the V4.1 Flash Blueprint

DeepSeek V4.1 Pro has not shown up as a model card, a Hugging Face upload, or a price sheet. It first appeared as a single dependent clause. On September 10, 2026, DeepSeek said V4 Pro traffic would be handled by V4.1 Flash "until V4.1-Pro launches." As of October 16, 2026, five weeks later, the model still does not answer on any public API. In its place there is a hidden slug, a post-outage probe clocked at roughly 180 tokens per second, and a prediction market giving it 16% odds of shipping by October 31.

TLDR DeepSeek has confirmed in writing that V4.1 Pro exists and belongs to the same architecture family as V4.1 Flash. It has not published a date, size, price, license, or benchmark. Community trackers report a deepseek-v4.1-pro slug in per-account early access since September 27, and an October 15 probe of a possibly new model on DeepSeek's service. Neither claim is vendor-confirmed. The best guide to what Pro might look like is V4.1 Flash: 552B total parameters, 8B/16B active, 1M context, MIT license.

Key Takeaways

• DeepSeek named V4.1 Pro in its September 10 V4.1 Flash announcement. Every other detail comes from the community.
• The planned reroute of V4 Pro traffic to V4.1 Flash was reversed before its September 14 deadline. V4 Pro stays up with billing unchanged.
• A deepseek-v4.1-pro slug was reportedly spotted in per-account early access on September 27. This rests on one account and one screenshot.
• Polymarket priced the next DeepSeek Pro at 16% by October 31 and 31% by November 30 as of October 16.
• Parameter guesses vary widely. One account expects "at least 2.6T". The confirmed V4 Pro baseline is 1.6T total and 49B active.
• No benchmarks exist. Any V4.1 Pro score circulating today is unverified.

What Was Actually Seen

The public record is thin but consistent. Here is the timeline, with each entry graded by source quality.

Date (2026)	Event	Source type	Status
Sep 9	V4.1 Pro described as "in the works"	Community commentator	Commentary
Sep 9	V4 Pro traffic to route to V4.1 Flash "until V4.1 Pro launches"	Community + DeepSeek notice	Later reversed
Sep 10	V4.1 Flash ships; DeepSeek names V4.1 Pro	Vendor announcement	Confirmed
Before Sep 14	V4 Pro reroute cancelled, billing unchanged	Vendor message to API users	Confirmed
Sep 14	DeepSeek web and API outage	Community observation	Observed, cause unknown
Sep 27	deepseek-v4.1-pro slug in per-account early access	Single account, screenshot	Unverified
Sep 28	Initial Pro checkpoint reportedly text-only	Single account	Unverified
Oct 15	Post-outage endpoint passes a reasoning probe at ~180 t/s	Single account, N=4	Model identity unknown
Oct 15–16	Pro "in testing for weeks"	Two accounts	Unverified

The first signal came from @teortaxesTex on September 9. They wrote that V4.1 Pro "is in the works" and read it as confirmation that DeepSeek had "solved architectural issues of V4 family, as they committed to do in the V4 paper." That is an interpretation, not a disclosure.

The same day, @LuminaBench reported that DeepSeek would "route all V4 Pro traffic to V4.1 Flash until the new V4.1 Pro model launches." DeepSeek's own V4.1 Flash announcement used nearly the same wording, according to secondary write-ups that quote it. Then the company backtracked. API users received a notice, discussed on r/LLM, saying V4 Pro service would continue after September 14 "with the billing method unchanged." This article calls that episode the Reroute Reversal.

The most concrete artifact came on September 27. @LuminaBench posted that the slug "deepseek-v4.1-pro" appeared in "per account early access, deliberately hidden from the public model picker."

Source: @LuminaBench

Per-Account Early Access is a gated rollout pattern in which a model slug is enabled for selected accounts but left out of the public model list. If the screenshot is genuine, V4.1 Pro was running on DeepSeek's infrastructure almost three weeks before this article was written.

On October 15, after another service outage, @teortaxesTex tested the returning endpoint. They reported that it passed a known trick-question probe "with the best results this side of Claude," reproducible across 4 runs, at roughly 180 t/s. V4-Pro-0813 and V4.1 Flash both reportedly failed the same probe. The tester was explicit about the limits: "I don't know if this is a new model."

Source: @teortaxesTex

Why This Matters: The Flash-Over-Pro Inversion

DeepSeek's lineup is currently upside down. The newest small model is reported to beat the older large one. Users on r/LLM summarized DeepSeek's messaging as claiming that "V4.1-Flash is better than V4-Pro." A widely shared r/DeepSeek post title quotes the line "V4.1 Flash has comprehensively surpassed V4 Pro across all key metrics." @ItsmeAjayKV put it bluntly: "Your last flash model already beat previous Pro."

The Flash-Over-Pro Inversion is the state in which a vendor's newest small-tier model outperforms its previous flagship, which leaves the flagship slot effectively empty until the next Pro ships. That gap has practical consequences. Teams on V4 Pro are paying a premium for a model the vendor itself describes as surpassed.

The pricing history makes this worse. According to the r/LLM thread, V4 Pro's price "was raised substantially in August after the first 75% permanent price cut." One release explainer lists V4 Pro at $1.32 / $3.96 per 1M tokens at peak. A separate release tracker lists the V4 line at $0.66 / $1.98, exactly half. That may reflect off-peak versus peak rates, but neither source says so.

The inversion also explains the impatience. A Reddit thread titled "Where is v4.1 Pro?" drew guesses like "Tomorrow" and "Release_date→∞." The most useful reply was sober: "no one here works at deepseek… everything else are guesses." Another r/DeepSeek post already asks whether V4.1 Pro is "outdated before it even ships."

The V4.1 Flash Blueprint

DeepSeek called V4.1 Flash "the smallest model in our new architecture family, with native visual understanding." "Smallest" implies at least one larger sibling, and "family" implies shared design. So the best available evidence about Pro's architecture comes from Flash.

Model	Total params	Active params	Context	Vision	License
DeepSeek V4 Pro	1.6T	49B	Not stated in sources reviewed	Added later	MIT
DeepSeek V4 Flash	284B	13B	Not stated in sources reviewed	Experimental vision variant later	Open-weight preview
DeepSeek V4.1 Flash	552B	8B input / 16B output	1M tokens	Native image input	MIT
DeepSeek V4.1 Pro	Unknown	Unknown	Unknown	Reportedly not in first checkpoint	Unknown

The V4 figures come from the April 2026 V4 Preview announcement, reposted on Threads: "DeepSeek-V4-Pro: 1.6T total / 49B active params" and "DeepSeek-V4-Flash: 284B total / 13B active params." The V4.1 Flash figures come from release write-ups based on DeepSeek's model card.

Three design features stand out.

Asymmetric Active Parameters is the V4.1 Flash design in which the model activates a different number of parameters during prefill (8B, on input) than during decode (16B, on output). Public descriptions call it a causal encoder-decoder. If Pro inherits it, @ItsmeAjayKV argues it "is going to be faster than last pro for sure."

Engram Memory is the large memory component that release write-ups list among V4.1 Flash's core architectural pieces. DeepSeek has not published how it scales.

The 1M-token context window is confirmed for Flash. It is not confirmed for Pro.

At 8B active parameters on input, V4.1 Flash runs about one-sixth of V4 Pro's 49B active parameters per token, yet DeepSeek's own messaging says it surpasses V4 Pro.

What We Can Reasonably Expect

Everything in this section is inference, and each claim should be read with that in mind.

Size. @MiaAI_lab predicts V4.1 Pro will be "at least 2.6T params." No source supports that number. @ItsmeAjayKV claims the current V4-Pro-0813 checkpoint is 1.7T and that V5 "will be 2T parameters." The 1.7T figure conflicts with the official 1.6T, so all three numbers should be treated as unverified.

Vision. According to @ItsmeAjayKV, the initial Pro checkpoint will reportedly ship "without vision support," as V4.0 did, with vision arriving later. That would be odd, since V4.1 Flash had native vision on day one. The claim comes from one account with no attached evidence.

Agent focus. @teortaxesTex speculated that Pro might be "further trained for DSH and agent teams," possibly shipping alongside "DSH 0.2." Agent Teams here means multi-agent coordination workloads. One widely shared tracker analysis independently suggests swarm coordination, not raw scale, may be what is holding Pro back. That explanation also comes from a single source.

Timing. Release-timing guesses have repeatedly missed. @ItsmeAjayKV said on September 28 that Pro was coming "within next two weeks." That window passed. Their latest estimate is "October second half - November first half." The V4 generation's precedent, according to one release explainer, was 13 days from Flash (July 31) to Pro GA (August 13). V4.1 Flash shipped on September 10, so V4.1 Pro has already taken well over twice that gap.

On the limited evidence so far, DeepSeek V4.1 Pro appears to be in gated testing on DeepSeek's own infrastructure. No source has yet tied a benchmark, a price, or a verified parameter count to it.

DeepSeek V4.1 Pro vs Gemini 4 Argon: What the Reports Show

Gemini 4 Argon is the competitor most often named next to V4.1 Pro. A Reddit post titled "DeepSeek V4.1 Pro vs Gemini 4 Argon Same Prompt" circulates in r/DeepSeek and r/LLM recommendation lists. Its contents could not be verified, and V4.1 Pro has no public endpoint for anyone to reproduce it. @LuminaBench also pairs Pro with Kimi K3.1, which is likewise reportedly "in testing for a good while."

• Availability. V4.1 Pro has no public endpoint, only the reported per-account slug. Gemini 4 Argon became generally available on the paid Gemini API on October 13 as gemini-4-argon, according to an October 13 status roundup.
• Pricing. V4.1 Pro: unverified, no public number yet. Gemini 4 Argon is reported at $2 / $10 per 1M tokens until November 30, then $4 / $20 from December 1. The V4 Pro baseline is $1.32 / $3.96 at peak.
• Weights and license. V4.1 Pro is unverified, though V4 Pro and V4.1 Flash both set an MIT precedent. Argon requires a paid API project, and no open-weights release has been reported.
• Benchmarks. Unverified, with no public number from either lab yet.
• Head-to-head. One same-prompt Reddit post, not independently verified.

What We Know vs. What We Don't

What we know:

• DeepSeek named V4.1 Pro in writing on September 10: V4 Pro requests would be handled "until V4.1-Pro launches."
• DeepSeek calls V4.1 Flash "the smallest model in our new architecture family," which makes Pro a larger sibling.
• The V4 Pro reroute was cancelled. V4 Pro continues past September 14 with billing unchanged, per the notice API users received.
• The baseline is V4 Pro at 1.6T total / 49B active and V4 Flash at 284B / 13B.
• V4.1 Flash shipped September 10 under MIT: 552B total, 8B/16B active, 1M context, native image input.
• Polymarket priced the next DeepSeek Pro at 16% by October 31 and 31% by November 30, as of October 16.

What we don't know:

• The release date. None has been announced.
• The parameter count. Guesses run from 1.7T to "at least 2.6T," and none is sourced.
• Whether Asymmetric Active Parameters carry over from Flash.
• Whether vision ships on day one.
• Pricing and license.
• Benchmarks, and whether the October 15 endpoint running at ~180 t/s was V4.1 Pro at all.

How to Evaluate It Yourself

The Flash-Over-Pro Inversion changes what to measure. The key question is whether V4.1 Pro beats V4.1 Flash by enough to justify a Pro-tier price. Beating V4 Pro is not enough.

1. Baseline on Flash now. Build your eval harness against V4.1 Flash today. A comparable endpoint such as DeepSeek-V4.1-Flash gives you the same-family reference point you will need on launch day.
2. Add a reasoning trap set. The October 15 probe separated models that V4-Pro-0813 and V4.1 Flash both failed. Include adversarial prompts of that kind, not just coding tasks.
3. Measure throughput separately for prefill and decode. If Pro uses asymmetric activation, prompt-heavy and generation-heavy workloads may scale differently. A single tokens-per-second figure like "~180 t/s" will hide that.
4. Don't migrate off V4 Pro on rumor. DeepSeek has already reversed one deprecation plan. Pin your current model ID until a dated changelog entry exists.

The Week Ahead

Three signals matter. First, watch DeepSeek's API changelog and Hugging Face organization for a model card, the only source that will settle size and license. Second, check whether the deepseek-v4.1-pro slug appears in the public model list, which would be the end of Per-Account Early Access. Third, follow the Polymarket odds: a jump from 16% before October 31 would usually mean insiders see something the public does not. Until then, run your own evals on V4.1 Flash, re-test with the reasoning probe, and pin V4 Pro.

Try related models on Kie.ai: Gemini 4 Argon, Claude Sonnet 5.5 and Claude Haiku 5.5.