# Oracle’s Stargate partnership tied a 4.5GW plan to named buildout milestones OpenAI announced a 4.5-gigawatt Stargate partnership with Oracle on July 22, 2025, describing planned US data-center capacity rather than completed delivery. Canonical: https://rangoon.ai/insights/archive-openai-oracle-stargate-four-point-five-gigawatt-2025/ Author: Rangoon Editorial (https://rangoon.ai/insights/editorial/) Published: 2026-10-23 Updated: 2026-10-23 Event date: 2025-07-22 Tags: [OpenAI](https://rangoon.ai/insights/tags/openai/), [Oracle](https://rangoon.ai/insights/tags/oracle/), [Stargate](https://rangoon.ai/insights/tags/stargate/), [data centers](https://rangoon.ai/insights/tags/data-centers/) Source note: Historical reporting: primary documents record this event on 2025-07-22. Vendor statements, planned schedules and comparative figures remain attributed. This retrospective does not infer current availability, price, capacity, performance or support. Image: Site commissioning chain. Original Rangoon explanatory diagram: concepts for editorial review, not measured results, an official legal determination, vendor interface or event photograph. ## Key takeaways - OpenAI said its Stargate partnership with Oracle would develop 4.5 gigawatts of additional US data-center capacity. - A vendor announcement, a plan, an installed system and a completed workload are different evidence states. - Original analysis: retain configuration and outcome evidence before treating an infrastructure claim as an operating result. ## The dated event has a bounded claim [source 1](https://openai.com/index/stargate-advances-with-partnership-with-oracle/) [source 2](https://www.oracle.com/data-centers/) On 2025-07-22, the first primary document recorded this event. OpenAI said its Stargate partnership with Oracle would develop 4.5 gigawatts of additional US data-center capacity. The July statement presented the capacity as planned buildout and identified the work as part of Stargate’s broader infrastructure program; Oracle’s data-center page recorded the same announcement date. The July Oracle partnership said the companies entered an agreement to develop 4.5GW of additional Stargate capacity and placed the result within capacity under development. That wording is stronger than a general aspiration but still different from power that has been commissioned and allocated to a running customer workload. ## Engineering facts need a workload boundary [source 1](https://openai.com/index/stargate-advances-with-partnership-with-oracle/) [source 2](https://www.oracle.com/data-centers/) Power capacity is only one layer of a usable AI service. Server configuration, network, storage, cooling, grid connection, commissioning and customer allocation must line up before a workload is served. An announced site portfolio therefore remains a schedule, not a delivered cluster. OpenAI’s statement distinguished the additional sites from Stargate I in Abilene, where it said parts were up and early training and inference workloads had begun. A story must not transfer that early-workload fact to every proposed Oracle location or use it as proof that all 4.5GW was live. ## Plans, delivery and use are separate states [source 1](https://openai.com/index/stargate-advances-with-partnership-with-oracle/) [source 2](https://www.oracle.com/data-centers/) The relevant construction record has at least two paths: site work and compute commissioning. Equipment can arrive before grid interconnect, and a powered hall can precede model acceptance. Recording those states per site makes it possible to see whether a constraint is power, building, servers, network or software. Gigawatts describe an electrical scale, not a billable service unit. The cost of a training run also includes accelerator configuration, utilization, networking, storage and failure recovery. Job estimates and construction claims in the announcement should remain attributed to OpenAI rather than converted into measured economic output. ## Original analysis: make the operating evidence inspectable [source 1](https://openai.com/index/stargate-advances-with-partnership-with-oracle/) [source 2](https://www.oracle.com/data-centers/) For each named site, ask for a state and evidence: land, permit, utility interconnect, construction, equipment installed, energised, commissioned and workload accepted. Report missing states as unknown; do not fill them using a project-wide headline number. This event can be updated safely by attaching named sites and state changes to the July agreement. Until then, “under development” is the accurate phrase. It preserves the supplier’s announced scope while keeping delivered capacity and productive AI compute as later evidence questions. For the Oracle expansion, compare every future capacity statement against the July baseline: 4.5GW additional capacity under development and more than 5GW under development when combined with Stargate I. Then record whether the new claim is a change in agreement, site count, construction, energization or model use. This prevents a progress update for one facility from being read as completion of the whole partnership. The Oracle story includes both an agreement for additional capacity and a separate early-workload statement for Stargate I. Keeping those clauses apart prevents the most concrete operating fact from being incorrectly generalized to all future development capacity. ## Sources 1. [OpenAI: Stargate advances with partnership with Oracle](https://openai.com/index/stargate-advances-with-partnership-with-oracle/) 2. [Oracle: Data centers and Stargate update](https://www.oracle.com/data-centers/) ## Related reading - [Stargate’s January announcement made financing intent different from built infrastructure](https://rangoon.ai/insights/archive-openai-stargate-project-announcement-2025/) - [OpenAI, Nscale and Aker announced Stargate Norway as a planned Narvik facility, not live European compute](https://rangoon.ai/insights/archive-openai-stargate-norway-announcement-july-2025/) - [Marvell’s Celestial AI agreement put optical scale-up on a later-closing timeline](https://rangoon.ai/insights/archive-marvell-celestial-ai-agreement-december-2025/) ## More information - [Documentation index](https://rangoon.ai/llms.txt) - [AI access and policies](https://rangoon.ai/ai/) - [Source repository](https://github.com/hypler-dev/rangoon)