A short story about buildings, fiber, power and why infrastructure deserves more imagination.
We use the word cloud because “large buildings full of very expensive computers” never really caught on.
Unfortunately, the computers remain stubbornly physical.
The metaphor is wonderfully convenient right up until somebody has to choose a site, negotiate power, design cooling and decide how many fiber routes are enough fiber routes.
For people using a product, none of that should be visible. For the people building the product, pretending it is invisible is how avoidable constraints become expensive surprises.
That matters because intelligence has an address.
Servers need land. Land needs power. Power creates heat. Heat needs cooling. Cooling may need water. The building needs fiber. Hardware ages. Batteries age. Materials eventually have to go somewhere.
Where that address sits affects latency, resilience, cost and environmental impact. A workload that needs to respond in milliseconds has different needs from one that can wait. A region with abundant low-carbon power creates different options from one under grid stress.
The physical system is not separate from the software strategy. It is the part of the software strategy that happens to need electricians.
Once you see the whole system, sustainability becomes an engineering problem instead of a marketing adjective.
Where should the facility sit? What energy is available? How much water should it use in that climate? Can waste heat serve another purpose? Can equipment be repaired or redeployed? Can the building eventually be taken apart without turning itself into a landfill?
There are no impact-free data centers. There are better and worse choices: climate-appropriate cooling, thoughtful water use, cleaner energy where available, high utilization, longer equipment life, reuse and material recovery.
The honest goal is not to make infrastructure disappear. It is to create more useful capability with less avoidable impact.
We think the next generation of computing infrastructure should be designed with the end in mind.
Not because data centers can become impact-free. They cannot. Because scale creates an obligation to understand the impact and reduce it where engineering makes that possible.
And then there is fiber.
A beautiful AI interface is still remarkably unimpressive if the network behind it cannot move the information. Which is why eFind’s infrastructure thinking starts on Earth long before it starts talking about orbit.
Fiber is the quiet connective tissue between facilities, exchanges, cities and eventually edge locations. Redundant routes matter because a network is only as resilient as the backhoe operator who does not know the route is there.
This is why our long view starts on Earth. Orbit may eventually add reach or resilience, but the first kilometre of serious infrastructure thinking is usually buried in the ground.
Less magical than “the cloud.”
Considerably more useful.