The reference hardware combines a machine for local inference with an optional hardware KVM for controlling a separate computer. Running Ember does not require a KVM.
Inference host
OtherU's reference machine is a Framework Desktop with AMD Ryzen AI Max+ 395, Radeon 8060S graphics (gfx1151), 128 GB unified memory, NVMe storage, and native Linux. The internal deployment runs Fedora 44.
CPU and GPU share physical memory. The amount available for a model still depends on firmware reservations, driver limits, context size, and other running software; the full installed capacity is not a guaranteed model budget.
Ember targets Strix Halo specifically. See Setup and Deployment for the supported software stack and storage requirements.
Hardware KVM
A JetKVM captures the target computer's display over HDMI and delivers keyboard and mouse input over USB. The target uses its normal display and HID interfaces, so the control path does not require an agent installed in the target operating system.
The agent receives screenshots through its configured KVM integration, sends relevant images to a vision-capable model, and uses tool calls to deliver input. Image understanding belongs to the model; capture and input delivery belong to the device and integration.
Access boundary
Hardware control carries the authority of the target's active session. It can interact with applications, files, and administrative screens available to that session. Restrict access to both the KVM management interface and the agent tools that control it.
Device-specific setup is covered in the JetKVM documentation. The Security Model explains the broader trust boundaries.