There is no cloud. There never was one. The word exists because we needed something gentler than a warehouse in Ohio, and the abstraction worked too well. It made people forget that data lives somewhere, that bits have address coordinates, that the things you do on your phone travel through copper wires to machines owned by shell companies whose names sound like fantasy verbs.

I first noticed this disconnect while visiting a data center. The person giving us a tour walked through rows of server racks and said, casually, we use about two million gallons of water per year for cooling. That sentence landed in my head like an object I could not set down. Two million gallons. An amount of liquid you could fill a small Olympic pool with twice over, just to keep machines from overheating as they processed something as meaningless as a teenager Instagram story or as consequential as a banker portfolio rebalancing.

We speak about the cloud as if it is the opposite of physical: weightless, odorless, existing in a dimension above geography and physics. Upload your files to the cloud, we say, as though uploading meant lifting something into pure information. But every single upload involves electricity flowing through circuits, heat generated by CPUs, cooling fans spinning, and water vaporizing in massive evaporative condensers. The word cloud was always a marketing conceit, borrowed from telecom diagramming where engineers drew wiggly lines to represent telephone networks they could never see. It is a visual shorthand that someone at Cisco drew in 1980s documentation and accidentally became the vocabulary we all use for how modern infrastructure works.

The buildings are enormous and unremarkable, which is part of why we forget about them. A typical hyperscale data center occupies around fifty to one hundred acres, roughly the same footprint as an Amazon distribution warehouse, because they share a lot with one another: vast floor plates, concrete slabs stamped out of farmland near highway interchanges, flat gray roofs in places where electricity is cheap and weather is mild. Northern Virginia, which hosts about thirty percent of the internet infrastructure, has no mountains, no scenery, no reason to attract visitors other than fiber-optic landlines running into a massive crossroads for long-distance phone cables. The architecture says nothing about what happens inside. You would never guess from the exterior that one of those windowless rectangles processes enough queries per second to answer every Google search in the United States within milliseconds.

Inside is cold, aggressively cold. Sixty-five to seventy degrees Fahrenheit, which is the temperature range where heat sinks on server CPUs actually dissipate thermal energy without help from liquid cooling systems. The noise is what hits you first: hundreds of fans whirring in a harmonious drone that sounds like standing next to a massive HVAC system except magnified by fifty. You can feel it in your chest through the floor. This is not metaphor. The low-frequency vibration travels through concrete and metal, registers on your body as pressure. A building full of data centers is physically loud in a way that makes you want to raise your voice without realizing you are doing it.

And then there is the water consumption nobody talks about because the numbers are genuinely hard to hold. A large data center uses roughly one million gallons per day for cooling alone, and that is four million cubic meters annually, equivalent to about two thousand residential households. Some facilities in arid regions of Arizona or Nevada operate in areas where local water authorities have already declared drought emergencies. The irony is thick and completely unnoticed: the same infrastructure that lets people communicate across continents while simultaneously consuming enough water to threaten the communities around it exists without anyone calling attention to the contradiction because the building has no windows and nobody lives next door.

I think about this in connection with something else I noticed recently: how many of us treat going paperless as a moral victory for the environment when the servers processing those digital documents consume more electricity than the paper they replaced. Every email you send generates roughly 0.03 kilograms of carbon. Tiny individually, enormous as a species. The physical world is always hiding behind whatever abstraction you are currently using to describe it. The cloud has water bills. It has HVAC maintenance schedules. It has repair trucks driving across Nevada on sandy roads to replace fans that broke because sand got in the bearings.

What makes this interesting is not just that I know this fact now and could not un-know the abstraction. It is what it reveals about how language shapes our relationship with infrastructure. We talk about the cloud the way medieval people talked about the heavens, as if something invisible held everything together and operated according to laws we could observe but never access directly. Only in this case, the invisible system has addressable geography, real supply chains, and failure modes that are entirely ordinary physics rather than divine will. Every time a data center goes offline, it does not feel like nature withdrawing its favor. It feels like nothing happened at all because there are no physical signs of disruption you can perceive without checking your screen.

This is why I think the metaphor matters more than we realize. If we describe infrastructure as cloud, we never question what it costs to keep running. We never ask who needs the water cooling those server racks. We never notice that the abstraction itself was designed by marketers and engineers whose job was literally to make the physical world feel less present, so that the people paying the electricity bill would stop asking about where their data actually lived.

The solution, if there is one, is not to stop using technology because it has an address. It is to recognize that everything digital is also physical. Every query travels through a cable, every stored photo warms a room, every uploaded video spins a fan somewhere on earth. Naming it honestly does not fix the problem but might make us notice who pays for it and whether we would build something differently if we knew where it lived.