DeepSeek's own official account, 深度求索 — the company's Chinese name, run as its community/support channel — confirmed today what several independent sightings had already described, relayed in a screenshot posted by the account @MaxForAI: "DeepSeek V4.1 Flash's interim version has entered internal testing, feel free to try it," followed by the identical technical details third-party accounts had already reported — new architecture, native multimodal support, "more capable, faster, and lower cost" — and a request for feedback via a linked survey form. Chinese tech outlets covering the same test report, secondhand, that the feedback DeepSeek is specifically soliciting centers on one question: whether this Flash-tier model can substitute for V4-Pro entirely — meaning the goal isn't just a cheaper model, but Pro-level capability at Flash's cost and speed. That's not confirmed by DeepSeek's own post directly, but it would explain why a company iterates on its budget tier with a "new architecture" claim rather than its flagship. The model is reachable by keeping the same API base URL and setting the model name to deepseek-v4.1-flash-expires-on-0910, priced the same as the current deepseek-v4-flash tier, capped at 20 concurrent requests per account.
Third-party sightings and DeepSeek's own account now agree, detail for detail
Before DeepSeek's own confirmation surfaced, at least three independent accounts had already described the identical technical specifics — the exact model string, the "expires-on-0910" suffix, and the instruction to keep the existing base URL and just change the model name — which was already a meaningfully stronger signal than a single unverified post. DeepSeek's own community-account post matches those third-party reports point for point: same model string, same pricing note, same 20-concurrent-request cap, plus the "new architecture" and "native multimodal support" language. That agreement is reassuring on the facts, but it doesn't change what's still missing: no pricing has actually changed from the current deepseek-v4-flash tier, so any "cheaper to run" claim has to come from doing a given task in fewer tokens or fewer calls, not from a headline price cut — a real efficiency claim, but a different one than "cheaper" suggests on its own.
An official beta, not an official launch
A model ID with a hard-coded expiration date, distributed through a community account with a feedback survey attached, is still not how DeepSeek normally announces a product. Compare this to DeepSeek's own V4-Pro launch last month, which arrived via a post from DeepSeek's main account, came with a full benchmark table against named rivals, and gave the new checkpoint a permanent model name that existing integrations didn't need to change to pick up. Today's confirmation has none of that: no benchmark table, no permanent name, and an explicit two-day test window. DeepSeek is officially confirming a beta, not officially launching a model — a real distinction, not a technicality, since everything about how this is being distributed (temporary ID, capped concurrency, a survey asking testers whether it can replace the Pro tier) says DeepSeek itself doesn't yet consider this checkpoint finished.
If "native multimodal" holds up, that's the actual story
DeepSeek's V4 line, as this blog covered at its Pro launch, has competed primarily on agentic coding and reasoning benchmarks against Kimi K3, Claude Fable 5, and Claude Opus 4.8 — a text-and-code competitive set. Native multimodal support would be a genuine architectural shift for that line, not an incremental update, and it would put DeepSeek in more direct competition with the vision-capable frontier models this blog has tracked all month. That's exactly why it's worth treating as an interesting claim to verify rather than a confirmed capability: "native multimodal support" attached to a two-day beta test with a feedback survey, and zero benchmark numbers attached from DeepSeek or anyone else, is not yet the same thing as a shipped, evaluated capability.
What to expect next
- Watch whether the endpoint actually disappears on September 10, as named. If it does, that confirms this stayed a bounded test; if DeepSeek extends it or converts it into a permanent model name, that's the tell that testing went well.
- Watch for the eventual official launch post and benchmark table. DeepSeek's V4-Pro launch set the template — a main-account post with a full comparison table against named rivals; that's the actual test of whether V4.1 Flash's claims hold up, not today's beta confirmation.
- Watch for independent benchmark results before crediting "faster," "more capable," or "cheaper." All three claims currently rest on DeepSeek's own beta-announcement language, not on any measured comparison from DeepSeek or an outside evaluator.
- Watch whether the survey question reported secondhand — can Flash replace Pro entirely — gets answered explicitly in whatever DeepSeek says when the test period ends, since that's the more consequential claim than any individual benchmark score.