Synthesis · Training · Serving · Cost · assembled from many sources, not a reading of one paper. Model names and version numbers are hypothetical stand-ins for a 2026-class system, not any vendor's product.
A frontier model is two machines wearing one name. The first spends months and hundreds of millions of dollars turning a corpus into a file of numbers. The second spends 400 milliseconds turning your sentence into the next one - and has to do that a hundred thousand times a second, profitably. This walks both, in order.
The interactive version of this page lets you vary request shape, batch size, precision, and hardware, and watch the cost and latency move. Without JavaScript you get this framing and the source list below; the numbers underneath are representative of 2026-class deployments rather than any single vendor's disclosed figures.
Corpus construction, tokenization, the repeated decoder block, the parallelism mesh that splits it across tens of thousands of accelerators, what breaks during the run, and the post-training that turns a text predictor into an assistant.
One request end to end: the edge, authentication, safeguards, routing, the scheduler, prefill and decode inside the engine, and the eight tiers of infrastructure between a user and a tensor core.
Why decode is memory-bound and no purchase fixes it, what the KV cache costs, how continuous batching and speculative decoding buy throughput back, and where prompt caching decides the bill in an agent loop.
Scope: this page describes the shape of a modern training and serving stack and the arithmetic that governs it. Hard numbers are datasheet figures or published results and are attributable to the sources above. Everything else - throughput, prices, latencies, model names - is a representative illustration chosen to make the mechanism concrete, not a measurement of any deployed system.