Intel N100 Mini PC Homelab: Home Assistant, Proxmox, Plex and NAS

There are two common ways to install it. Write the generic x86-64 image straight to the SSD and the box becomes a dedicated appliance. Or run Home Assistant OS as a virtual machine under Proxmox, which keeps the rest of the hardware free for other jobs.

• Bare metal: simplest; the whole box is Home Assistant.
• Proxmox VM: 2–4GB assigned, the USB radio passed through, snapshots before every update.
• Docker container: works, but loses the add-on store that Home Assistant OS provides.

Zigbee, Z-Wave and Thread radios plug in over USB. Use a short USB extension cable to move the stick away from the box, since USB 3.0 ports are known to interfere with 2.4GHz radios.

Camera work is the heavier end. Frigate can use the N100's integrated GPU through OpenVINO for object detection, and its media engine for decoding camera streams, which keeps a few cameras within the chip's means.

Four cores without Hyper-Threading set the scale. A few light VMs and a dozen LXC containers run comfortably; several busy Windows VMs do not. Containers share the host kernel and cost far less memory than full VMs, so lean on them.

• 16GB: Home Assistant, a Linux VM and several containers.
• 32GB: room for an OPNsense VM and a Windows guest besides. Only possible on SO-DIMM boxes.
• 12GB soldered: fine for containers; a hard ceiling for anything more.

A multi-port firewall box makes the most of VT-d. On the CWWK 4-port, two Intel i226-V ports can go to an OPNsense VM while the others serve the host, turning one 6W box into router and server at once. The N100 firewall guide covers the port layouts.

The integrated GPU can be passed to one VM, or shared with LXC containers for Plex or Jellyfin. Sharing through a container is simpler and keeps the GPU available to several services.

Store VM disks on NVMe rather than eMMC or a USB drive. Proxmox writes steadily to its boot disk, and cheap flash wears faster under that pattern.

Direct play costs almost nothing: the server just sends the file. Transcoding happens when a client cannot play the original format or needs a lower bitrate, and that is where Quick Sync earns its place. An N100 handles several simultaneous 1080p transcodes, with the exact count depending on source format, tone mapping and client mix.

• Plex: hardware transcoding requires a Plex Pass subscription.
• Jellyfin: free, with Intel QSV and VA-API support.
• HDR to SDR: tone mapping on the GPU is supported on Linux and adds load, so 4K HDR sources transcode fewer streams at once.

Memory type matters slightly here. DDR5 and LPDDR5 boxes feed the GPU faster than DDR4 ones, which helps when several streams run at once. For a single household, any N100 does the job.

Older Celeron boxes, the J4125 and N5105, lack AV1 decode entirely. As streaming services and home libraries move to AV1, that gap is the strongest reason to pick an N100 for a media server.

The HKUXZR board runs one SATA port from the chip and five from a JMB585 controller, a common and well-supported combination in TrueNAS and Unraid. It needs an ATX power supply with 24-pin and 4-pin connectors, and a Mini-ITX case with drive bays.

• 2.5GbE tops out at 312.5MB/s raw, which is about what one modern hard drive delivers.
• ZFS wants direct SATA, not USB enclosures that hide drive health.
• Hard drives add several watts each at idle, often more than the N100 itself.

For a small flash NAS, a two-slot box such as the OUMAX is enough: mirror two NVMe drives and share them over SMB. For bulk media on hard drives, go to a board. Board builds get their own breakdown in the N100 motherboard guide.

Network drivers are the other check. Intel i226-V controllers use the igc driver, built into Linux, FreeBSD-based OPNsense and pfSense. Realtek RTL8125 2.5GbE chips, found on some firewall boxes, work well on Linux and are the less trouble-free choice on BSD-based firewalls.

1. Install headless. Ubuntu Server, Debian or Proxmox, managed over SSH or a web interface.
2. Check the GPU. The render device should appear under /dev/dri before setting up transcoding.
3. Enable power management. powertop's auto-tune often trims idle draw.
4. Set Wake-on-LAN and auto power-on in the BIOS for remote recovery.
5. Back up the configuration of every service to another machine.

A fanless box suits a closet if air can move around it; a fan-cooled box suits a shelf where a faint whir does not matter. Power draw at idle, typically around 6–10W for the whole system, is covered in the N100 power consumption breakdown.

For a first homelab, start with one socketed 16GB box. Home Assistant, Proxmox, Plex and a few containers all run on it, and the box you outgrow becomes the backup node.