#1111th of 37 in Model serving

lmcache

KV cache offloading and reuse layer for LLM serving engines

Stars
12.1k
License
Apache-2.0
Last commit
Oct 2026
Last release
Oct 2026
Language
Python
Stars, last 29 weeks+4,449
31 Mar 2026: 7,688 stars7 Apr 2026: 7,793 stars14 Apr 2026: 7,860 stars21 Apr 2026: 7,944 stars28 Apr 2026: 8,033 stars5 May 2026: 8,080 stars12 May 2026: 8,145 stars19 May 2026: 8,194 stars26 May 2026: 8,251 stars2 Jun 2026: 8,299 stars9 Jun 2026: 8,368 stars16 Jun 2026: 9,096 stars23 Jun 2026: 9,621 stars30 Jun 2026: 9,864 stars7 Jul 2026: 10,040 stars14 Jul 2026: 10,439 stars21 Jul 2026: 10,690 stars28 Jul 2026: 10,834 stars4 Aug 2026: 10,938 stars11 Aug 2026: 11,033 stars18 Aug 2026: 11,139 stars25 Aug 2026: 11,340 stars1 Sept 2026: 11,555 stars8 Sept 2026: 11,657 stars15 Sept 2026: 11,766 stars22 Sept 2026: 11,846 stars29 Sept 2026: 11,907 stars6 Oct 2026: 11,951 stars13 Oct 2026: 12,039 stars20 Oct 2026: 12,137 stars

7,688 on 31 Mar 202612,137 on 20 Oct 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

LMCache runs as a standalone daemon that stores LLM KV cache outside the inference engine, in tiers spanning CPU RAM, local disk and remote backends. Cached KV can be reused across requests, sessions and engine instances, which cuts repeated prefill and time-to-first-token on long-context, multi-turn and RAG workloads. It also supports non-prefix reuse via CacheBlend and prefill-to-decode KV transfer over NVLink, RDMA or TCP.

Who it is for: Engineers running LLM inference clusters who want to cut prefill cost

Strengths

  • Runs as a separate daemon, so KV cache survives inference engine crashes
  • Backends include CPU RAM, disk, Redis/Valkey, Mooncake, S3-compatible, NIXL and GDS
  • Non-prefix KV reuse at any prompt position through CacheBlend
  • Exposes KV-cache metrics such as request-level and token-level prefix hits

Weaknesses

  • Not a standalone server; it needs a supported serving engine in front
  • README gives no hardware requirements or supported-engine version list
  • Multi-node and PD disaggregation setups need external transports and storage
  • No Docker or compose files detected in the repository

What it needs

  • Docker
  • Needs Redis/Valkey (optional), Mooncake (optional), NIXL (optional), S3-compatible storage (optional)
  • Models: gpt-oss 20B/120B, multimodal models in vLLM V1

Also in Model serving

See all 37
Also in Model serving
RankProjectScore
1LocalAISelf-hosted inference server with OpenAI-compatible API and pluggable backends49.8k starsMIT83 out of 100
2llama.cppC/C++ inference engine serving GGUF models over an OpenAI-compatible API131.9k starsMIT81 out of 100
3OllamaLocal model runner with CLI and REST API for open-weight LLMs184.1k starsMIT80 out of 100
#4vLLMInference engine for Hugging Face LLMs with PagedAttention and continuous batching94.6k starsApache-2.077 out of 100
#5strataRuns a 125B-parameter MoE model on one consumer GPU plus system RAM29.5k starsMIT77 out of 100