llm-d
Kubernetes-native distributed LLM inference: state-of-the-art throughput on any accelerator, with intelligent routing above vLLM and SGLang.
About
llm-d is a high-performance distributed inference serving stack for production Kubernetes deployments. The pitch is layered: model servers like vLLM and SGLang already run models efficiently on accelerators, and llm-d adds the orchestration above them, intelligent prefix-cache and load-aware request routing (including experimental latency-predicted scheduling), advanced KV-cache management with tiered prefix caching, and disaggregated serving, to squeeze maximum throughput and minimum latency out of real-world traffic.
It is a CNCF sandbox project founded by Red Hat, Google Cloud, IBM Research, CoreWeave, and NVIDIA, which explains the enterprise-grade posture: well-tested deployment guides ('well-lit paths'), real-world benchmarks, and broad accelerator support. At 4,800+ stars it is the serious answer when a single vLLM pod stops being enough. The cost of admission is Kubernetes itself: this is infrastructure for platform teams, not a pip install for your laptop.
What it can do
- Distributed inference orchestration on Kubernetes, above vLLM/SGLang
- Intelligent routing: prefix-cache-aware and load-aware balancing, latency-predicted scheduling
- Advanced KV-cache management with tiered prefix caching
- Disaggregated serving for prefill/decode separation
- Well-lit-path deployment guides and real-world benchmarks
- CNCF sandbox project backed by Red Hat, Google, IBM Research, CoreWeave, NVIDIA
Setup
- Provision a Kubernetes cluster with GPU/accelerator nodes.
- Follow a 'well-lit path' guide at llm-d.ai/docs for your model and hardware.
- Deploy the llm-d stack (it orchestrates vLLM/SGLang model servers underneath).
- Configure intelligent routing and prefix-cache policies for your traffic shape.
- Validate with the provided benchmarks before cutting over production traffic.
Prerequisites
A Kubernetes cluster with accelerator nodes; familiarity with vLLM or SGLang concepts; production traffic worth optimizing.
Use cases
Works with
Trust score — 8/10
Scored 8/10 (verified tier, metrics-v1). Evidence: 4,833 GitHub stars (GitHub API), Apache-2.0, pushed Oct 15 2026; the README documents the routing, KV-cache, and disaggregation themes and the CNCF/founder backing; llm-d.ai corroborates the well-lit-path guides. Strengths: the credible k8s-native inference stack, serious institutional backing, honest scope above vLLM/SGLang. Docked for: (1) Kubernetes is the price of admission; (2) younger project, ecosystem still forming; (3) experimental scheduler features are not all production-proven. License: Apache-2.0.
★ 4,833 GitHub stars
How the trust score is built
Full methodology →- Adoption · stars/downloads, log-scaled vs peers
- 6.0/10
- Maintenance · recency, releases, issue load
- 10.0/10
- Openness · license + docs
- 10.0/10
- Manual review · sanity read + red-flag check
- 8.0/10
- · Adoption 6: starScore from 4,833 stars on llm-d/llm-d (log scale vs 298k peer max)
- · Maintenance 10: pushed 2026-10-15 (recency 10); CNCF sandbox with major founders
- · Openness 10: Apache-2.0 (0.7*10) + docs verified at llm-d.ai (0.3*10)
- · Manual 8: credible k8s-native inference stack corroborated by README and well-lit-path guides; docked: Kubernetes is the price of admission, some scheduler features experimental
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.