Joined August 2014
I'm fortunate to have witnessed and contributed to @vllm_project's growth from a research project into one of the industry standards for LLM inference and the most popular open-source LLM inference engine. Today we announce @inferact, with a mission to solve inference and make it cheaper and faster. As model architectures evolve and hardware splinters across an ever-expanding landscape of accelerators, we're building the infrastructure layer that absorbs all that complexity so the world can focus on what to build, not how to run it.
Today, we're proud to announce @inferact, a startup founded by creators and core maintainers of @vllm_project, the most popular open-source LLM inference engine. Our mission is to grow vLLM as the world's AI inference engine and accelerate AI progress by making inference cheaper and faster. The Challenge Inference is not solved. It's getting harder. Models grow larger. New architectures proliferate: mixture-of-experts, multimodal, agentic. Every breakthrough demands new infrastructure. Meanwhile, hardware fragments: more accelerators, more programming models, and more combinations to optimize. The capability gap between models and the systems that serve them is widening. Left this way, the most capable models remain bottlenecked and with full scope of their capabilities accessible only to those who can build custom infrastructure. Close the gap, and we unlock new possibilities. And the problem is growing. Inference is shifting from a fraction of compute to the majority: test-time compute, RL training loops, synthetic data. We see a future where serving AI becomes effortless. Today, deploying a frontier model at scale requires a dedicated infrastructure team. Tomorrow, it should be as simple as spinning up a serverless database. The complexity doesn't disappear; it gets absorbed into the infrastructure we're building. Why Us vLLM sits at the intersection of models and hardware: a position that took years to build. When model vendors ship new architectures, they work with us to ensure day-zero support. When hardware vendors develop new silicon, they integrate with vLLM. When teams deploy at scale, they run vLLM, from frontier labs to hyperscalers to startups serving millions of users. Today, vLLM supports 500+ model architectures, runs on 200+ accelerator types, and powers inference at global scale. This ecosystem, built with 2,000+ contributors, is our foundation. We've been stewards of this engine since its first commit. We know it inside out. We deployed it at frontier scale—in research and in production. Open Source vLLM was built in the open. That's not changing. Inferact exists to supercharge vLLM adoption. The optimizations we develop flow back to the community. We plan to push vLLM's performance further, deepen support for emerging model architectures, and expand coverage across frontier hardware. The AI industry needs inference infrastructure that isn't locked behind proprietary walls. Join Us Through the open source community, we are fortunate to work with some of the best people we know. For @inferact, we're hiring engineers and researchers to work at the frontier of inference, where models meet hardware at scale. Come build with us. We're fortunate to be supported by investors who share our vision, including @a16z and @lightspeedvp who led our $150M seed, as well as @sequoia, @AltimeterCap, @Redpoint, @ZhenFund, The House Fund, @strikervp, @LaudeVentures, and @databricks. - @woosuk_k, @simon_mo_, @KaichaoYou, @rogerw0108, @istoica05 and the rest of the founding team
5
2
126
47,853
Great minds think alike! 😍
Great work! FWIW, vLLM is moving in the same direction. We've put a lot of work into isolating model-specific code, and it works really nicely now. We've also been considering moving more of the stack to Rust, and your work makes a strong case for it!
1
25
1,142
I wish more people can do some basic research before posting nonsense
5
30
2,343
Roger Wang retweeted
It's easy to make inference benchmarks look impressive with random inputs and idealized expert routing. The harder part is making those numbers hold up on real workloads. Our DeepSeek-V4.1-Flash benchmarks use real input distributions, realistic expert routing, and the same serving configurations validated on @SemiAnalysis_ AgentX. Fun fact: our results have been online since Oct. 20, even before DeepInfer's release. And we'll deliver even more speedups! Synthetic benchmarks have their place, but let's be clear about what they actually measure. Check out our blog for the full optimization story and benchmarking methodology!
Replying to @vllm_project
Scaled out with P/D disaggregation and Wide-EP on a GB300 NVL72 rack, vLLM serves V4.1-Flash on SemiAnalysis AgentX at 954K tokens/s per GPU with 196 tokens/s P90 per user, 7.9× our single-node result. Our engineering blog covers the work behind it: vllm.ai/blog/2026-10-23-deep…
6
20
99
5,745
Roger Wang retweeted
We wrote a blog post on how we achieved such great performance on DSV41-Flash. Our results are also verified in the @SemiAnalysis_ AgentX benchmark.
vLLM matches DeepInfer, DeepSeek's own engine for DeepSeek-V4.1-Flash, on DeepSeek's decode configuration across batch sizes 8 to 256, and does it at DEP32 against DeepInfer’s EP64DP64. DeepInfer was originally built on vLLM. By integrating DeepSeek's open-source kernels and extensively optimizing prefill and decode, vLLM now matches DeepInfer's performance curves.
7
13
90
4,600
One important difference in the benchmarking methodologies here is the dataset and the shape of the workload. We care much more about real agentic workloads than random inputs. It’s great that @SemiAnalysis_ provided a comprehensive AgentX platform with full transparency.
VLLM and SGLang both just said they match DeepSeek's new DeepInfer engine. Here's what you need to know. DeepSeek open-sourced DeepInfer on Oct 20 under Apache 2.0. It is the in-house inference engine behind DeepSeek-V4.1-Flash, and it supports NVIDIA GPUs and Huawei chips. It was originally built on vLLM. Now the two big open serving engines are claiming parity with it. vLLM posted first on Oct 25. It says it matches DeepInfer on DeepSeek's decode configuration across batch sizes 8 to 256. It does that at DEP32, against DeepInfer's EP64DP64. vLLM did it by integrating DeepSeek's open-source kernels and heavily optimizing prefill and decode. The work was led by the Inferact team, with help from NVIDIA and SemiAnalysis' AgentX benchmark. SGLang says it matches DeepInfer on both prefill and decode. It first brought in DeepSeek's Mega kernels (MegaMoE, MegaAttention, Mega-mHC, MegaGate), SWA bounded replay and Engram optimizations. Then it added more kernel fusions and breakable CUDA graphs for prefill. Everything is in SGLang main, with an end-to-end reproduction guide. SGLang also points out gaps in DeepInfer's release. It leaves out a KV cache system, prefill/decode disaggregation and load balancing. SGLang ships all three. Its team also says some prefill comparisons mix GB300 results with DeepInfer's published B300 numbers, and argues that makes a fair comparison hard. Key numbers: - vLLM decode: matches DeepInfer at batch sizes 8 to 256, using DEP32 vs EP64DP64 - vLLM on a GB300 NVL72 rack: 954K tokens/s per GPU, 196 tokens/s P90 per user, 7.9x its single-node result - SGLang prefill: up to 1.04x throughput on 4x GB300 and 4x B300 - SGLang decode: up to 7.4% more throughput on 64x GB300 The result is that DeepSeek's release set a performance bar, and the two main open engines reached it within days.
1
5
20
1,472
🚀🚀🚀The teams involved work tirelessly on this! Check it out!
vLLM matches DeepInfer, DeepSeek's own engine for DeepSeek-V4.1-Flash, on DeepSeek's decode configuration across batch sizes 8 to 256, and does it at DEP32 against DeepInfer’s EP64DP64. DeepInfer was originally built on vLLM. By integrating DeepSeek's open-source kernels and extensively optimizing prefill and decode, vLLM now matches DeepInfer's performance curves.
1
2
22
1,332
Own your intelligence
We just had a really tough inference bug that 4x parallel Opus 5.5 agents couldn't figure it out after more than 24 hours. Our Agent V's agent collaboration infra running 16 self-hosted Kimi K3 agents cracked it under 12 hours. Definitely a win for open intelligence!
17
1,235
Inferact & vLLM 🤝 MiniMax as always 🤗
2
23
931
Roger Wang retweeted
🎉 MiniMax M3.1 Flash from @MiniMax_AI has Day-0 support in vLLM! Built for multi-step automation, real-codebase engineering and visual reasoning—with native NVFP4 KV, NVFP4 MoE weights and DSpark speculative decoding in the serving stack. What the model can do, and the vLLM engineering that makes it practical to serve. 👇 Model: huggingface.co/MiniMaxAI/Min… 1/5
MiniMax M3.1 Flash weights are now public. 428B parameters total, 23B activated per token. Agentic performance: A generational leap in agentic tasks, coding, and cybersecurity — 76.2 on BankerToolBench, 73.7% on DeepSWE v1.1, 61.7 on OSWorld V2, 29.6 on Agents' Last Exam, and 82.2 on CyberGym. Efficient by design: MiniMax Sparse Attention and DSpark speculative decoding improve inference efficiency. Hugging Face: huggingface.co/MiniMaxAI/Min… ModelScope: modelscope.cn/models/MiniMax… API: platform.minimax.io M Plan: minimax.io/m-planMiniMax MCode for desktop: agent.minimax.io/download
17
35
5
197
11,334
Efficiency and quality, at scale
Today, we are announcing a strategic partnership with @MiniMax_AI to advance frontier production inference for open-source models. The Inferact Platform has served MiniMax M3.1 Flash in production since the day it launched. Requests through the MiniMax platform are routed to our stack alongside MiniMax’s own capacity, after we met MiniMax’s vendor verification requirements for accuracy and reliability. The Inferact Platform serves this agentic workload with guaranteed SLAs and auto-tunes the endpoint against live traffic, while MiniMax keeps control of how its model is served. Inferact also leads day-0 @vllm_project support for each MiniMax release, so the model serves at production quality the day the weights ship. The engineering from both efforts is upstreamed to vLLM. Thanks to the MiniMax team for the partnership. Read the full announcement: inferact.ai/news/minimax-par…
1
3
19
1,252
Roger Wang retweeted
Day-0 support for @Recursive_SI's Flint is here in vLLM! 🚀 40B parameters, just 2.5B active per token. Thanks to the small size, our custom NVFP4 kernels push it to 500 TPS on a single GB200, even at 100K context without speculative decoding. Both NVFP4 and BF16 are ready to run today! vllm.ai/blog/2026-10-21-flin…
Introducing Flint, @Recursive_SI’s first model: a fast local coding model built with our automated research system, the Eureka Machine. • Best-in-class fast local coding • Up to 2x faster than comparable models: 125+ tokens/sec on a MacBook Pro, 150+ on RTX Spark • Built from scratch in under 4 months Private, unmetered intelligence on your own machine. Open weights available now on @huggingface, run it locally on your favorite framework or try it for free on @opencode or @pidotdev.
15
23
2
142
8,360
Roger Wang retweeted
DeepInfer: the secret behind DeepSeek's 10-month inference payback It is claimed to be derived from vLLM, tuned for DeepSeek V4.1 Flash: 1. Draft verification sized by DSpark confidence 2. Zero-overhead scheduling: CPU runs a step ahead 3. Bounded replay: cheaper prefill 4. Wide EP + MegaMoE #DeepSeek #vLLM #DeepInfer #LLM #Inference #GPU #DSpark #MoE
1
2
159
When we say we're pushing the frontier of inference efficiency we REALLY mean it
🚨🚨🚨 vLLM is all you need to reproduce DeepSeek’s performance. With Wide-EP and EPLB, vLLM can match DeepInfer’s decode performance within 6% and generate $39/gpu/hr in revenue at DeepSeek’s off-peak pricing, at 200 P90 TPS on the AgentX workload. Specifically: • Under DeepSeek’s decode configuration (DeepSeek-V4.1-Flash, 131K context, nextn=3), vLLM on GB200 achieves throughput within 6% of DeepInfer’s published results across batch sizes 8–256. • On AgentX, vLLM pushes the Pareto frontier further on GB300, reaching up to 1M tokens/s/GPU and generating $38.96/gpu/hr in revenue at 196 P90 TPS, based on DeepSeek’s off-peak API pricing. • Also, vLLM extended low-latency kernel support for DeepSeek-V4.1-Flash, achieving up to 826 TPS per user on AgentX.
2
3
1
60
3,389
When @santinoramos_ asked our agent to scale up prefill
1
12
658
Beyond very big kernels
Our Kimi K3 result running @vllm_project TPU v7 reaches 391 tokens/s per user on @SemiAnalysis_ AgentX. This result uses our TPU megakernels in vLLM TorchTPU and holds up on real, long-context, production-level agentic workloads. The results are publicly viewable on InferenceX, and the megakernels are open source. 1/2
21
1,093
Roger Wang retweeted
Happy to work together with Physis-AI Infra team and bring the extremely low latency and high FPS physical AI serving experience to our community memebers. @rogerw0108 @90VuHwwuzNhhW3h
⚡️ Solid work from the Physis-AI Infra team. Together with Physis-AI, we’re introducing PhysisServe. PhysisServe advances autoregressive denoising serving via fine-grained stage pipelining, time-sharing and multi-stream joint scheduling, optimizing both single-stream output latency and multi-stream system efficiency in one inference system. PhysisServe’s core techniques are coming to vLLM-Omni, and our teams are working closely together to make it happen. Congrats on a strong debut. Excited for what we’ll build together! 👏
1
1
1
174
Learn from the best and keep pushing the boundaries of inference efficiency
Grateful to @deepseek_ai for releasing DeepInfer, initially built primarily on @vllm_project, under Apache 2.0 and crediting the open-source community! We've worked hard on DeepSeek V4.1 Flash inference efficiency and will keep improving with ideas from DeepInfer! Stay tuned 🙌
4
42
1,450
Roger Wang retweeted
It has been so much fun to work on this MiniMax model for the past weeks, and we have discovered so much surprise in a good way. 1. A few things that people thought are "dead ends" are getting their second lifes for agentic serving. 2. No more "I can only do this performance number on XXX hardware". It matters more if you can co-design the hardware <> engine <> serving stack all together and let them play well with your clusters' scale up/out network. 3. "Traditional" computation hardware matters as well. Your CPU, your RAM size, your NIC, your switch, etc. GPUs themselves solely wouldn't get you anything near your target. Lastly, vape hard when you vibe hard 🤘
Inferact is an API launch partner for MiniMax M3.1 Flash! 🎉 We're working with @MiniMax_AI on production inference for its latest model, built for multi-step automation, real-codebase engineering and visual reasoning. M3.1 Flash scored 29.6 on Agents’ Last Exam (ALE), alongside 72.5% on AutomationBench-AA and 73.67% on DeepSWE—capabilities that matter when agents need to plan work, use tools and carry tasks through. Our contribution is the serving stack: bringing our vLLM engineering and the Inferact Platform to the collaboration. Thanks to the MiniMax team for the partnership. Explore the model and API integration: platform.minimax.io/docs/gui…
5
5
30
2,151
I’ve been thinking more and more about this: should Inferact open a Toronto office? 🤔 No troll pls
47%Yes, no brainer
15%No, why would you?
38%Don't care show me result
73 votes • Final results
4
12
1,435
Inferact & vLLM 🤝 MiniMax
Inferact is an API launch partner for MiniMax M3.1 Flash! 🎉 We're working with @MiniMax_AI on production inference for its latest model, built for multi-step automation, real-codebase engineering and visual reasoning. M3.1 Flash scored 29.6 on Agents’ Last Exam (ALE), alongside 72.5% on AutomationBench-AA and 73.67% on DeepSWE—capabilities that matter when agents need to plan work, use tools and carry tasks through. Our contribution is the serving stack: bringing our vLLM engineering and the Inferact Platform to the collaboration. Thanks to the MiniMax team for the partnership. Explore the model and API integration: platform.minimax.io/docs/gui…
1
1
31
924