Ross ROSS = Recommend OSS · open-source software intelligence for agents

vllm-project/production-stack

vLLM’s reference system for K8S-native cluster-wide deployment with community-driven performance optimization observed · 2026-08-28

github.com/vllm-project/production-stack · homepage · Python · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

85/100

  • Activity 98
  • Release rhythm 94
  • Longevity 42
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 10.5
  • age_days: 589
  • days_rel: 40
  • days_push: 15
  • n_releases_24m: 23

Full methodology

Adoption not part of the score

2526 stars · 472 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

vLLM Production Stack is a reference implementation for deploying vLLM LLM inference at scale on Kubernetes, distributed via Helm charts. It adds a request router with KV-cache-aware, prefix-aware, and load-aware routing, plus KV cache offloading via LMCache and Prometheus-based monitoring.

Use cases

  • deploy vllm on kubernetes
  • scale llm inference across multiple gpu nodes
  • route llm requests with kv cache aware load balancing
  • share kv cache across vllm instances with lmcach
  • deploy openai-compatible llm api on aws or gcp
  • monitor vllm inference metrics with prometheus
  • set up disaggregated prefill for llm serving
  • enable tool calling for llama models in production

When to choose

  • you already use vLLM and need cluster-wide, multi-replica deployment on Kubernetes
  • you want smart request routing (prefix/KV-cache/load aware) across vLLM instances
  • you need KV cache offloading and sharing to improve throughput and fault tolerance
  • you want an OpenAI-compatible LLM endpoint with built-in monitoring and autoscaling

When to avoid

  • you only need a single vLLM instance on one machine without Kubernetes
  • you use a different inference engine like TGI, SGLang, or TensorRT-LLM
  • you cannot run a Kubernetes cluster or Helm
  • you need a fully managed LLM API rather than self-hosted serving

Facets

framework · maturity active

llm-inference deployment monitoring caching container-orchestration infrastructure-as-code api-framework benchmarking tracing large-language-models artificial-intelligence cloud-computing self-hosted microservices python cloud self-hosted vllm helm-chart kv-cache lmcache request-routing openai-compatible-api llm-serving inference-serving load-balancing prefix-caching devops containers kubernetes docker gpu linux

6 sources

Member repositories

RepositoryRoleHealth v2
vllm-project/production-stackmain85

For agents

markdown · JSON · MCP: product_card(name="vllm-project/production-stack")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem