Intel N100 Mini PC: The Perfect Passive Income Server

Why a $130 N100 box outearns a Raspberry Pi, and how to set it up as a 10W always-on income server with Proxmox or plain Ubuntu.

1. Why N100 beats Pi for earning

The Intel N100 (in Beelink/NiPoGi/AOOSTER boxes) hits the sweet spot for node hosting: 4 efficient cores, 8–16GB RAM options, gigabit ethernet, ~6–10W idle draw, and x86 compatibility — meaning every Docker image just works, including ones without ARM builds. It costs about double a Pi 5 but delivers triple the usable capacity.

Verdict: Pi for learning and single-purpose nodes; N100 when you're serious about stacking multiple DePIN networks.

2. Choose your OS: Ubuntu vs Proxmox

Ubuntu Server 24.04 — simplest path. One OS, Docker Compose stacks, identical workflow to our Pi playbook. Choose this unless you specifically want virtual machines.

Proxmox VE — proper hypervisor. Run multiple VMs/containers: an Ubuntu VM for bandwidth apps, another for DePIN nodes, isolated experiments that can't break each other. Choose this if you enjoy infrastructure or want clean separation between projects.

This playbook follows the Ubuntu path (the Proxmox route ends in the same place: Docker inside a VM). Flash Ubuntu Server to a USB stick with Balena Etcher, boot the N100 from it (F7/Delete for boot menu on most boxes), and install with SSH enabled.

3. Foundation: updates, Docker, firewall

ssh youruser@n100-ip

sudo apt update && sudo apt full-upgrade -y
sudo apt install -y ca-certificates curl git ufw htop
sudo ufw allow OpenSSH && sudo ufw --force enable

# Docker
curl -fsSL https://get.docker.com | sudo sh
sudo usermod -aG docker $USER && exit
# reconnect, then:
docker run --rm hello-world

4. Deploy the earning stack

Same compose pattern as the Pi playbook, scaled up. With 16GB RAM you can comfortably run: Honeygain, Grass, EarnApp, EarnFM, plus a DePIN node or two (Titan, BlockMesh CLI), all simultaneously.

services:
  honeygain:
    image: honeygain/honeygain:latest
    restart: unless-stopped
    command: "-tou-accept -email YOU@example.com -pass PASS -device n100"
    mem_limit: 300m

  earnfm:
    image: earnfm/earnfm-client:latest
    restart: unless-stopped
    environment:
      - EARNFM_TOKEN=YOUR_TOKEN
    mem_limit: 200m

  watchtower:
    image: containrrr/watchtower
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    command: --cleanup --schedule "0 0 4 * * *"

docker compose up -d && docker compose ps

5. Resource guardrails

Bandwidth apps are polite; some DePIN nodes are not. Every service above carries mem_limit — extend that discipline to CPU where needed so no single node starves the rest:

    # per-service CPU cap example (half a core):
    deploy:
      resources:
        limits:
          cpus: '0.50'

Watch actual usage with htop and docker stats. An N100 handles the full stack below 40% utilization in our testing — headroom matters for stability more than efficiency.

6. Remote access & monitoring

You'll want visibility without opening security holes. Options ranked by simplicity:

  uptime-kuma:
    image: louislam/uptime-kuma:latest
    restart: unless-stopped
    ports:
      - "127.0.0.1:3001:3001"
    volumes:
      - ./kuma-data:/app/data

Access Uptime Kuma via SSH tunnel: ssh -L 3001:localhost:3001 user@n100-ip, then browse localhost:3001. Add monitors for each app's dashboard URL.

7. The numbers: what an N100 actually earns

Our reference N100 (residential Australian IP, 16GB RAM) ran the full stack for 90 days:

Electricity cost: ~$2/month. Payback period on the hardware: 4–7 months, after which it's a permanently cashflowing appliance. Scale further by adding VPS nodes per our bandwidth-farm playbook.

Tools used in this playbook

• Grass — ★★★★½ 4.5/5
• EarnApp — ★★★★☆ 4.0/5
• Titan Network — ★★★½☆ 3.5/5