MetroVolt Siting Context
MetroVolt is the burner in a data-center housing, sited with the load it powers to shrink both water and transmission land.
MetroVolt is the burner (Aegis / MetroVolt) configured to power data centers. Its siting logic is co-location: the generator sits with the computing load it serves. That arrangement addresses two of the largest environmental terms for data centers — the water embedded in grid electricity and the land of long transmission corridors.
Why co-location helps here
Grid electricity for a data center carries embedded thermoelectric cooling water and arrives over transmission land. MetroVolt's direct-energy-conversion architecture makes power without a steam cycle, cutting the embedded-water term, and generating on-site removes the corridor for the primary load. Server cooling remains a separate facility choice.
The availability gate is decisive here
Data centers demand extreme uptime. The burner's design-and-simulation availability of ~0.86-0.995 is 30-100x short of hyperscale Tier III (0.99982). So MetroVolt is honestly framed as an on-site generation architecture that reduces water and transmission land, but not as a sole Tier-III power source today; it would operate with grid or storage backup. Overstating uptime would be false and is avoided deliberately.
- Helium-3 fuel demand for a commercial unit is ~400x current domestic supply, gating deployment on breeder-bred and lunar helium-3.
- The machine is a design-and-simulation study, not built.
- Water and land advantages are architectural and real; uptime is a stated gate.
It is worth being precise about what co-location does and does not solve. It addresses the electricity-side water embedded in grid supply and the transmission land for the primary load; it does not change how servers are cooled or, on its own, meet Tier III uptime. Presenting those boundaries clearly is what keeps the MetroVolt case credible to an audience that scrutinizes uptime above almost everything.