384 GB of VRAM in a basement: one builder's local-AI server is Minecraft for adults

On September 5, u/suspect80 posted a build log to r/LocalLLM: "Local AI is Minecraft for adults: my 4× RTX PRO 6000 Blackwell build." It drew roughly 450 upvotes and 360-plus comments — among the subreddit's most-discussed threads in weeks. The subject is Cerebro: a 5U rack server with four Nvidia RTX PRO 6000 Blackwell Max-Q GPUs and 384 GB of VRAM in total, built to run personal AI agents on hardware its owner controls. This is a story about money, learning, and what happens when local AI stops being a laptop question.

What Happened

Cerebro did not appear fully formed. The post traces a familiar escalation: a MacBook, then a gaming PC with an RTX 5090, then a Mac Studio M3 Ultra with 96 GB of unified memory — the machine class Apple has since pushed to 1.2 TB/s in the M5 Ultra Mac Studio, covered here in late August. Each step ran bigger models with less friction, until the last one: stop renting time on hardware in someone else's datacenter.

"Built a 5U local AI server with 4× RTX PRO 6000 Blackwell Max-Q GPUs (384 GB total VRAM) to run models for my personal AI agents. It started as an attempt to reduce API costs and turned into a hardware hobby." — suspect80, r/LocalLLM

Cerebro's purpose is not a single chatbot but a team of personal agents handling coding, research, tool use and experiments with memory and delegation. Software-wise, the author started with OpenClaw and then built an open-source harness, somora: MIT-licensed, a "local-first gateway for personal AI agents with persistent memory across multiple LLM providers," written with heavy assistance from the agents it runs. Each agent has its own role and memory, they share a long-term wiki, and tasks route to local or cloud models depending on the job. Cerebro did not retire the older machines either: the RTX 5090 PC and Mac Studio stay in the setup, running what fits each best.

Why the thread resonated is in the title:

"Local AI really does feel like Minecraft for adults. You build one thing, it needs another thing, and eventually you're explaining why the basement needs 384 GB of VRAM."

The Build

The shopping list reads like a quote sheet from a server vendor:

• GPUs: 4× NVIDIA RTX PRO 6000 Blackwell Max-Q, 96 GB each — 384 GB total VRAM
• CPU: AMD Threadripper PRO 9965WX, 24 cores / 48 threads
• Motherboard: ASUS Pro WS WRX90E-SAGE SE
• Memory: 256 GB (8×32 GB) Kingston DDR5-5600 ECC RDIMM
• Case: SilverStone RM52 5U rackmount
• Cooling: SilverStone XE360-TR5 360 mm CPU AIO
• PSU: Seasonic PRIME PX-2200 (2200 W)
• Storage: Samsung 990 Pro 1 TB + 2 TB NVMe, Crucial T705 4 TB NVMe

The economics deserve a moment of silence. The RTX PRO 6000 Blackwell Max-Q is a 96 GB GDDR7 workstation card on the GB202 die — and memory shortages have pushed its street price far past launch. The card debuted around $8,000 in early 2025; by mid-2026 it was selling above $13,000, and NVIDIA's own listing has since climbed to $16,000. Four cards at today's money can cost more than a new car before the Threadripper platform, ECC memory and rack chassis add a five-figure premium. The author knows what this looks like:

"Financially, this has become a hobby and a learning project. The original we'll save money argument did not survive contact with the hardware shopping list."

He adds, drily: "I am deliberately not calculating the break-even date." Whatever API bill started this journey was a rounding error by the time the rack arrived.

What 384 GB Does — and Doesn't — Buy

The headline number deserves the usual skepticism, and the builder would agree with most of it. Four 96 GB cards do not make one 384 GB pool. The VRAM is not shared: what actually runs depends on the inference engine, model distribution across cards, and whether the stack supports multi-GPU tensor parallelism. That means sharding weights, scheduling layers and accepting communication overhead.

Memory is the wrong thing to count alone. Long contexts and the KV cache eat capacity that looks abundant on paper, and a team of agents means concurrent requests competing for the same silicon. The Max-Q cards are 300 W blowers, so four of them plus a 2200 W power supply turned cooling, power draw and noise into first-class design constraints. On all of this, the author's summary is the most useful paragraph in the thread:

"Fitting a model is only the beginning. Context length, concurrent requests, inference-engine support and cooling all matter. More VRAM also makes it very easy to invent more workloads."

He ends asking readers what their real bottleneck became once VRAM stopped being the first one — the thread's 360-plus comments are largely the community's answers.

What This Means

Read as an investment, Cerebro is indefensible, and its owner says so. Read as a signal, it is more interesting: local AI is splitting into two camps. Unified-memory machines — Apple's Mac Studios, Framework's 192 GB desktop — suit people who want one very large model in a single address space. Multi-GPU rigs like Cerebro suit people who want many models and concurrent agents, and will pay the tensor-parallelism tax for that flexibility.

The same wave that pushed frontier API pricing out of hobby budgets is pushing tooling down. A year ago, "local agents" meant a laptop running a small model through a chat interface. Now hobbyists build role-based agent teams with persistent memory, shared wikis and per-task model routing — infrastructure problems once reserved for companies with GPU clusters. somora — 416 commits, an author who admits agents helped write it — is an early attempt to make that manageable for one person.

The honest takeaway: nobody should buy four 96 GB workstation cards expecting to save on API calls. But that this segment exists — builders writing their own orchestration software instead of waiting for a vendor — says where local AI is heading. The bottleneck for serious local inference stopped being hardware availability. It is software maturity now, and hobbyists are writing that software themselves.

Conclusions

Cerebro is less a story about Nvidia's hardware than about what people now build with it. One builder spent car money to run agents in his basement; hundreds of comments trading notes on context limits and engine quirks suggest he describes a real phase of the hobby, not an outlier. Local AI has moved from "can it fit on my desk" to "what infrastructure do I want to maintain" — a different question entirely.

The thread's practical advice is the builder's own lesson: buy memory for the workloads you actually run, not the ones you can invent. Start with one capable card or a unified-memory machine, learn where context length and concurrency bite, and treat the hardware as a hobby budget, not a savings plan. The break-even date is not the point — he is not calculating it.