The Custody Machine:

## Systems & Architecture Review # Local Document Intelligence That Never Leaves the Rack **By Ross Nesbitt** Every vendor currently flogging artificial intelligence to the enterprise is selling the exact same illusion: infinite intelligence in a black box, piped straight out of a multi-tenant cloud data center. For casual text generation or brainstorming session notes, that model works fine. But for the professional who holds other people's confidential material as a condition of doing business—lawyers, medical practices, accountants, and defense subcontractors—handing client files to a third-party API isn't a feature; it is an audit failure waiting to happen. The market has plenty of tools measuring tokens per second. What it has been missing is **custody**. Over the past year, I built the answer: a self-hosted, air-gapped document analysis appliance running entirely on hardware you own, in a room you control, with the cloud path severed at the image level rather than trusting a software policy. Here is how it works, why a small model on modest iron is all you actually need for ninety percent of the workload, and how you can either build your own from these blueprints or have a pre-rolled unit shipped directly to your rack. --- ### Anatomy of the Appliance: Custody Over Cloud The core realization behind this architecture is simple: intelligence is cheap and getting cheaper, but control is non-negotiable. Firms handling sensitive contracts, HR records, and case notes cannot answer client questionnaires with a shrug and a link to a cloud vendor's fluctuating terms of service. To solve this without requiring a venture-capital budget or a cluster of water-cooled accelerators, the system is segmented into practical hardware tiers: * **The Entry Tier (Z240 SFF, 8 GB RAM):** Deliberately modest. Running a 1.5B model with no GPU overhead, it yields a first token in about 3 seconds and sustains roughly 23 tokens/sec *(measured)*. It is built for classification, date and entity extraction, routing, and policy flagging. It is slow, private, and cheap enough to test on your own desk before committing real money. * **The Working Tier (Z230, 32 GB RAM, SSD):** The sweet spot for full adversarial analysis using 7B–14B models, handling the deep analytical lifting where nuance actually matters. * **The Cluster Tier (12 × Z230 in a single rack):** Scaled for heavy overnight corpus processing where interactive latency takes a back seat to raw batch throughput. --- ### The Architecture: A Queue, Not a Load Balancer When building out multi-node processing, traditional web architectures immediately reach for load balancers and round-robin DNS. For overnight corpus processing, where nothing is actively waiting on an interactive HTTP connection, a load balancer only adds a component, a failure mode, and a health-check overhead for zero benefit. Instead, this architecture relies on a fundamental rule: **Nodes pull. Nothing pushes.** A central head unit running Redis manages a single work queue. Consumer nodes run independently, pulling items via a robust `BRPOP` pipeline. A slow node naturally takes fewer items; a dead node takes none; a new node joins the topology instantly without registration or DNS gymnastics. To make multi-node parallelization rock-solid without race conditions, the engine uses **worker-scoped leases** and **per-item claims atomic with selection**. This eliminates the double-processing trap and turns commodity desktop hardware into a synchronized, resilient processing swarm. --- ### Build Your Own or Let Us Roll It For You The complete architecture—from the pipeline scripts and model-tier routing logic down to the provisioning notes—is fully documented for engineers who want to raid eBay for used Z230 workstations, flash the images, and spin up their own local sovereign intelligence grid. If you have the hardware and the time, clone the repository, set up your Redis queue, and run it. If you want a turnkey solution—a pre-configured, hardened appliance delivered to your office with setup, baseline training, and ongoing support backed by decades of enterprise reliability engineering—get in touch. Intelligence belongs to the models. Your data belongs to you.