whatisgithub

What is llm-d?

pacoxu/llm-d — explained in plain English

Analysis updated 2026-07-17 · repo last pushed 2025-05-21

Audience · ops devopsComplexity · 4/5StaleSetup · hard

In one sentence

llm-d is a distributed inference stack for serving large language models at scale on Kubernetes, built on vLLM with smart request routing, prefill-decode separation, and tiered caching to optimize production LLM deployments.

Mindmap

mindmap
  root((repo))
    What it does
      Serves LLMs at scale
      Smart request routing
      Prefill decode separation
      Tiered caching
    Tech stack
      Kubernetes
      vLLM
      Inference Gateway
      Multi hardware support
    Use cases
      Customer support at scale
      Low latency LLM serving
      Production AI apps
    Audience
      Platform engineers
      ML engineering teams
    Notable backers
      Google
      NVIDIA
      IBM Research
      Red Hat

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Serve LLMs in production on Kubernetes with intelligent traffic routing and caching.

USE CASE 2

Run a customer-facing AI support tool with guaranteed low latency across many concurrent users.

USE CASE 3

Optimize LLM inference by separating prompt processing and answer generation across independent instances.

What is it built with?

KubernetesvLLMGoInference Gateway

How does it compare?

pacoxu/llm-d0verflowme/alarm-clock0xhassaan/nn-from-scratch
Stars0
LanguageCSSPython
Last pushed2025-05-212022-10-03
MaintenanceStaleDormant
Setup difficultyhardeasymoderate
Complexity4/52/54/5
Audienceops devopsvibe coderdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Requires a Kubernetes cluster with hardware accelerators (GPUs) and familiarity with distributed inference concepts, the README points to a separate deployer tool and quickstart guide.

The explanation does not mention a specific license, so the licensing terms are unknown.

So what is it?

llm-d helps you serve large language models at scale, on Kubernetes, without having to build the infrastructure from scratch. If your team is deploying LLMs and needs them to handle real production traffic efficiently, this project gives you a pre-built path to get there. At its core, it is a distributed inference stack built on top of vLLM, Kubernetes, and an Inference Gateway component. It tackles three main performance problems. First, it routes incoming requests intelligently, using a scheduler that is aware of things like cache state and service-level agreements to pick the best server for each request. Second, it separates the "prefill" stage (processing the prompt) from the "decode" stage (generating the answer), running them on independent instances so each can be optimized independently. Third, it manages a tiered cache of the intermediate computations LLMs produce, storing them locally or across instances to avoid redundant work. The target user is a platform or ML engineering team that needs to run LLMs for a customer-facing application. For example, if you are building an AI-powered customer support tool and need to guarantee low latency across hundreds of concurrent conversations, this framework manages the traffic routing and compute distribution to make that possible. It is built to work across different hardware accelerators, so you are not locked into a specific chip vendor. The project was launched by a coalition of major players including Google, NVIDIA, IBM Research, and Red Hat. It is designed to be modular, meaning teams can swap in their own scheduling logic or caching backends. Some advanced features, like intelligent autoscaling based on traffic patterns and hardware capacity, are noted as planned or in progress. The README does not go deep into the operational requirements for getting it running, but points to a deployer tool and quickstart guide for installation.

Copy-paste prompts

Prompt 1
I need to serve a large language model on Kubernetes for a production app with hundreds of concurrent users. Help me evaluate whether llm-d is the right fit and walk through the quickstart deployment steps.
Prompt 2
I want to understand how llm-d separates the prefill and decode stages of LLM inference. Write a simple diagram or explanation of the request flow from Inference Gateway to vLLM instances.
Prompt 3
Help me design a custom scheduling plugin for llm-d that prioritizes requests based on tenant-specific SLAs and current cache state across the distributed inference pool.
Prompt 4
I am comparing llm-d to running plain vLLM on Kubernetes. Create a comparison table covering routing, caching, prefill-decode separation, and hardware portability.

Frequently asked questions

What is llm-d?

llm-d is a distributed inference stack for serving large language models at scale on Kubernetes, built on vLLM with smart request routing, prefill-decode separation, and tiered caching to optimize production LLM deployments.

Is llm-d actively maintained?

Stale — no commits in 1-2 years (last push 2025-05-21).

What license does llm-d use?

The explanation does not mention a specific license, so the licensing terms are unknown.

How hard is llm-d to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is llm-d for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.