Open-source LLM inference, serving and optimisation

Inference tooling decides what a model costs to run and how fast it answers. These projects cover serving engines, batching, quantisation and the memory tricks that make a model fit hardware you already own.

Inference is where AI budgets are actually spent. Training makes the headlines; serving makes the invoice — and a factor-of-three difference in throughput between two engines running the same weights is routine, not exceptional.

The projects here sit at different points on that curve: raw engines, routing and batching layers, and memory optimisations that let a larger model fit on smaller hardware. Each description says which of those it is, because mixing two layers that both want to own scheduling is the most common way this stack goes wrong.

Projects in this topic

18 analysed projects match this topic.

LLM and Claude Tools
Featured

Developer-first llm inference layer for macos

Skip weeks of custom work by starting from a working llm inference foundation.

llm inferencemacoscontinuous batching
Beginner · Developer library
TOOL-66275View details

Questions people ask

What is the difference between an inference engine and a model server?
The engine runs the forward pass efficiently on your hardware. The server puts an API, queueing, batching and authentication in front of it. Some projects do both; combining two that both do both usually costs you throughput.
Does quantisation hurt quality?
Moderate quantisation costs little on most tasks and a lot on a few — long-form reasoning and code are the sensitive ones. Test on your own prompts before deciding; benchmark averages hide exactly the cases you care about.
Where does the biggest speed-up usually come from?
Batching and cache reuse, not a faster GPU. Two identical deployments can differ several-fold on the scheduling layer alone.

Related collections

All collections

Other topics

Updated: 2026-08-17