Building a Home Lab From Salvaged Server Parts

This is the full build log of the Chromewire home lab, assembled from parts rescued from an office clearance. It is long, so we split it into two pages.

The Fine Print

Home labs start with a single machine and a vague plan, then expand to fill every shelf in the apartment. The appeal is freedom: a place to break things without consequences, to learn how services really fit together, to host your own photos and calendars instead of renting them. Salvaged enterprise hardware makes it cheap to start, though the power bill can be a rude surprise. The builders we met treat their labs as ongoing experiments. Nothing is ever finished, documentation is always slightly out of date, and something is always blinking amber.

Open-source tools changed the economics of making things. A decade ago, a small studio needed expensive licences before it could render a single frame or edit a single minute of footage. Now a determined team with donated hardware can produce work that stands next to studio releases. The catch is labour. Free software is free to download, not free to maintain, and the communities behind it depend on volunteers who juggle bug reports with rent. The healthiest projects we know treat documentation as seriously as code, pay contributors when they can, and say thank you often.

The hardware of the future looks a lot like the hardware of the past, only smaller and harder to open. Enthusiasts building their own portable computers, the chunky cyberdecks that fill social feeds, are partly reacting to that trend. They want machines with visible screws, replaceable batteries and keyboards that can survive being dropped. Many of the builds are impractical, but they carry a serious message. People are hungry for technology they can understand, modify and repair, and the industry keeps selling them sealed slabs of glass instead of tools they can own.

• Two rescued 1U servers
• One fanless switch
• A secondhand UPS with new batteries
• Four drives from a clearance bin

services:
  photos:
    image: photoprism/photoprism
    restart: unless-stopped
    ports:
      - 2342:2342

Lessons From the Street

Cooling is the invisible cost of computation. Every calculation turns into heat, and that heat has to go somewhere. Large facilities pump it into towers that steam gently at dawn, while smaller operators crack windows and hope for a breeze. Engineers are experimenting with piping waste heat into nearby swimming pools and greenhouses, turning a liability into a neighbourhood amenity. The schemes work best when planners think about them early. Retrofitting a heat network into a finished district is expensive, but designing one alongside a new data centre is surprisingly cheap.

The people keeping the lights on rarely make headlines. They are the technicians who climb poles in the rain, the moderators who clear spam before breakfast, the volunteers who answer the same beginner question for the hundredth time with patience. Our coverage tries to keep them in view, because systems are only as reliable as the care that goes into them. If there is a thread running through everything we publish, it is this: technology is made by people, maintained by people and, when it fails, repaired by people too, usually late at night and without thanks.

Nobody planned the rooftop network. It grew the way ivy grows, one bracket and one borrowed extension cord at a time, until a map of the district looked less like a street grid and more like a nervous system. The early nodes were salvaged routers flashed with community firmware, zip-tied to water tanks and pointed at whichever neighbour had line of sight. Today the mesh carries school homework, pharmacy orders and late-night gossip, and it does so without a single invoice. The people who maintain it rarely call themselves engineers. They call themselves neighbours who got tired of waiting for someone else to fix things.

The data is always more personal than the people collecting it want to admit.

Hye-jin Seo, digital rights lawyer

@@ -12,7 +12,7 @@ server {
 server_name lab.home.arpa;
-listen 80;
+listen 443 ssl;
 root /srv/www;

Numbers That Matter

Ask anyone who has kept a piece of street hardware alive for a decade and you will hear the same complaint: the parts exist, the knowledge exists, but the manufacturer would rather you did not have either. Screws with proprietary heads, glued batteries and firmware that refuses to boot after a component swap are not accidents. They are business decisions. The repair crowd answers with printed guides, shared spare-part spreadsheets and a stubborn refusal to throw anything away. Their workshops smell of flux and instant noodles, and their shelves are lined with labelled bins of screens, ribbon cables and chips pulled from dead machines.

Security people like to say that the weakest link is always human, but that framing lets a lot of badly designed systems off the hook. When a login screen trains people to click through warnings, when a password policy guarantees sticky notes on monitors, the failure started in a design meeting long before anyone made a mistake at a keyboard. The best defenders we interviewed spend less time lecturing users and more time removing traps. They shorten the path to doing the right thing, they log everything that matters, and they assume that anything exposed to the network will be probed within hours.

The night markets run on trust that would make an auditor faint. Vendors lend each other power cables, split the cost of a shared generator and settle debts with a handshake and a promise to cover the next shift. Payment happens on cracked phones, in cash, and occasionally in favours that are hard to price. Tourists see the neon and the steam and the noise. Regulars see a finely tuned economy where everyone knows who sells the best dumplings, who can unlock a phone in ten minutes, and who should never be asked about where the stock came from.

Open Questions

Power is the quiet dependency underneath every other story we cover. The grid in this city was designed for a cooler climate and a smaller population, and every summer it reminds us of that fact. Transformers cook, substations trip, and entire blocks go dark just as air conditioners are needed most. The utility publishes cheerful statements about resilience, but the maintenance backlog tells a different story. Engineers we spoke to described replacing equipment older than they are, rationing spare parts between districts, and watching demand charts climb toward numbers the network was simply never built to carry.

Surveillance rarely arrives as one big decision. It accumulates. A camera goes up after a burglary, a licence plate reader follows a grant application, a transit card starts logging trips because the data might be useful someday. Each step sounds reasonable in isolation, and by the time anyone draws the whole picture the infrastructure is already paid for and wired in. That is why the most effective campaigns we have seen start with a map. When residents can see every lens pointed at their front door, the conversation shifts from abstract privacy rights to something personal and immediate.

There is a particular kind of silence in a data centre at three in the morning. The fans never stop, so it is not quiet exactly, but the humans are gone and the machines carry on without supervision. Operators describe the night shift as long stretches of boredom punctuated by moments of pure adrenaline. A disk array degrades, a cooling unit throws an alarm, a routing change on another continent sends traffic somewhere it should not go. The job is to notice early, act calmly and write down everything, because the morning team will want to know exactly what happened.

Open a terminal with Ctrl+Alt+T, then search your shell history with Ctrl+R.

Why It Matters

Biohacking has a reputation problem, mostly earned by a handful of people who injected untested things on camera. The community labs we visited are nothing like that. They are cramped, well organised and slightly obsessive about safety data sheets. Members run workshops on extracting DNA from strawberries, calibrate secondhand centrifuges and argue about ethics over cheap coffee. The work is slow, careful and often boring, which is exactly the point. What they want is access: to equipment, to knowledge and to a seat at the table when the rules about bodies and data are written.

Every city has a layer of infrastructure that nobody notices until it breaks. Here it is the tangle of copper and fibre running beneath the old telephone exchange, a building that officially closed years ago but still carries a surprising share of the district’s traffic. Contractors refer to it as the graveyard because so much abandoned cable remains in the ducts. Removing it would cost more than leaving it, so the dead lines stay, wrapped around the live ones like roots. Mapping what is still connected has become a hobby for a small group of retired technicians.

The arcade restorers work in a warehouse lit by the glow of attract screens. Each cabinet arrives with a history: water damage from a flooded basement, cigarette burns from a bar that closed in the nineties, a monitor that crackles when it warms up. The restorers replace capacitors, redraw faded side art by hand and trade circuit boards across three continents. They could run the same games on a laptop, of course, but that misses the point. The weight of the joystick, the hum of the tube and the queue of people waiting their turn are part of the software.