Skip to content

Build1 publisherNot yet confirmed elsewhere2 min readPublished

National Compute's shared AI grid counts 760 MW as connected or in sight

Anjney Midha's National Compute launched a shared AI compute grid that it says has about 760 MW connected or in sight. For startups and researchers, the open question is how much of it the Grid Exchange scheduler can place real jobs on today.

The Engineer · Build desk

How we use AISend a correction

Illustration accompanying National Compute's shared AI grid counts 760 MW as connected or in sight
Generated illustration

What happened

  • The National Compute Grid, announced October 7, is meant to let startups, universities and public-sector researchers use capacity spread across clouds, labs and chip systems.
  • A shared scheduler matches jobs to resources that providers list by chip type, location, price and utilization.
  • Vultr, a founding member, says pricing will be based on goodput, meaning completed and uninterrupted work, instead of GPU-hours.
  • The consortium's stated goal is 2 GW of pooled capacity by 2030.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

  • constraint A team sizing a training run cannot plan against 760 MW until the consortium says how much is running, contracted and open to customers.
  • cost Goodput billing puts the cost of preemptions and node failures on providers, so operators with unreliable spare capacity pay to list it.
  • decision Smaller AI companies shut out of long-term contracts now have a pooled option to weigh, and they will have to prove it with their own jobs before relying on it.

"Connected or in sight" puts two different states under one number [1]. Of the two words, "connected" is the one a scheduler can send a job to. According to Runtimewire's reading of the launch, the wording does not say how much of the 760 MW is operational, contractually committed or available to customers now [3]. Against the 2030 target [9], the figure is 38% of the goal [17], and that share assumes every in-sight megawatt shows up.

National Compute calls its software layer Grid Exchange [4]. Members can put idle capacity into it or reserve larger clusters for planned training runs, and the scheduler routes workloads across participating sites and systems [4]. Vultr says the pool will span NVIDIA, AMD and TPU architectures [10]. Chip type is one of the fields providers list capacity under [2]. A given job can only use the part of the pool listed under hardware it runs on, so the headline figure overstates what any one customer can reach.

Goodput pricing [11] is the best design decision in the launch. Under it, a preempted job or a failed node is the provider's loss. An operator that lists unreliable spare capacity pays for the unreliability, and the cost lands on the party that controls it. I think it is the right default for a pool of independent operators who do not share an on-call rotation.

The supply case rests on idle hardware. The consortium's paper, as Axios summarized it, says independent single-tenant data centers average less than 15% net computing utilization [5]. Taken at face value, more than 85% of their capacity goes unused [16]. The figure is the group's own, not an independently audited measure [6]. For it to carry over to this grid, the idle hardware has to sit at sites that join. It also has to be free when a job asks for it.

Demand is easier to show. The consortium says it is opening access to public-sector teams, including government, education and national laboratory users [12]. Sam Sinha, head of AI at robotics company 1X, told Axios that when it comes to large, long-term contracts, smaller operators have a hard time competing with OpenAI and Anthropic [13]. Midha helped some founders secure computing access when he was an a16z general partner [15]. He told Axios that U.S. compute capacity is larger than most people assume, and that what it lacks is interconnection and coordination [14].

The launch materials describe an intended design, not independently demonstrated results [7]. If every counted megawatt does convert, the consortium still needs another 1,240 MW to reach 2 GW by 2030 [18].

What to watch

  • A breakdown of the 760 MW into operational, contractually committed and customer-available capacity.
  • Published goodput results from jobs routed across more than one provider or across NVIDIA, AMD and TPU hardware.
  • Independent utilization data for single-tenant data centers, or the method behind the consortium's under-15% figure.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories