#5252nd of 71 in Model serving

llm-d

Kubernetes stack for distributed LLM inference on top of vLLM and SGLang

Stars
5.2k
License
Apache-2.0
Last commit
Nov 2026
Last release
Oct 2026
Language
Python
Stars, last 29 weeks+2,214
22 Apr 2026: 3,023 stars29 Apr 2026: 3,072 stars6 May 2026: 3,114 stars13 May 2026: 3,148 stars20 May 2026: 3,190 stars27 May 2026: 3,235 stars3 Jun 2026: 3,260 stars10 Jun 2026: 3,307 stars17 Jun 2026: 3,359 stars24 Jun 2026: 3,407 stars1 Jul 2026: 3,621 stars8 Jul 2026: 3,722 stars15 Jul 2026: 3,783 stars22 Jul 2026: 3,831 stars29 Jul 2026: 3,888 stars5 Aug 2026: 3,957 stars12 Aug 2026: 3,998 stars19 Aug 2026: 4,047 stars26 Aug 2026: 4,148 stars2 Sept 2026: 4,374 stars9 Sept 2026: 4,457 stars16 Sept 2026: 4,552 stars23 Sept 2026: 4,630 stars30 Sept 2026: 4,686 stars7 Oct 2026: 4,764 stars14 Oct 2026: 4,827 stars21 Oct 2026: 4,935 stars28 Oct 2026: 5,075 stars4 Nov 2026: 5,149 stars11 Nov 2026: 5,237 stars

3,023 on 22 Apr 20265,237 on 11 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

llm-d sits above model servers such as vLLM and SGLang and adds prefix-cache and load-aware routing, tiered KV-cache offload to CPU or disk, and prefill/decode disaggregation with wide expert-parallelism. It also covers multi-tenant flow control, session-aware routing for agents, OpenAI-compatible batch APIs and SLO-aware autoscaling. It deploys through benchmarked Helm-chart guides and is a CNCF sandbox project.

Who it is for: Platform teams running multi-GPU LLM inference on Kubernetes in production

Strengths

  • Prefix-cache-aware routing reported at 3x output throughput versus round-robin on Llama 3.1 70B
  • Supports NVIDIA, AMD and Intel GPUs and Google TPUs, with vLLM and SGLang backends
  • Prefill/decode disaggregation and tiered KV offload for large models like gpt-oss-120b
  • Tested Helm-chart guides with reproducible benchmarks published on Prism

Weaknesses

  • Requires a Kubernetes cluster; not a single-node or laptop server
  • Needs a separate model server (vLLM or SGLang) underneath
  • Predicted-latency scheduling is described as experimental in the README
  • Many components (router, flow control, KV indexing) add operational overhead for small deployments

What it needs

  • GPU required
  • Docker
  • Needs Kubernetes, vLLM or SGLang, Helm
  • Models: DeepSeek-V4, Kimi K3, gpt-oss-120b, Llama 3.3 70B, Llama 3.1 70B

What changed

  1. v1.0.0 ↗ (opens in a new tab)Security fix

    “Revise security vulnerability reporting methods by @davidgs in https://github.com/llm-d/llm-d/pull/2692”

From the release notes. No flag means the note does not say so, not that the upgrade is safe.

Also in Model serving

See all 71
Also in Model serving
RankProjectScore
1llama.cppC/C++ inference engine for GGUF LLMs and VLMs with an OpenAI-compatible server134.3k starsMIT94 out of 100
2OllamaLocal model runner with CLI and REST API for open-weight LLMs186.8k starsMITknown advisory in latest version92 out of 100
3LocalAISelf-hosted inference server with OpenAI-compatible API and pluggable backends50.3k starsMIT91 out of 100
#4vLLMInference engine serving LLMs with PagedAttention and an OpenAI-compatible API96.8k starsApache-2.088 out of 100
#5strataRuns a 125B-parameter MoE model on one consumer GPU plus system RAM43.4k stars+20,534 (+90%) in 30 daysMIT88 out of 100