DeepSeek open-sources DeepInfer, the inference framework behind its production services
SiliconANGLE Duncan Riley ● Covered by 9 sources
DeepSeek open-sourced the software that runs its AI serving system. It’s built to cut the cost of serving huge models, and the company says one cluster now handles 155 trillion tokens a day.
Based on reporting by SiliconANGLE, Duncan Riley — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
DeepSeek has put the software behind its own production inference stack on GitHub. The framework, called DeepInfer, is the engine that helps serve the company’s models at scale, and that problem is exactly how DeepSeek frames it: how do you reach a huge audience without making every request ruinously expensive?
The company says one cluster already serves 155 trillion tokens a day. It also says off-peak revenue works out to $38 per graphics processing unit per hour. Those numbers give the release a sharper edge than a normal open-source drop. This is not a toy repo. It is the plumbing for a live service.
For now, DeepInfer only supports DeepSeek-V4.1-Flash, and by default it loads the updated 1017 version DeepSeek shipped over the weekend. It runs on Nvidia’s SM100 Blackwell chips and on Huawei’s Ascend 950 neural processing units, but not on Hopper or other older Nvidia architectures. Two reproducibility features are Nvidia-only, and all of the benchmark numbers DeepSeek published were measured on Nvidia hardware too.
The framework leans on a couple of tricks to save compute. One, called DSpark, uses a draft model to propose five tokens at a time, then a confidence head decides which ones the main model will keep. DeepSeek says that cuts the number of draft tokens checked per step by about 30% and lifts throughput by 4% to 7% at its production load. Another method nearly halves total prefill work by running only the last 128 tokens of each prompt through decoder layers.
DeepSeek still hasn’t released the key-value cache management and load-balancing code. The company says those parts are tightly bound to internal infrastructure, though it does explain them in a blog post on Zhihu. Splitting prefill and decode across separate machines is also left to operators, and DeepSeek notes that most of the engine work for that is already in place. The smallest setup it calls efficient uses 64 GPUs for prefill and another 64 for decoding.
This is also a partial return to a job DeepSeek said was too much for its small research team back in April 2025, when it described the software as an early fork of vLLM built around its cluster tools. The new README says vLLM was the original foundation, and DeepInfer also uses libraries DeepSeek had already released, including FlashMLA, DeepGEMM and DeepEP. The companion deepseek-recipe library translates requests into token sequences using the same logic as DeepSeek’s official API. Future model inference code will go into the same repository.
My take — AI-written commentary, not fact-checked reporting
This is the useful kind of open source: not a victory lap, but the messy machinery that actually keeps an AI service cheap enough to run. DeepSeek is also making a quiet point about where the real moat lives — in systems work, not just model weights. That’s the part everyone keeps forgetting while they argue about who released what first.
Read more about this at: SiliconANGLE
Related stories
DeepSeek Upgrades DeepSeek-V4-Flash-0731 with Major Agentic and Coding Gains
MarkTechPost · 2 months ago ·
55
DeepSeek increases prices for AI services by multiple times
Fortune ·
16
DeepSeek made its name with cheap AI models. Now it’s undercutting search API rivals, too.
The New Stack · 1 day ago ·
8