ROCm Infera#

A lightweight inference-serving layer for AMD ROCm GPUs. Infera (the infera package) puts an OpenAI-compatible endpoint in front of one or many model workers, and routes each request to the best worker — by cache locality, by load, or by splitting prefill and decode across GPUs. It runs vLLM, SGLang, or ATOM underneath, and adds an AMD-native tiered KV cache that spills from GPU memory to RAM, NVMe, and the network.

If you have ever run vllm serve, you already know 80% of this. Infera is the thin orchestration layer that turns one model server into a routed fleet.


Start here#

Quick start

Five minutes from pip install to a served model and a working curl.

Quickstart
Overview

What Infera is, the three moving parts, and when to reach for it.

Overview
Server and router

The OpenAI-compatible endpoints and how requests flow through the router.

Server & router

Components#

The moving parts, one page each — what they are and how to run them.

Server & router

OpenAI / Anthropic endpoints + the router (modes, policies).

Server & router
Engines

vLLM / SGLang / ATOM workers — launch, TP, DP-attention.

Engines
KV cache management

kvd’s tier design, offload/onboard mechanism, and on-disk format.

KV-Cache Management (kvd)
Operator

The Kubernetes CRD that reconciles server + prefill/decode pools.

Operator (Kubernetes)

Feature one-pagers#

Each of these is a single, self-contained page — read only the one you need.

KV-aware routing

Route to the worker that already holds your prompt’s prefix.

KV-aware routing
PD disaggregation

Run prefill and decode on separate GPUs (or nodes) and stitch them with a KV transfer.

PD disaggregation
KV cache offload

Spill KV to RAM / NVMe / network — the usage modes and per-request control.

KV-Cache Offload