Skip to main content

Architecture

System design and topology overview.

Verification Status​

FieldValue
Last verified2026-01-24
OSUbuntu 25.04 (Resolute Raccoon)

Network Topology​

Internet
│
▼
┌─────────────┐
│ UDM SE │
└─────────────┘
│
├── Management
├── Servers
├── IoT
└── Guest

Compute​

Primary Node: sudoflux​

ComponentSpecification
Hostnamesudoflux
CPUAMD Ryzen 9 9950X (16C/32T)
RAM96GB DDR5
GPUNVIDIA RTX 4090 (24GB)
BootSamsung 980 PRO 2TB (NVMe)

Roles:

  • Docker host (all services)
  • Media transcoding (NVENC)
  • AI/ML workloads

Secondary Node: powerflux​

ComponentSpecification
Hostnamepowerflux
OSWindows 11
CPUAMD Ryzen 9950X3D
RAM64GB DDR5
GPUNVIDIA RTX 5090

Roles:

  • VR gaming
  • Development workstation

Network Equipment​

DeviceRole
UDM SERouter, firewall, controller

Storage​

ZFS Pools​

PoolTopologyCapacityUsedPurpose
tankSingle vdev (expandable)58.4TB30.9TB (52%)Bulk storage, media
nvmepoolStripe (2x NVMe)3.6TB438GB (11%)Fast storage, containers

Physical Drives​

DriveSizePurpose
4x Seagate ST16000VE00216TBtank pool
2x Samsung 9100 PRO4TBnvmepool (future)
Samsung 990 PRO2TBnvmepool
Samsung 980 PRO2TBnvmepool / boot

See ZFS Gotchas for configuration details.


Service Stack​

ServicePurposePort
JellyfinMedia streaming8096
SonarrTV management8989
RadarrMovie management7878
ProwlarrIndexer management9696
SABnzbdDownload client8080
PrometheusMetrics9090
GrafanaDashboards3001
OllamaLocal LLM11434
Open WebUILLM interface3000
ImmichPhoto management2283

Design Rationale​

Single Node​

Simplicity over redundancy for home use. Critical data protected by ZFS + offsite backup, not hardware redundancy.

Docker over Kubernetes​

Single node doesn't benefit from K8s orchestration overhead. Compose provides sufficient service management.

ZFS​

Data integrity via checksums, snapshots for rollback, compression for efficiency. Worth the RAM overhead.


Revision History​

DateChange
2026-01-24Initial document with current specs