Building a Budget Intel N100 Homelab: The Ultimate 2024 Guide
Build a powerful, energy-efficient homelab with Intel N100 mini PCs and Proxmox. Complete guide with parts list, setup steps, and real-world performance.
Table of Contents
- Why Intel N100 for Homelabs?
- Key Specifications
- What Makes It Special?
- Popular N100 Mini PC Options
- My Recommendation: Beelink EQ12
- Hardware Setup
- Parts List
- Physical Setup
- Installing Proxmox VE
- Download and Create Boot Media
- BIOS Configuration
- Installation Steps
- Initial Configuration
- Essential First Steps
- 1. Network Configuration
- 2. Storage Configuration
- 3. CPU Configuration
- Running Your First VM
- Creating a Linux VM
- Running Docker Containers
- Performance Benchmarks
- Power Consumption
- VM Performance
- Common Services to Deploy
- Home Assistant
- Media Server Stack
- Troubleshooting Common Issues
- Boot Issues
- Network Problems
- Performance Issues
- When to Upgrade
- Conclusion
- What’s Next?
Building a Budget Intel N100 Homelab with Proxmox
The Intel N100 processor has become the darling of the homelab community in 2024, and for good reason. This tiny powerhouse delivers quad-core performance at just 6W TDP, making it perfect for running multiple virtual machines and containers without spinning up your electric meter. In this comprehensive guide, we’ll walk through building a complete homelab using Intel N100 mini PCs with Proxmox VE.
Why Intel N100 for Homelabs?
The Intel N100 (Alder Lake-N) represents a sweet spot that didn’t exist before. Until recently, you had two choices: power-hungry desktop CPUs or underpowered ARM boards. The N100 changes that equation entirely.
Key Specifications
| Specification | Intel N100 |
|---|---|
| Cores/Threads | 4C/4T |
| Base Clock | 0.8 GHz |
| Boost Clock | 3.4 GHz |
| TDP | 6W |
| Cache | 6MB L3 |
| Architecture | Alder Lake-N |
| Process | Intel 7 (10nm) |
| GPU | Intel UHD (24 EUs) |
What Makes It Special?
Power Efficiency: At 6W TDP, you’re looking at roughly $15-20 per year in electricity costs running 24/7. Compare that to a typical 65W desktop CPU that would cost $150+ annually.
Surprise Performance: Despite the low power, the N100 handles surprising workloads:
- Home Assistant with dozens of integrations
- Pi-hole + Unbound for network-wide ad blocking
- Plex/Jellyfin media server (hardware transcoding supported!)
- Multiple Docker containers via Portainer
- Development VMs and test environments
- Lightweight Kubernetes clusters (k3s)
Quick Transcode Support: The integrated GPU supports Intel Quick Sync Video, making it excellent for Plex/Jellyfin hardware transcoding. This feature alone makes it worth considering for media enthusiasts.
The N100’s Quick Sync Video support means you can transcode multiple 1080p streams simultaneously with minimal CPU overhead. This was previously only available on much more expensive hardware.
Popular N100 Mini PC Options
Several manufacturers have released N100-based mini PCs at attractive price points. Here are the most popular options:
Parts Used
| Component | Model | Price |
|---|---|---|
| Total | $0 | |
* Prices are approximate at time of purchase. Links may include affiliate commissions.
Be careful with models that have soldered RAM (like Chuwi LarkBox X). While LPDDR5 is faster, you won’t be able to upgrade later. For Proxmox, prioritize models with upgradeable DDR4 SO-DIMM slots.
My Recommendation: Beelink EQ12
After extensive testing, the Beelink EQ12 stands out for several reasons:
- Dual NVMe slots - Run Proxmox on one drive, VMs on another
- Upgradeable RAM - Two DDR4 SO-DIMM slots, supports up to 32GB
- Dual 2.5GbE ports - Perfect for network-intensive workloads
- Active cooling - Runs cooler than passively cooled alternatives
- Excellent Linux support - Well-documented community experience
Hardware Setup
Parts List
Here’s everything you’ll need for a complete setup:
Parts Used
| Component | Model | Price |
|---|---|---|
| Total | $0 | |
* Prices are approximate at time of purchase. Links may include affiliate commissions.
You can start with stock configuration and upgrade later. The base 8GB RAM and 256GB storage is sufficient for learning Proxmox and running light workloads.
Physical Setup
-
Unbox and Inspect: Check for any shipping damage. Verify ports and cooling vents are clear.
-
RAM Upgrade (if applicable):
- Power off and unplug
- Remove bottom screws
- Locate DIMM slots
- Insert new RAM at 45° angle, press down until clicks
-
Storage Installation (if adding second NVMe):
- Locate M.2 slot
- Insert NVMe at 30° angle
- Secure with mounting screw
- Replace thermal pad if included
-
Network Connection:
- Connect to your primary network via LAN1
- Reserve second 2.5GbE port for future expansion
Installing Proxmox VE
Proxmox Virtual Environment (VE) is the perfect hypervisor for N100 mini PCs. It’s free, open-source, and offers both VM and container (LXC) virtualization.
Download and Create Boot Media
# Download Proxmox VE ISO (use latest stable)
wget https://downloads.proxmox.com/proxmox/iso/proxmox-backup-server_3.2-1.iso
# Create bootable USB (Linux)
sudo dd if=proxmox-backup-server_3.2-1.iso of=/dev/sdX bs=4M status=progress && sync
# On Windows, use Rufus or Etcher
This guide uses Proxmox VE, not Proxmox Backup Server. Make sure you download the correct ISO: proxmox-ve_*.iso
BIOS Configuration
Before installing, configure the BIOS properly:
- Enter BIOS (usually F2 or Delete during boot)
- Enable Virtualization: Intel VT-x and VT-d must be enabled
- Disable Secure Boot (Proxmox works better without it)
- Set Power Profile: Performance or Balanced
- Boot Order: Set USB as first boot device
Installation Steps
-
Boot from USB drive
-
Select “Install Proxmox VE” from menu
-
Accept EULA
-
Select target disk (your primary NVMe)
-
Configure:
- Country/Time Zone: Set appropriately
- Keyboard Layout: Your preference
- Admin Password: Create strong password
- Email: For important notifications
- Hostname: Something like
pve-n100.local - Network: DHCP is fine for initial setup
-
Wait for installation (5-10 minutes)
-
Reboot and remove USB
Initial Configuration
After installation, access the web interface:
- Open browser to
https://[IP]:8006 - Accept self-signed certificate warning
- Login with
rootand your password - You’ll see the Proxmox dashboard
After first login, run the following commands in the Proxmox shell to access the web interface properly:
# Update repositories
apt update && apt dist-upgrade -y
# Remove "No Subscription" popup (optional)
sed -i.bak 's/data.status !== 'Active'/false/' /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js
# Reboot for kernel updates
reboot
Essential First Steps
After installation, configure these critical settings:
1. Network Configuration
Create a proper network bridge for VMs:
# Edit /etc/network/interfaces
auto lo
iface lo inet loopback
auto eno1
iface eno1 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.1.10/24
gateway 192.168.1.1
bridge-ports eno1
bridge-stp off
bridge-fd 0
2. Storage Configuration
Proxmox uses “local” for ISOs and containers, and “local-lvm” for VM disks by default. Optimize for NVMe:
# Enable discard for SSD/NVMe storage
pvesm set local-lvm --content rootdir,images --ssd 1
3. CPU Configuration
The N100’s efficiency cores benefit from specific tuning:
# Install CPU frequency utilities
apt install cpufrequtils -y
# Set to performance governor
cpufreq-set -g performance
# Make persistent
echo 'GOVERNOR="performance"' > /etc/default/cpufrequtils
If power consumption is critical, use “ondemand” or “powersave” governor. This reduces idle power by ~2-3W but may impact burst performance.
Running Your First VM
Now for the fun part - creating virtual machines!
Creating a Linux VM
-
Download ISO: Upload a Linux ISO to Proxmox
# Download Ubuntu Server directly to Proxmox cd /var/lib/vz/template/iso/ wget https://ubuntu.com/download/server/thank-you?version=22.04.3 -
Create VM:
- Click “Create VM” in top right
- General: Give it a name (e.g., “docker-host”)
- OS: Select your uploaded ISO
- System: Defaults are fine (Qemu Agent enabled)
- Disk: 32GB is plenty for a Docker host
- CPU: 2 cores, type “host” for best N100 performance
- Memory: 2048MB minimum, 4096MB recommended
- Network: vmbr0, VirtIO
-
Start and Install:
- Click Start
- Open Console (top right)
- Follow installation prompts
Always use “host” CPU type with N100. This passes through specific CPU features that improve performance significantly.
Running Docker Containers
The real power of an N100 homelab comes from containers. Here’s a quick setup:
# Install Docker on your VM
curl -fsSL https://get.docker.com | sh
sudo usermod -aG docker $USER
# Install Portainer for easy management
docker run -d -p 9000:9000 --name portainer \
--restart=always \
-v /var/run/docker.sock:/var/run/docker.sock \
-v portainer_data:/data \
portainer/portainer-ce:latest
Access Portainer at http://[VM-IP]:9000 and set up your admin password.
Performance Benchmarks
Here’s what you can expect from an N100 mini PC running Proxmox:
Power Consumption
| State | Power Draw |
|---|---|
| Idle (no VMs) | 8-10W |
| Idle (2 VMs) | 12-15W |
| Moderate Load | 18-25W |
| Full Load | 30-35W |
VM Performance
| Workload | vCPU | RAM | Performance |
|---|---|---|---|
| Home Assistant | 2 | 2GB | Excellent |
| Pi-hole + Unbound | 1 | 512MB | Excellent |
| Jellyfin (transcode) | 2 | 2GB | Good (hw accel) |
| Minecraft Server | 2 | 2GB | Good (5-10 players) |
| Kubernetes (k3s) | 2 | 4GB | Good (light workloads) |
The N100 handles multiple lightweight VMs better than one heavy VM. Instead of running everything in one VM, distribute services across multiple smaller VMs or LXC containers for better resource utilization.
Common Services to Deploy
Home Assistant
The quintessential homelab service:
# docker-compose.yml for Home Assistant
version: '3'
services:
homeassistant:
container_name: homeassistant
image: "ghcr.io/home-assistant/home-assistant:stable"
volumes:
- ./config:/config
- /etc/localtime:/etc/localtime:ro
restart: unless-stopped
privileged: true
network_mode: host
Media Server Stack
A complete media server configuration:
# docker-compose.yml for media stack
version: '3'
services:
jellyfin:
image: jellyfin/jellyfin
container_name: jellyfin
environment:
- PUID=1000
- PGID=1000
- TZ=America/New_York
volumes:
- ./jellyfin/config:/config
- ./media:/media
ports:
- "8096:8096"
restart: unless-stopped
sonarr:
image: lscr.io/linuxserver/sonarr:latest
container_name: sonarr
environment:
- PUID=1000
- PGID=1000
volumes:
- ./sonarr/config:/config
- ./media:/media
ports:
- "8989:8989"
restart: unless-stopped
radarr:
image: lscr.io/linuxserver/radarr:latest
container_name: radarr
environment:
- PUID=1000
- PGID=1000
volumes:
- ./radarr/config:/config
- ./media:/media
ports:
- "7878:7878"
restart: unless-stopped
Troubleshooting Common Issues
Boot Issues
If Proxmox won’t boot or shows errors:
- Disable Fast Boot in BIOS
- Disable Secure Boot completely
- Try legacy boot mode if UEFI fails
- Check NVMe is properly seated
Network Problems
If VMs can’t reach the internet:
# Check bridge status
brctl show
# Verify IP forwarding
cat /proc/sys/net/ipv4/ip_forward
# Should return 1
# If not enabled:
echo 1 > /proc/sys/net/ipv4/ip_forward
Performance Issues
If VMs feel sluggish:
# Check CPU governor
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
# Check I/O wait
iostat -x 1
# Check VM balloon driver (increase minimum RAM)
# In VM config: balloon=0
The N100 doesn’t have hyperthreading, so don’t assign more vCPUs than you have physical cores. Start with 1-2 vCPUs per VM and only increase if monitoring shows consistent high usage.
When to Upgrade
The N100 is powerful for its size, but you’ll eventually hit limits:
Consider upgrading when:
- Running more than 15-20 Docker containers
- Needing GPU passthrough for LLM/AI workloads
- Requiring high-performance storage (10GbE+)
- Running multiple transcoding streams (4K)
Upgrade options:
- N305 - 8 cores, still efficient at 15W
- i3-13100 - Significant jump in performance
- Used enterprise gear - Dell Wyse/HP t630 series
Conclusion
The Intel N100 mini PC with Proxmox represents the best bang-for-buck entry into homelabbing. For under $200, you get a capable virtualization host that sips power while running dozens of containers. Whether you’re learning virtualization, automating your home, or building a media server, this setup delivers exceptional value.
What’s Next?
Once you’ve mastered the basics:
- Set up Proxmox Backup Server for automated backups
- Explore LXC containers (more efficient than VMs)
- Consider clustering multiple N100 nodes
- Learn Infrastructure as Code with Terraform/Ansible
Check out the Proxmox Helper Scripts at https://tteck.github.io/Proxmox/ for one-click installation of many popular services. They handle all the configuration automatically!
Resources:
Comments
Powered by GitHub Discussions