Hardware Configuration

This is the full parts list. Every component was chosen for a reason — no filler, no unnecessary spend.

Component Model Spec Notes
SBC Raspberry Pi 5 8GB LPDDR4X RAM, BCM2712 quad-core Cortex-A76 @ 2.4GHz Official Pi 5 — not a clone
Case Argon ONE V5 M.2 NVMe PCIe Active fan, passive heatsink, GPIO access Designed for Pi 5, exposes full PCIe 3.0
Storage Crucial P310 1TB M.2 NVMe SSD PCIe 3.0 x1 (Pi limitation), ~900 MB/s read Connected via Argon's PCIe bridge — no USB bottleneck
Power Official Raspberry Pi 27W USB-C PSU 5V/5A, PD-compliant Required for stable NVMe + Pi 5 — do not use cheap adapters
Thermal pad Included with Argon V5 Blue thermal pad between board and heatsink Pre-applied during build
Hands-on assembly of the Raspberry Pi 5 into the Argon ONE V5 case
The build in progress — every component seated and secured before closing the Argon case

What We're Running On It

Seven projects, one machine. This is the current stack living on the Pi.

Wealth Command Center
Personal finance intelligence dashboard
PostgreSQL · Grafana
Career Command Center
Job board aggregator, CV prompt engine, LinkedIn tracker
Python · PostgreSQL
Germanos
German language learning automation
n8n · local LLM
E-Commerce Command Center
Order tracking, inventory, and fulfilment automation
n8n · Flask
Pi-hole
Network-wide ad blocking for the whole flat
DNS
Local LLM Inference
Qwen / Llama models for pre-filtering automation pipelines
Ollama
n8n
Self-hosted workflow automation — the glue between every service
n8n

Why Run This Locally?

Seven projects, zero ongoing compute cost. API spend is kept to €9–15 per month by running heavy polling, scheduling, and LLM inference locally. Cloud APIs — Gemini Flash, DeepSeek, Claude — are used only for high-value outputs where quality matters and frequency is low. This machine is the filter layer: it decides what is worth sending to an expensive API and what can be handled on-device.

The stack also runs pgvector inside the same PostgreSQL instance, storing vector embeddings for each automation's outputs. Over time this enables lightweight reinforced learning loops — job match scores improve as the career tracker learns preferences, product recommendations sharpen as the e-commerce center logs conversions, and finance alerts self-calibrate against actual spending patterns. All inference stays local; nothing leaves the machine.

The Build — Key Steps

This build replaced a cloud VM that was costing €15/month and is faster for local inference. Total hardware cost: one-time, already paid for itself in three months.