Rune skips the transmission line by running 1,024 GPUs on solar DC at the plant

The buyer for this is an infrastructure lead with graphics cards on order and nowhere to plug them in. Rune's chief executive speaks to that person directly. "Every solar plant is a latent data center," said William Layden, Rune co-founder and CEO ^[8]. "The power is already there, sitting idle while AI labs wait years for grid connections that may never come" ^[9].

Both savings Rune names sit at the interconnection. A solar plant generates direct current and routes it through transformers to make alternating current, because AC travels better on long lines, and at the far end an AI data center converts it back to DC for the servers ^[5]. Put the servers beside the panels and the line is unnecessary, and so are both conversions ^[4][6]. For the scale of the expense being skipped, SiliconANGLE reports that OpenAI expects to spend $4.2 billion on power transmission hardware in connection with its Ohio buildout ^[13].

Fifteen percent of the auxiliary infrastructure bill still remains on Rune's own numbers ^[14]. The report does not include a price for a module or the baseline the 85 percent is measured against ^[15]. A buyer with estimates in hand can still test it, because the two items are specific enough to appear as line items: the long-haul circuit and the transformers at each end of it.

Capital cost per installed GPU and cost per delivered GPU-hour are different numbers, and the second is the one that shows up in the training bill. Rune's other argument is curtailment. Utilities lower solar output when supply exceeds demand, and Rune says RELIC can harness that unused capacity for AI processing ^[7]. Curtailed output exists only while the plant is generating more than the grid wants, so the hours on offer follow the plant's production curve ^[16].

A workload sorts onto hardware like this if the job survives being stopped and resumed, and if nobody outside the company notices the pause. Checkpointed pretraining and overnight batch evaluation clear both. A production inference endpoint with a latency commitment clears neither, and no amount of setup speed changes that.

The number that decides this is cost per delivered GPU-hour. Count it across a full month of one plant's output, then set it against the same figure for a grid-connected site with a queue date attached.