Tag: Nvidia Dynamo

  • CoreWeave’s 15x Reload Claim Puts AI Inference on the Training Critical Path

    CoreWeave’s 15x Reload Claim Puts AI Inference on the Training Critical Path

    TL;DR · 30-second read

    The Short Version

    CoreWeave is a company that rents out the powerful computer chips used to build artificial intelligence. It has now launched Forge, a software toolkit for building and running artificial intelligence systems. Anyone can start using it for free.

    The surprising part: when these systems learn by trial and error, they keep swapping in updated versions of themselves. CoreWeave says it made that swap 15 times faster in testing, so the learning stops stalling.

    The move also puts CoreWeave in more direct competition with Amazon, Google and Microsoft, which already sell similar toolkits.

    CoreWeave has launched CoreWeave Forge, a platform that connects model serving, observability, post-training and evaluation in one environment. It was unveiled at the Fully Connected event and is free to start, with paid tiers for additional capabilities. CoreWeave’s product page describes Forge as a way to “run, observe, curate, improve, and evaluate models and agents” without locking work to one cloud, model or framework.

    SiliconANGLE reported on October 8 that Urvashi Chowdhary, CoreWeave’s vice president of product and AI services, said a preview capability called CoreWeave RL Rollouts, built on Nvidia’s Dynamo framework, improved model reload latency by 15x compared with a baseline configuration in testing.

    Executive Summary

    CoreWeave built its business renting GPU capacity, the graphics processors that train and run AI models. Forge adds managed software on top of that capacity. According to CoreWeave’s product page, it covers fine-tuning, managed reinforcement learning, per-token serverless inference, dedicated inference, agent tracing, sandboxes, a model and dataset registry, and experiment tracking through Weights & Biases Models. The free entry tier extends the platform to individual developers, not only the large labs and enterprises that sign capacity contracts.

    The most technically significant claim concerns reinforcement learning, the training method used to build agentic models that take multistep actions. In that workflow, the inference system that generates the model’s attempts has to keep reloading freshly trained versions of the model. CoreWeave says RL Rollouts cut that reload time 15-fold in testing. If that holds outside the lab, inference performance becomes a direct constraint on how fast these models can be trained, which changes how teams should size and buy GPU capacity.

    Commercially, Forge places CoreWeave alongside hyperscaler AI platforms such as Amazon Bedrock and SageMaker, Google Vertex AI and Microsoft Azure AI Foundry. Its distinguishing pitch is an open-source foundation and portability across clouds, models and frameworks.

    Inference Is Now on the Training Clock

    In conventional AI development, training and inference are separate phases. A model learns from a fixed dataset, and inference, meaning serving the model to answer requests, comes afterward. Reinforcement learning for agentic models erases that boundary. The model generates attempts at a task, called rollouts. Verifiers check the results and rewards score them, and those scores update the model. Each update produces a new checkpoint, a saved snapshot of the model’s weights, which must be loaded back into the inference servers that produce the next round of attempts. Chowdhary described inference as the bottleneck during rollouts, and the mechanics show why: every reload is time the loop spends waiting.

    That is the problem the 15x figure addresses. CoreWeave RL Rollouts is built on Nvidia’s Dynamo, an open-source framework for distributing inference across many GPUs. It loads new checkpoints into a live deployment, and Chowdhary said the approach improved model reload latency 15-fold against a baseline configuration. The practical effect, in Chowdhary’s framing, is that training keeps moving while inference scales independently. This matters to the people who plan and buy GPU capacity. When inference sits inside the training loop, the size and responsiveness of the inference fleet partly determine training throughput. Teams can no longer budget the two as unrelated line items.

    The claim deserves careful reading. The baseline configuration has not been specified. The figure comes from testing. The capability is in preview. Reload is also only one step in each loop iteration, alongside generating rollouts, scoring them and updating weights, so a 15x gain in reload time does not translate into a 15x gain in end-to-end training speed. CoreWeave has not quantified that overall effect. The direction of the argument is sound. Its magnitude in production is still unproven.

    From GPU Landlord to Platform Vendor

    CoreWeave’s product page lays out Forge as a five-stage loop. Teams run models and agents, observe them through traces in Agent Lens, curate failures into versioned datasets, improve the model through fine-tuning, reinforcement learning or distillation, and evaluate the new version before it ships. Pricing models span per-token serverless inference on open models and dedicated inference, where a customer’s own weights run on GPUs it chooses. Chowdhary described the strategy as building managed services in layers on top of the infrastructure, so that each service builds on the others.

    The economic logic is familiar from the hyperscalers. Raw GPU capacity is easiest to sell when it is scarce, and it is easiest to compare on price when it is not. Software layers give a provider other ways to compete. Customers who keep their experiments, traces, datasets and model registry on one platform have reasons to stay. Per-token pricing lets the provider capture value from efficiency gains on hardware it already owns. The free tier widens the funnel to individual developers who would never sign a capacity contract. Amazon, Google and Microsoft have pursued the same strategy for years by bundling compute with managed AI platforms. Forge is CoreWeave’s entry into that contest.

    CoreWeave’s chosen point of difference is openness. Chowdhary emphasized open-source tools such as vLLM and contributing back to open projects, and the product page promises work that is not locked to one cloud, model or framework. That is a credible counter to proprietary platform stacks. It also creates a tension the company will have to resolve in practice, because an integrated, connected loop is valuable precisely because it is sticky. Portability will be judged by how easily customers can move data, traces and registry entries out, not by the launch language.

    Reading the Inference Demand Signal Carefully

    The demand case rests on one data point. In a theCUBE Research survey of CoreWeave customers and prospects, one healthcare customer’s share of inference workload rose from about 10% in its first year to 40% in its second, with roughly 50% expected within 12 months. That fits the thesis that serving models, not training them, will drive the next phase of AI cloud economics. However, it is a single customer drawn from CoreWeave’s own customer base. It illustrates a trend and does not measure one.

    The infrastructure implication still holds. As more of a GPU’s working life goes to serving requests, providers compete on how much useful output each GPU produces. CoreWeave lists Nvidia’s Hopper, Blackwell and Vera Rubin generations, which competitors can also buy. When the hardware is shared, efficiency comes from the software above it. Chowdhary pointed to that layer: the vLLM serving engine, quantized models, which use lower-precision numbers to shrink a model and speed it up, and custom speculative decoders, in which a small draft model proposes output that the large model verifies. Forge packages that tuning as a product. Over time, it could matter as much as the size of the fleet.

    Background

    CoreWeave began as a GPU-based cryptocurrency operation and pivoted to become a specialized AI cloud, renting large clusters of Nvidia GPUs to AI labs and enterprises. It listed on Nasdaq under the ticker CRWV in 2025 and acquired Weights & Biases, the AI experiment-tracking company, the same year. That tooling now sits inside Forge. Its infrastructure catalog spans Nvidia’s Hopper, Blackwell and Vera Rubin GPUs, managed Kubernetes, AI object storage and fleet-management software.

    Specialized GPU clouds grew on demand for model training, which consumes large blocks of capacity for weeks at a time. As AI products reach users, inference, the continuous work of running models to answer requests, takes up a growing share of compute. That has pushed providers to compete on software efficiency and managed services, the territory where Amazon Web Services, Google Cloud and Microsoft Azure have long operated.

    Sources

    Source: AI inference gets a full stack as CoreWeave launches Forge — SiliconANGLE’s interview with CoreWeave’s Urvashi Chowdhary on Forge, inference optimization and RL Rollouts.

    Primary sources: CoreWeave Forge → Models, agents, training, and inference (CoreWeave product page).