DeepSeek open-sources DeepInfer, but developers still need key serving components
The framework supports DeepSeek-V4.1-Flash and exposes its decoding and scheduling techniques. The public release stops short of a complete online service.
Loading page…
The framework supports DeepSeek-V4.1-Flash and exposes its decoding and scheduling techniques. The public release stops short of a complete online service.
Listen to this story
DeepSeek’s Apache 2.0 release gives developers access to the inference engine behind its production services, including kernels, runtime code and distributed-computing tools. It is not a turnkey serving stack: users must supply KV caching, infrastructure to separate prefill from decoding, and load balancing. That makes DeepInfer useful for examining and adapting DeepSeek’s optimizations, but adopting it for production still requires substantial serving infrastructure; support is also limited to one listed model and specific accelerator families.
DeepInfer lists only DeepSeek-V4.1-Flash, and supports NVIDIA SM100 GPUs or Huawei Ascend 950 NPUs.
DeepSeek’s benchmark configuration uses four SM100 GPUs for prefill and 64 for decoding, with a repository script to reproduce the tests.
DSpark uses draft tokens and confidence estimates; variable-length drafting is configurable and defaults to a maximum of five tokens.
DeepSeek released DeepInfer on October 20, 2026, opening the inference engine it says powers its large-scale production services. The Apache 2.0 release lets developers run DeepSeek-V4.1-Flash offline and inspect its optimization techniques. But the DeepInfer repository leaves out several components that DeepSeek says are necessary for a complete inference service.
In its launch post, DeepSeek described the release as a way to help the community reduce computing costs and energy use.
The release includes optimized computing kernels, the model runtime and sampling code, plus tools for spreading work across processors. Its supported-model list contains one entry: DeepSeek-V4.1-Flash.
Developers building a complete service still need a key-value, or KV, cache system; infrastructure that separates input processing from output generation; and load balancing across parallel copies of the model. DeepSeek lists all three as outside this release.
One central technique is DSpark, which DeepSeek describes as accelerating decoding with draft tokens—proposed pieces of output—and confidence estimates that schedule verification. Developers can enable variable-length drafting and set the maximum draft length, which defaults to five.
Another technique reduces decoder input-processing work by replaying only a bounded suffix. The default V4.1 settings retain 140 tokens, enough to cover the sliding attention window plus the maximum backtracking length.
DeepInfer also overlaps CPU batch scheduling with accelerator execution, enabled by default. The repository credits vLLM as its main original foundation, with additional inspiration from SGLang and TensorRT-LLM.
Supported hardware is limited to NVIDIA SM100 GPUs and Huawei Ascend 950 neural processing units. Builds require Linux, GCC 13 or later and Python 3.12, plus CUDA 13 for NVIDIA or CANN 9.2 for Ascend.
DeepSeek’s published benchmarks use four SM100 GPUs for prefill, or input processing, and 64 for decoding, or output generation. Each runs within one scale-up domain. The repository supplies a script for reproducing the tests.
For an initial offline run, the example downloads DeepSeek-V4.1-Flash-1017 into the Hugging Face cache. Developers can instead point it to a local copy through an environment variable.
Story updates
deepseek posted way more alpha on their zhihu page, if you only read twitter you are reading the laowai approved stuff "Based on this framework, we have implemented a high-throughput, low-latency large-scale inference service for DeepSeek V4.1 Flash. Currently, the service throughput of a single cluster is 155 trillion tokens/day, and the overall revenue is $38 per card per hour (based on off-peak prices)." it costs roughtly $5-10 per gpu hour so depseek is claiming 80% serving margin at THEIR prices lololololol
Loading discussion...
Join the conversation
Explain when partial access is useful enough to justify the extra work.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.