Box by Future Industries
moves a homelab/sovereignty decision from "what should I buy?" to "here's the bill of materials, here's why, here's where to source it."
Recommended tier
The two Box tiers
Two operational profiles, two use cases. Tier 3 (Headless Bunker) is in spec and ships v2.
Why this shape
About the build philosophy
Used > new at the same price. Five-year-old enterprise gear is 80% of current performance at 20% of new price. ECC RAM is non-negotiable for ZFS — without it, you're betting the integrity of the storage pool on consumer-grade memory error rates. Dual-socket NUMA isn't an exotic optimization; it's a way of physically separating workloads. Compiled-for-your-CPU (-march=broadwell, -march=skylake-avx512) extracts free performance from chips that are already paid for.
About sovereignty
The Box is the minimum viable unit of digital sovereignty. ZFS at the storage layer, LDOS at the OS layer, Box at the hardware layer. Each layer's redundancy is independent of the layers above. A wagon (Box) carries buckets (drives); the wagon makes the buckets transportable as a unit. The shape that matters isn't "data center" — it's "I can hand-carry the whole thing if I need to."
About power and noise
Both reference platforms idle in a workstation-class envelope and full-load in a datacenter-class envelope; rack chassis are louder but more power-efficient per useful cycle. There's no free lunch: the quiet tier costs more per watt of work; the loud tier costs more in decibels and heat. Pick by where the Box lives, not by where you wish it lived. (Sourced watt and dB numbers pending — see plan Decision H.)
About cold spares
Not just drives — spare PSUs, RAM modules, HBAs, boot NVMes. The same availability-decay doctrine that applies to disks applies to chassis components. Buy your second HBA when you buy your first; that model goes EOL faster than you think, and replacement at year three may mean a different SKU.
About dive-buddies
Two Boxes is the smallest fault-tolerant configuration. ZFS replication (zfs send | zfs receive) is the irrigation mode; physical bucket migration is the hardware-guy mode. Sometimes you start with one Box and add the second later; sometimes you start with two. The dive-buddy doctrine is structural to operating sovereign storage — single-Box configurations have an honest single-point-of-failure budget.
When something breaks
Drive recovery: see Bucket's recovery doctrine. PSU / HBA / motherboard failures are different — in-place replacement is the standard play. The Box's hardware redundancy is the dive-buddy pair, not single-chassis component duplication.
Box vs. the alternatives
Up-front column shows rough order-of-magnitude bands for orientation; specific Box numbers ship once the BOM scan lands (see footer disclosure).
| Option | Up-front (order) | Sovereignty | Capacity ceiling | Where it fits |
|---|---|---|---|---|
| Synology DS920+ / QNAP TS-453D | low-$$ + drives | Low (DSM lock-in) | 4 bays | Family with limited tech depth |
| Cloud-only (Backblaze B2) | $0 capital, ongoing | None (vendor) | Unbounded | Strong bandwidth; willing to rent forever |
| New self-built (Newegg, B&H) | highest one-time | Full | High | Newer tech but multiple-× cost vs used |
| Box by FI (used enterprise + LDOS) | mid one-time | Full | High | Sovereignty at homelab+ scale |
| Used Synology / QNAP | low one-time + drives | Medium | 4–6 bays | If you want turnkey |
| Managed by FI | $0 capital, monthly | Full (FI-operated) | Scales with plan | If you want the Box without operating it |