Reference architectures

Real inference stacks, not hypotheticals — official vendor blueprints and production case studies that named their framework, orchestration, and silicon in public.

Vendor blueprintNVIDIA

Enterprise RAG pipeline

Retrieval-augmented generation for enterprise search, knowledge assistants, and copilots

Framework
NVIDIA NIM microservices (Nemotron LLMs + retrieval/reranking/extraction models)
Orchestration
LangChain-based RAG orchestrator server
Cloud
Docker, Helm/Kubernetes, or Helm/OpenShift — not tied to one cloud

NVIDIA's official blueprint for enterprise RAG: NIM-packaged models behind a LangChain orchestrator, with a vector database (Milvus or Elasticsearch) for retrieval. Silicon isn't pinned in the blueprint itself — it's specified per-model in NIM's separate support matrix.

Vendor blueprintAWS

Generative AI inference architecture and best practices

Real-time and batch inference for RAG, chatbot, and agentic workloads

Orchestration
Self-managed Kubernetes, Amazon ECS, or Amazon SageMaker
Cloud
EC2 g4dn/g5/g6, trn1/trn1n, inf1/inf2

AWS's own prescriptive guidance covers the full decision space rather than one fixed stack — it explicitly compares vLLM, TensorRT-LLM, and Triton, and NVIDIA GPUs against AWS's own Trainium/Inferentia silicon, across self-managed Kubernetes, ECS, and SageMaker.

Vendor blueprintGoogle Cloud

Serving open LLMs on GKE with TPUs

Real-time LLM serving (reference models: Gemma 3/4, Qwen 3 32B)

Framework
Orchestration
Google Kubernetes Engine (Autopilot or Standard)
Silicon
Cloud TPU v6e (Trillium)
Cloud
GKE, provisioned via Terraform + CLI wrappers for single-host TPU nodes

Google's own pre-configured pattern for serving open-weight models: vLLM on GKE, backed by single-host TPU v5e or v6e nodes, provisioned with Terraform rather than clicked together by hand.

Vendor blueprintMicrosoft Azure· 2025-10-24

Multi-node inference with NVIDIA Dynamo on AKS

Large-scale LLM inference serving, benchmarked on GPT-OSS 120B

Framework
NVIDIA Dynamo (disaggregated prefill/decode; vLLM, TensorRT-LLM, or SGLang backends)
Orchestration
Azure Kubernetes Service (AKS)
Silicon
GB200 NVL72 (Grace + Blackwell, NVLink-domain rack)
Cloud
Azure ND GB200-v6 VM series

Azure's AKS engineering team benchmarked NVIDIA's Dynamo disaggregated-serving platform across a full GB200 NVL72 rack on AKS, reaching 1.2M tokens/sec on GPT-OSS 120B — one of the few public examples of rack-scale NVLink inference on a hyperscaler's managed Kubernetes.

Production case studyCharacter.AI· 2026-01-13

Doubling inference throughput on AMD MI325X

Character.AI's production chat-companion serving

Framework
Custom inference stack — AITER kernels, FP8 quantization, DP2/TP4/EP4 parallelism
Orchestration
DigitalOcean Kubernetes (DOKS)
Silicon
AMD Instinct MI325X
Cloud
DigitalOcean

Character.AI, DigitalOcean, and AMD jointly published the tuning behind a 2x throughput gain serving Qwen3-235B on MI325X — topology-aware GPU allocation plus FP8 and custom attention kernels, running on a non-NVIDIA cloud GPU host.

AMD Instinct MI325X platform on DigitalOcean achieved 2x production inference throughput.

Production case studyCharacter.AI· 2024-06-20

A fully custom inference stack, from scratch

Character.AI's production chat-companion serving at 20,000+ queries/sec

Framework
In-house inference engine — not vLLM or TensorRT-LLM

Rather than building on an off-the-shelf serving engine, Character.AI wrote their own — custom int8 attention kernels, cross-layer KV-cache sharing, and tree-structured inter-turn caching. A useful counterpoint: the popular frameworks aren't the only viable path at extreme scale.

Character.AI designs its model architecture, inference stack, and product from the ground up.

Production case studyFireworks AI· 2024-10-15

One engine, two silicon vendors

Fireworks AI's multi-tenant model-serving platform

Framework
FireAttention (proprietary inference engine/kernels)

Fireworks built one proprietary engine (FireAttention) that runs production traffic on both NVIDIA H100 and AMD MI300 — a rare public example of a serving stack designed for silicon portability from day one, rather than a single-vendor bet.

Fireworks has been using AMD MI300 hardware in production since the launch of LLaMA 405B.

Production case studyBaseten· 2025-12-11

TensorRT-LLM as the production serving layer

Baseten's hosted model-inference platform

Framework

A straightforward, publicly confirmed data point: Baseten's platform runs NVIDIA's own TensorRT-LLM directly in production rather than an alternative serving engine — useful as a baseline for how the "default" NVIDIA-native stack performs at a real inference-hosting company.

We use both TensorRT and TensorRT-LLM in production to optimize model performance.

Production case studyTogether AI· 2026-05-04

Custom engine, rack-scale Blackwell

Together AI's inference platform for open-weight and frontier models

Framework
In-house inference engine — dynamic batching and routing

Together AI's engine spans a 72-GPU NVLink mesh with NVFP4 quantization on Blackwell-generation hardware — a look at what a from-scratch serving engine looks like once it's tuned specifically for rack-scale NVLink domains rather than single 8-GPU nodes.

Together's inference engine handles this dynamically, extracting maximum efficiency from each GPU-hour.