$300 in the Basement vs. $1,500 a Month in the Cloud

We needed a second shared development box. We call them “Cloud Dev” machines with real IP addresses where a few of us can collaborate on a codebase, stand up a staging environment, or just experiment without stepping on each other. I was provisioning “Cloud Dev 2”.

So I went pricing it out. A modest server, 8 GB of RAM and a couple of vCPUs, runs roughly $40 to $80 a month at the American hosts: DigitalOcean, Linode (now Akamai), EC2. Hetzner is far more reasonable, single-digit dollars for the same shape, but the tiers I wanted were sold out (* UPDATE: Hetzner updated their prices in mid-June, and is no longer dramatically cheaper). I took a Hetzner box and moved on, but it left a bad taste. For the price of a Raspberry Pi, four real cores and 16 GB of RAM, I was renting one month of half that. The competition wasn’t producing competitive prices. I had a nagging sense I could do better.

The shopping trip

I went looking on the secondhand market, and the secondhand market delivered.

Facebook Marketplace had someone offloading retired HP StoreVirtual nodes. I picked them up for a little under $60 each. eBay had a meaningfully better CPU, about 50% faster, for $35 I bought a matched pair. Then 256 GB of matched server RAM for $200.

Tally it up. For under $300, plus a weekend of elbow grease, I have a server with:

• ~384 GB of RAM
• 20 physical cores / 40 hyperthreaded
• room to spare for the team to run dev and staging environments side by side

The math that made me grin

Running cost first, since that’s the part people forget. A box like this sips somewhere in the 200–300 watt range around the clock. Even at the high end, and at a not-cheap $0.17/kWh, that’s roughly $300–450 a year to power. Call it well under $500.

Now the comparison. The closest equivalent on a major cloud, something with around 40 vCPUs and 384 GB of RAM, is an instance like AWS’s r6i.12xlarge: 48 vCPU, 384 GB, $3.02 an hour on demand. That’s about $2,200 a month. Even priced conservatively against a cheaper provider, you’re north of $1,000 a month for that footprint.

So: under $300 once, plus under $500 a year to run, against more than a thousand dollars every month in the cloud. The hardware pays for itself in under a week of equivalent rental.

The honest part

This is the stewardship blog, so here’s where it doesn’t pencil out. The gear is old. DDR3 is “slow”¹. There’s no SLA but the one I provide, no other availability zone, and the redundancy story is whatever I build myself. It lives in my basement, which means I own the power, the cooling, and the noise². None of that is the right answer for a customer’s production workload, where managed infrastructure earns its keep.

But for development, staging, internal tools, and experiments, the workloads where you want lots of room and don’t need five nines, paying cloud rates is just lighting money on fire. The convenience is real. It is also, for this kind of work, wildly overpriced.

There’s a sustainability angle here too, and it’s the same one we keep coming back to: a perfectly capable machine got retired because an appliance reached end-of-life, not because the silicon stopped working. A little reuse turned e-waste into the most cost-effective box we own.

The fun part came next, which was getting it to do something the cloud charges a premium for: running a frontier-class AI model locally, with no GPU. If your cloud bill has crept somewhere uncomfortable and you want a clear-eyed second opinion on what actually belongs there, we’re happy to talk.