Oracle adds NVIDIA’s Vera Rubin to its cloud, with multi-gigawatt growth planned
The coordinated rollout covers model computing and the tool-running work around AI agents. General availability is here; the largest infrastructure expansion remains a plan.
Oracle and NVIDIA are extending OCI beyond GPU-heavy model training and inference: Vera CPUs are intended to handle agents’ tool calls, retrieval and code execution, while Rubin GPUs handle model work. Customers can access Vera Rubin NVL72 systems and Vera CPUs now, but Oracle’s multi-gigawatt Supercluster expansion and eight-GPU HGX Rubin NVL8 server remain plans, not delivery commitments. The claimed reduction in GPU idle time has no quantified result yet; OpenAI’s cited GPT-6 Astra deployment used more than 100,000 Blackwell GPUs, not Rubin.
01
Each NVL72 rack connects 72 GPUs through NVLink; the planned network combines Oracle Acceleron with NVIDIA Spectrum-X, Spectrum-6 switches and BlueField-4 DPUs.
02
The planned HGX Rubin NVL8 is an x86 server with eight Rubin GPUs, two 64-core Intel Xeon 6 CPUs and 4 TB of DDR5 memory.
03
OCI Kubernetes Engine lets customers scale CPU and GPU resources independently, while Oracle says Acceleron isolates workloads running untrusted, AI-generated code.
Oracle customers can now accessNVIDIA’s Vera Rubin NVL72 systems and Vera CPUs through Oracle Cloud Infrastructure, the companies said on October 27, 2026. Their announcement pairs a planned multi-gigawatt expansion with a different efficiency pitch: giving AI agents enough CPU capacity to execute tools and code without leaving GPUs waiting between model calls.
Two kinds of computing, two kinds of work
The collaboration, announced at Oracle AI World in Las Vegas, covers both sides of an agent’s workload. GPUs handle the intensive computing involved in training models and generating responses. CPUs perform surrounding tasks, including retrieving information, running tools and testing code. Slow execution of those steps can hold up an agent even between model responses, the companies said.
Oracle’s pitch for Vera CPUs rests on two features: strong performance on individual processing threads and high memory bandwidth. The first is intended to accelerate individual tool calls and code execution. The second keeps processor cores supplied with data when agents run many tasks at once. The companies say that combination can reduce GPU idle time; they did not provide a quantified improvement in this announcement.
Customers can scale CPU and GPU resources independently through OCI Kubernetes Engine, Oracle’s service for managing software workloads. That lets them adjust each type of computing to the work at hand rather than increase both together. Oracle also says its Acceleron infrastructure provides hardware-based isolation for workloads running untrusted, AI-generated code.
We are bringing Vera into production on OCI to support these workloads at scale.
Uday Ruddarraju, OpenAI chief technology officer of compute, on agentic sandbox workloads
A 72-GPU rack—and a smaller option
For the largest model workloads, the companies plan to take OCI Superclusters using Vera Rubin NVL72 systems to multi-gigawatt scale. Each NVL72 rack connects 72 GPUs through NVIDIA’s NVLink networking. Oracle says its network can connect hundreds of thousands of GPUs, combining the rack systems with gigawatt-class power and cooling.
The network combines Oracle Acceleron with NVIDIA Spectrum-X Ethernet technology, Spectrum-6 switches and BlueField-4 data processing units. This planned expansion builds on Oracle’s existing GB200 and GB300 NVL72 infrastructure. NVIDIA says the shared CUDA software foundation helps customers support changing models and workloads across those hardware generations.
Not every planned configuration is rack-sized. Oracle also intends to offer HGX Rubin NVL8, an x86-based server with eight Rubin GPUs connected through NVLink. The company positions it as a smaller option for training, fine-tuning and generating model responses, while retaining compatibility with x86-based applications.
The planned eight-GPU server
Two Intel Xeon 6 CPUs, each with 64 cores.
4 TB of DDR5 memory.
Available hardware is not the same as completed capacity
The immediate change is general availability of Vera Rubin NVL72 and Vera CPUs on OCI. The multi-gigawatt Supercluster expansion and eight-GPU offering remain future plans. Oracle’s product disclaimer says development, release timing and pricing can change, and that the outlined direction is not a delivery commitment.
OpenAI supplies a concrete example of the existing infrastructure’s use. The announcement says it trained and served GPT-6 Astra on an OCI Supercluster in Abilene with more than 100,000 NVIDIA Blackwell GPUs. That deployment used Blackwell hardware, not the newly available Rubin systems. OpenAI’s Vera CPU production work targets a different part of the stack: the environments where agents execute code and run tools.
AI agents’ tool calls and code execution are getting dedicated computing capacity on Oracle’s cloud. Oracle announced NVIDIA Vera-powered Compute instances on October 27, 2026, with an initial 150,000 CPUs planned across its regions. The announcement calls the offering generally available, but also says access will begin in select regions this quarter.
Oracle’s two availability statements leave an important distinction: the general-availability announcement is not a promise of immediate access in every region. Its stated rollout begins in select regions during the current quarter, while the 150,000-CPU figure describes the initial capacity it intends to make available across Oracle regions.
Customers can choose bare-metal servers or Flex Virtual Machine instances. Oracle also positions Vera as a standalone CPU platform, allowing agent services to run independently of GPU infrastructure. It can support GPU-based environments where needed, rather than requiring those surrounding services to be deployed as part of a GPU system.
The pitch addresses a specific delay in agent workflows. A GPU can generate a model response, but the next model step may have to wait for a CPU to execute code, run a tool or retrieve information. Oracle says faster completion of those jobs can shorten the wait between model interactions and improve an agent’s overall response time.
Oracle identifies several kinds of work for the new instances. They extend beyond producing model responses to the software that coordinates agents, prepares their data and manages the computing resources around them:
Coordinating agent sessions, executing tools and processing their results.
Running isolated code, tests and simulations, including environments used for reinforcement learning.
Searching and retrieving data, including vector search and in-memory analytics.
Scheduling GPU workloads, routing requests and supporting monitoring and data pipelines.
Reinforcement learning adds another reason to care about CPU speed. In that process, a system acts in an environment and receives feedback. Oracle says faster environment execution can accelerate those feedback loops and increase training throughput. That is a different benefit from making an individual model response arrive faster.
Oracle says multiple customers have used early-access production systems. One named customer is OpenAI: Uday Ruddarraju, its chief technology officer of compute, said the company is bringing Vera into production on OCI to support its growing agentic sandbox workloads, where agents execute code and run tools.
Each Vera processor uses 88 custom Arm-compatible Olympus cores and supports up to 1.2 TB per second of memory bandwidth. NVIDIA’s design combines a single compute die with a shared system for keeping data consistent across the processor, which Oracle says is intended to support many concurrent jobs. The OCI configuration also includes 7.68 TB of local NVMe storage for fast data access.
The largest performance figure needs a separate qualification. NVIDIA reports up to 80% faster agentic CPU performance than leading x86 CPUs. Those results come from NVIDIA platform benchmarks, not OCI instance-level testing, and actual performance varies with the workload and configuration. The figure therefore is not a measured speedup for an agent running on Oracle’s new instances.
Oracle also argues that shortening CPU-bound steps can help GPUs retain cached context—the stored information from earlier model processing. Preserving that context can reduce repeated computation, letting GPUs spend more time generating responses rather than waiting for dependent tasks. That remains a stated benefit of the design, rather than a quantified OCI performance result.
Reader comments
Newest comments first. Replies stay oldest first.