A position paper

The Other Cloud

Why the most overused word in technology was always a weather word, and what happens when you give it back.

Zero Edge

I. It started as a drawing that meant “don’t ask”

Before the cloud was an industry, it was a doodle.

Engineers sketching telephone systems needed a way to show that a signal went into the network and came out somewhere else. The interior was somebody else’s problem, so they drew a puffy shape around it and moved on. The convention carried into computing. A cloud shape stood in for networks on ARPANET diagrams by 1977 and on CSNET by 1981, and it always meant the same thing: there is machinery here, and you do not need to know about it.

The word followed the picture.

In November 1996, a small group at Compaq wrote an internal strategy document with “cloud computing” in the title. In May 1997, a startup called NetCentric filed to trademark the phrase, then let it lapse. That same year, an academic named Ramnath Chellappa described cloud computing as a model whose boundaries would be set by economics rather than by technical limits. Nine years later, in August 2006, Eric Schmidt used it from a conference stage and it entered every boardroom in the world within about eighteen months.

Four moments, one direction of travel. Each step moved the machine further out of sight. That was the product. You stopped owning servers. You stopped knowing where your data lived. You stopped thinking about the building, the substation, the cooling towers, the river. The cloud was a promise that none of it was your concern.

For thirty years, that promise held.

II. The invisible turned out to have a footprint

It stopped holding the moment the machinery got big enough to see from the road.

Water. Most large data centers reject heat by evaporating water, and roughly 80 percent of what they withdraw never returns to the supply. Google disclosed withdrawing 7.8 billion gallons across its data centers in 2024 and consuming 78 percent of it. Its largest site, in Council Bluffs, Iowa, averaged 3.9 million gallons withdrawn per day and consumed 2.8 million of them. A single hyperscale facility can use as much water in a day as a town of ten to fifty thousand people.

Power. The International Energy Agency projects global data center electricity consumption will more than double between 2022 and 2026, approaching 1,000 terawatt-hours a year. That is roughly what the nation of Japan consumes.

Consent. Communities have noticed, and they are voting. The National League of Cities has tracked at least 76 local governments attempting moratoriums or outright bans, most of them succeeding. Brookings counts more than 100 localities that have approved pauses and at least 15 states that have weighed them. Data Center Watch recorded at least 75 projects worth close to $130 billion blocked or delayed in the first quarter of 2026 alone — the highest quarterly figure on record — while the number of grassroots groups organized in opposition more than doubled, from 396 to 833. In Monterey Park, California, 90 percent of voters backed a permanent ban. In August 2026, the Cherokee Nation barred hyperscale data centers on tribally owned and trust land, a line drawn against the giants, not against compute.

This is not a public relations problem. It is arithmetic arriving at a county commission meeting.

And it is a strange fate for a metaphor. The cloud was supposed to be the part you never had to look at. Now it is the thing your neighbors are holding signs about.

III. There is another cloud, and it was here first

Here is what the industry forgot when it borrowed the word.

A cloud is not an abstraction. It is the visible portion of the water cycle. Water lifts off the land, gathers where the air is cold enough to hold it no longer, and falls back onto the same land it came from. Nothing is consumed. Nothing is exported. The system has been running without a net loss for roughly four billion years.

It is the oldest closed loop on Earth, and the only one every single person already understands.

So we are not abandoning the word. We are returning it to its original owner.

Cloud, as in the water cycle. It returns everything it takes.

That is the whole thesis of this company, and it happens to be sitting inside a name we already had.

IV. What the loop actually is

A metaphor is worth nothing if the engineering doesn’t match it. Ours is a circle with four stations, and material moves around it continuously.

Waste. It begins at the community’s own transfer station or landfill — the municipal waste stream a town is already paying to haul somewhere else and bury.

Energy. Modular plasma gasification converts that stream into electricity on site, behind the meter. The town’s trash becomes the town’s power. No new transmission line, no place in the utility interconnection queue, no diesel farm idling for the nights the grid is short.

Compute. That power runs a small, immersion-cooled data node. Sealed liquid cooling means the heat leaves through a closed loop rather than through an evaporating plume, so the facility consumes no water for cooling. Sized deliberately in the low single-digit megawatts — beneath the thresholds that moratoriums are being written to stop.

Recovery. Servers retire. Their metals return to the gasifier for reclamation rather than to a container ship. What the loop produced, the loop takes back.

Then it begins again.

The waste does not leave. The water does not leave. The metals do not leave. The tax base does not leave. And because the compute sits inside the jurisdiction that owns it, the data does not leave either.

V. Sustainability is a structure, not a percentage

Most of what the industry calls sustainability is a rate of improvement on a harm. Twenty percent less water. Forty percent less energy. Carbon offset by an instrument purchased in another hemisphere. These are real engineering achievements and we do not dismiss them. But every one of them describes a slower leak.

A loop is a different category of thing. Efficiency asks how little you can take. A closed system asks whether taking is the right model at all.

The distinction matters most to the people who live nearest the building. “We use 40 percent less of your water” is a negotiation. “We do not evaporate your water” ends the conversation and starts a different one.

This is what we mean when we say we are a sustainable company. Not that our footprint is small. That the circle closes.

VI. Why now, and why small

We are entering an era in which machine cognition becomes ordinary infrastructure, the way electricity and broadband did before it. That shift is going to require an enormous amount of compute, and the industry’s instinct is to meet it the way it has met every previous demand curve: build bigger, build farther away, and ask the nearest watershed to absorb the difference.

That instinct is now colliding with democracy, and democracy is winning more often than the industry expected.

We think the answer is the opposite shape. Compute that is small, close, sited inside the community it serves, sized below the thresholds that communities are drawing, and powered by a waste stream that town is already producing. Not a campus imposed on a place. A utility that belongs to it.

The cloud, in other words, comes back down to earth. Which is the only thing clouds have ever done.

VII. What we are asking you to do with a word

Every time you have heard “the cloud” for thirty years, you have been asked to stop looking.

We are asking for the reverse. Look at the whole thing. The truck that leaves the transfer station. The gasifier that turns its contents into current. The sealed racks that current runs. The metals that come back when the racks retire. The water that was never spent in the first place.

That is a cloud in the older and more honest sense: a system that gives back everything it borrows, visible from the road, running where you live.

Nothing is wasted. Everything returns.