People have asked what the hardware is that the Shield 399 is running, so here it is...
The host is an ASUS NUC 15 Pro running an Intel Core Ultra 7 255H (16 cores) with 96 GB of RAM and either 1 or 2 TB of NVMe storage depending on configuration. Networking comes with it: WiFi 7, Bluetooth 5.4, and 2.5G Ethernet. That's the computer doing the actual forensic work, the hashing and imaging and searching.
The interface is its own computer. The touchscreen runs on an Arduino GIGA R1 with an STM32H747XI microcontroller, a dual-core Arm chip with a Cortex-M7 at 480 MHz and a Cortex-M4 at 240 MHz, plus 16 MB of external flash and 8 MB of SDRAM. It handles the display and touch input, so the host isn't wasting time drawing buttons. Splitting it this way took more engineering than putting a monitor on a PC, but it means the interface stays responsive.
There's also a second, smaller status display next to the main touchscreen. It just shows status: source, destination, and utility drive counts and write-protection state, and while jobs are running it switches to a queue monitor showing what's active and what's pending. When you're across the room or sitting at your desk, that's the screen you check at a glance. It's a small thing but I really like it.
Then the USB ports. Each one has an assigned role that decides how a connected drive gets handled, and evidence plugged into a source port can't be written to. The ports deserve their own post, so I'll save the details.
The internal storage runs the platform (the software, the database, evidence records, logs). Acquiring a forensic image directly onto internal storage without a destination drive is currently a developer-testing feature and may be added later if there's a need for it. For now, plan on destination drives for your images and output.
The whole thing is a closed unit. It boots straight into the platform, there's no desktop environment, and you never touch an operating system. Everything happens through the touchscreen or the browser.