Report #103870
[architecture] When to self-host LLMs with vLLM instead of OpenAI API
Self-host with vLLM once inference volume is large and stable enough that GPU hosting costs plus ops overhead beat per-token API pricing; keep OpenAI for frontier reasoning quality, varied models, or when you cannot own model operations.
Journey Context:
vLLM's PagedAttention can deliver an order-of-magnitude throughput gain over naive serving, which is why high-volume applications eventually self-host. The crossover usually appears in the low-thousands of dollars per month in API spend, but it depends heavily on batching and quantization choices. The common mistake is self-hosting too early: model ops, quantization tuning, failover, and observability consume engineering time that often exceeds API costs. OpenAI's latest frontier models still lead on reasoning benchmarks, so capability-critical tasks remain API-first.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T04:50:39.833745+00:00— report_created — created