DeepSeek V4.1-Flash brings native image understanding to an open-weight reasoning model. For enterprises, it opens a useful evaluation question: can one model handle visual evidence and complex text at an acceptable cost per verified result?
All Model Families →
Released on 10 September 2026, V4.1-Flash is a multimodal mixture-of-experts model. DeepSeek describes a causal encoder–decoder with 8B active parameters for input and 16B for output. Its launch reports lower KV-cache memory requirements than the previous generation. That is a claim about inference memory, not a promise that your application runs four times faster. DeepSeek launch announcement.
The practical opportunity is a document workflow that needs both the words and the picture: a chart in a report, a screenshot attached to a support case, or a diagram alongside a maintenance note. The model can propose an interpretation; the application still needs to verify important values against the original evidence.
Provider-published specifications as of 19 September 2026, not figures we measured. Model families move quickly — check the provider's own documentation before committing to a number.
Sources: official model card and licence; current API specifications. The backbone count is the model-card figure, not a hardware-sizing estimate.
USD per million input tokens · Peak rate · Linear scale from 0 to $1.50
Same provider and token category. Cache hits and off-peak traffic have separate rates. This is a price comparison, not a quality or speed benchmark.
Source: DeepSeek pricing. Checked 19 September 2026. Provider-reported, not independently measured by QQuantum.ai.
USD per million output tokens · Peak rate · Linear scale from 0 to $4.00
Compare complete token usage, including reasoning and retries. A lower rate does not establish a lower cost per accepted result.
Source: DeepSeek pricing. Checked 19 September 2026. Provider-reported, not independently measured by QQuantum.ai.
Illustrative calculation: a batch totalling 10 million uncached input tokens and 1 million output tokens costs $4.20 on Flash or $17.16 on Pro at these peak rates. Calculation: input millions × input rate + output millions × output rate. This assumes equal token counts; it excludes tools, retries, infrastructure, tax and human review. Off-peak prices are half the peak rates. Pricing and current peak-hour schedule.
For a real decision, replay the same work on both models. Count rejected answers, additional reasoning, retries and manual corrections. A cheaper answer that takes longer to check can be the more expensive outcome. Our Jev model-router project applies this principle at request level: choose an eligible model, then verify the result.
DeepSeek recommends deepseek-flash. The old V4-Flash and V4-Flash-Vision-Exp aliases now resolve to V4.1-Flash. The current documentation also says V4 Pro remains available after 14 September, superseding the original launch plan to reroute it. Current API migration notice.
Treat an alias change as a model change: replay representative prompts, verify image handling and structured outputs, and compare the returned usage. API-format compatibility does not prove identical tool behaviour. Keep the previous approved route available until the acceptance criteria pass.
Self-hosting is a separate infrastructure project. Active parameters do not tell you how much memory the full deployment needs. Size weights, context cache, concurrency and the serving stack together. Confirm runtime support for this exact release before buying hardware.
Model provenance, provider jurisdiction and data flow are separate decisions. For a hosted service, review the actual processing locations, retention terms and contract. For self-hosting, inspect outbound connections, telemetry, tools and update mechanisms; hosting weights locally alone does not prove that the whole application is isolated.
Pin the model artefact, retain its licence, and evaluate behaviour on the topics your customers actually ask about. Our model supply-chain approach covers that review. If the organisation cannot approve the provider or operate the serving infrastructure, choose another eligible model before comparing scores.
No. The September release is V4.1-Flash. Current API documentation lists V4-Pro-0813 separately and says Pro remains available after 14 September.
The official model card describes image and text input with text output. This is visual understanding, not an image-generation service.
Start with a replay evaluation on your own tasks. Compare accepted results, response times, total spend and review effort before changing live traffic.
Bring representative documents or requests. We will scope an evaluation around quality, data constraints and cost per accepted result.
What we built, what stage it is at, and a link to the live thing wherever there is one.
yourOS is an operating system with an AI at its heart. You talk to it like a person, out loud or typed. It makes your calls, plans your days and works on your projects with a crew of agents, on your own private server. Our own product, built from the first commit; the waitlist is open.
Website, backend and app assets for Sonora, a free AI sound-therapy app on iOS and Android published by Cognitive AI.
Brand, website, prototype, apps on five platforms, the AI backend and the algorithm-intelligence pipeline for Podswap, a social growth engine that runs without a human in the loop.
In closed beta: Roxy, a private AI assistant with permanent memory running on infrastructure the user owns. Brand, site, product, backend and conversational design.
Live at coherence.com: brand identity generated with AI agents we directed, the motion system and website for the group behind Sonora, AboutAI, WakeUp and MudShadows. Agent work remains in build.
Live at domainbooth.com for DomainBooth, a premium domain brokerage: a new animated mark, every page redesigned and rebuilt with designed mobile layouts, and a custom CMS for its sales record, featured names, press and enquiries.
Apps, platforms and campaigns for these teams, long before the AI work. Every one is written up on the work page — what we did, and where our part ended.
