inference/research
deprecatedhigh · 0.87updated 2026-10-03

Text Generation Inference

cuda, rocm, xpu, npu-gaudi, cpu-avx512
Deprecated. Superseded or no longer accurate.

Fields

id
engines/text-generation-inference
Repo
huggingface/text-generation-inference
Languages
RustPythonC++CUDA
License
Apache-2.0
First release
2023
Design goal
throughput-firsthuggingface-ecosystem
Scheduling
continuous-batchingpaged-kvprefix-cache
Backends
cudarocmxpunpu-gaudicpu-avx512
Formats
safetensorsawqgptqmarlinfp8eetqbitsandbytes-nf4bitsandbytes-fp4
Notable features
Rust server plus a router for multi-model deploymentsOptimized architectures for modern models out of the box, with best-effort AutoModel fallback for everything elseOn-the-fly quantization with bitsandbytes, EETQ and fp8, plus 4-bit NF4/FP4 from bitsandbytesContainer targets for AMD, Gaudi, Intel and llama.cpp/TRT-LLM variants, and a SageMaker entrypointWas the default HF-hosted serving path and is still the reference most HF Inference Endpoints docs describe
Hardware caveats
ARCHIVED BY THE OWNER AND READ-ONLY. The GitHub API reports archived: true with the last push on 2026-03-21 and the final release v3.3.7 published 2025-12-19. It accepts no development, so it is a dead end for anything new. Note the archived flag and the README's 'maintenance mode' notice together mean both facts: the repo is read-only, and the project's own stated policy was already maintenance-only (minor bug fixes, documentation, lightweight tasks) before archivingNOT MERGED INTO vLLM - a widely repeated misconception. What was donated downstream is the pattern of optimised transformers model architectures that downstream engines reuse; the codebase itself was not absorbed. See notes for the README's exact wordingStill in production at Hugging Face, powering Hugging Chat and the Inference API/Endpoints, so 'deprecated' here means retired by maintainers, not unused in the worldIts quantization feature matrix predates the current generation of engines; what worked here may not reflect present-day kernelsBackend variety (AMD, Gaudi, Intel, SageMaker) existed mostly as Dockerfiles, with uneven depth behind each - a pattern that contributed to the maintenance burden
Best for
Reading how a production HF serving stack was put together, as a historical referenceExisting deployments that have not yet migrated off it
Avoid for
Any new deployment - it is archived and unmaintainedAnything needing current model architectures or current quantization kernelsNew feature work of any kind
Tracing support
basic
notes
Status deprecated and confidence deliberately moderate: the repo is ARCHIVED and read-only (archived flag true, last push 2026-03-21, final release v3.3.7 on 2025-12-19), so most capability claims are historical rather than current. CORRECTION TO A COMMON MISCONCEPTION, verified against the README on 2026-10-04: TGI was NOT merged into vLLM. It was retired. The README's own words are 'text-generation-inference is now in maintenance mode. Going forward, we will accept pull requests for minor bug fixes, documentation improvements and lightweight maintenance tasks', followed by an explanation that 'TGI has initiated the movement for optimized inference engines to rely on a transformers model architectures. This approach is now adopted by downstream inference engines, which we contribute to and recommend using going forward: vLLM, SGLang, as well as local engines with inter-compatibility such as llama.cpp or MLX.' The architectural idea - optimised transformers model architectures shared with downstream engines - was donated rather than the codebase. So there is no TGI code inside vLLM; there is a design pattern and a recommended migration path. A reader who believes TGI was absorbed should correct that here. Recorded because TGI was a significant GPU serving engine and its retirement is itself a fact worth having in the knowledge base; recommended migration targets are vLLM or SGLang. Confirmed still in use at Hugging Face to power Hugging Chat and the Inference API/Endpoints, which is the useful nuance behind the deprecation: retired upstream by maintainers, still deployed in production at Hugging Face. ||| MAINTENANCE (dated fact, GitHub API, 2026-10-04): last commit 2026-03-21 (6.5 months ago), latest release v3.3.7 published 2025-12-19, 148 contributors, open_issues_count 324 (issues PLUS pull requests), ARCHIVED flag TRUE, 10882 stars. This confirms and sharpens the existing record rather than contradicting it: the repo is read-only, the last release is ten months before this record's date, and the last commit is six and a half months before it. DEPLOYMENT: this engine remains the one clear NAMED DEPLOYMENT with no numbers - confirmed still in production at Hugging Face powering Hugging Chat and the Inference API/Endpoints, which is graded YES-without-numbers, and HF publishes no throughput, request volume or fleet size for it. That combination is the whole point of the record and the grading scheme in [[ev-production-evidence-is-scarce-and-nearly-always-single-site]] keeps it distinct from 'no evidence': archived upstream, deployed downstream, no figures either way. CHUNKED PREFILL and STRUCTURED OUTPUT: unstated for this engine and not verified. tracing_support set to basic on 2026-10-04, carried from the same-repo record obs-tgi-observability: OTel is present but emits only generic gRPC SERVER spans named after the RPC method with rpc.* attributes, opt-in via --otlp-endpoint. No gen_ai attributes and no prefill/decode split. The TTFT and KV-occupancy metrics it lacks were established by zero-hit searches documented there.

Notes

Status deprecated and confidence deliberately moderate: the repo is ARCHIVED and read-only (archived flag true, last push 2026-03-21, final release v3.3.7 on 2025-12-19), so most capability claims are historical rather than current. CORRECTION TO A COMMON MISCONCEPTION, verified against the README on 2026-10-04: TGI was NOT merged into vLLM. It was retired. The README's own words are 'text-generation-inference is now in maintenance mode. Going forward, we will accept pull requests for minor bug fixes, documentation improvements and lightweight maintenance tasks', followed by an explanation that 'TGI has initiated the movement for optimized inference engines to rely on a transformers model architectures. This approach is now adopted by downstream inference engines, which we contribute to and recommend using going forward: vLLM, SGLang, as well as local engines with inter-compatibility such as llama.cpp or MLX.' The architectural idea - optimised transformers model architectures shared with downstream engines - was donated rather than the codebase. So there is no TGI code inside vLLM; there is a design pattern and a recommended migration path. A reader who believes TGI was absorbed should correct that here. Recorded because TGI was a significant GPU serving engine and its retirement is itself a fact worth having in the knowledge base; recommended migration targets are vLLM or SGLang. Confirmed still in use at Hugging Face to power Hugging Chat and the Inference API/Endpoints, which is the useful nuance behind the deprecation: retired upstream by maintainers, still deployed in production at Hugging Face. ||| MAINTENANCE (dated fact, GitHub API, 2026-10-04): last commit 2026-03-21 (6.5 months ago), latest release v3.3.7 published 2025-12-19, 148 contributors, open_issues_count 324 (issues PLUS pull requests), ARCHIVED flag TRUE, 10882 stars. This confirms and sharpens the existing record rather than contradicting it: the repo is read-only, the last release is ten months before this record's date, and the last commit is six and a half months before it. DEPLOYMENT: this engine remains the one clear NAMED DEPLOYMENT with no numbers - confirmed still in production at Hugging Face powering Hugging Chat and the Inference API/Endpoints, which is graded YES-without-numbers, and HF publishes no throughput, request volume or fleet size for it. That combination is the whole point of the record and the grading scheme in [[ev-production-evidence-is-scarce-and-nearly-always-single-site]] keeps it distinct from 'no evidence': archived upstream, deployed downstream, no figures either way. CHUNKED PREFILL and STRUCTURED OUTPUT: unstated for this engine and not verified. tracing_support set to basic on 2026-10-04, carried from the same-repo record obs-tgi-observability: OTel is present but emits only generic gRPC SERVER spans named after the RPC method with rpc.* attributes, opt-in via --otlp-endpoint. No gen_ai attributes and no prefill/decode split. The TTFT and KV-occupancy metrics it lacks were established by zero-hit searches documented there.

Cross-references

This record references no other records — it is a leaf. It is cited by 46.