In this analysis
Planned megawatts and current GPU allocation measure different states; a project must match the announced delivery window to its own execution deadline.
CoreWeave’s India announcement describes a planned 240 MW campus, with the first phase expected in mid-2028. It is evidence of future infrastructure development, rather than a current GPU allocation. The useful question for an application team is whether the project’s delivery window matches its own need for executable capacity.
Start with the published delivery state
The October 7, 2026 investor-relations release states the planned Navi Mumbai deployment and phased timing. A plan can be commercially important while remaining outside the operating window of a project that needs resources sooner.
This is a calendar dependency. Announcement scale cannot compensate for a delivery date that falls after the work must run. Conversely, a longer-horizon project can use the plan as a candidate future option without counting it as already allocated.
Keep electrical and application units separate
The announced megawatts describe datacenter capacity. They do not directly specify a number of model replicas or completed requests. Those quantities depend on the system configuration and the workload that consumes it.
| Unit | What it can describe | Additional evidence needed |
|---|---|---|
| Planned datacenter power | Infrastructure development scale | Commissioning and operating state |
| Installed systems | Physical compute configuration | Readiness and support scope |
| Allocated service capacity | A customer’s usable window | Eligible workload and operating conditions |
A conversion between these rows needs explicit assumptions. Inventing a GPU count from the campus power headline would hide those assumptions.
Use earlier milestones as context
CoreWeave’s January 5 Rubin roadmap established intended platform adoption. Its August 4 Indonesia announcement established an earlier Asia-Pacific expansion plan. These are real precursors to the India release, not evidence that the later campus was already operating.
The causal hypothesis is geographic expansion supported by a developing compute platform. Both commercial presence and physical delivery are necessary to that story, but they progress through different milestones.
Match the plan to a project horizon
An illustrative project note should name the required location, the date work must begin and the execution conditions it needs. It can then classify the India campus as a future candidate, an unsuitable timing match or an option awaiting later delivery evidence.
This produces a usable decision without pretending to know inventory. It also avoids dismissing a meaningful infrastructure plan merely because it does not solve an immediate allocation problem.
Preserve the difference in the retrospective
The October event expands the documented future footprint. It does not establish current availability, reserved customer capacity or a guaranteed service result.
GPU availability and hourly cost explains the operating-window distinction. Colocation and on-premise deployment explains the facility boundary. Together they connect a large campus plan to application planning without turning planned power into fictional live inference.