pacoxu/llm-d — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2025-05-21
Serve LLMs in production on Kubernetes with intelligent traffic routing and caching.
Run a customer-facing AI support tool with guaranteed low latency across many concurrent users.
Optimize LLM inference by separating prompt processing and answer generation across independent instances.
| pacoxu/llm-d | 0verflowme/alarm-clock | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | — | — | 0 |
| Language | — | CSS | Python |
| Last pushed | 2025-05-21 | 2022-10-03 | — |
| Maintenance | Stale | Dormant | — |
| Setup difficulty | hard | easy | moderate |
| Complexity | 4/5 | 2/5 | 4/5 |
| Audience | ops devops | vibe coder | developer |
Figures from each repo's GitHub metadata at analysis time.
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.
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.
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.
Stale — no commits in 1-2 years (last push 2025-05-21).
The explanation does not mention a specific license, so the licensing terms are unknown.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
double-check against the repo, no cap.