Beelink EQ13 (N100) as a Whole Home Server: A Month On

A month of continuous uptime is the point where a mini PC stops being a review unit and starts being infrastructure — long enough for a filesystem to fill up unexpectedly, for a fan curve to reveal itself under real thermal load rather than a synthetic benchmark, and for whatever corners were cut to reach the price point to start showing. The Beelink EQ13 is built around Intel’s N100, the same four-core Alder Lake-N part that’s become the default recommendation for a low-power always-on box, but it’s specced differently to the generic N100 mini PC: two 2.5GbE ports instead of the usual one, aimed squarely at people who want this box doing router, NAS front-end and general self-hosting duty rather than sitting behind an existing switch as just another endpoint.

What’s actually in the box

The N100 is a 6W base TDP part, four cores and four threads, boosting to a little over 3GHz, built on Intel 7 — the same silicon generation underpinning most of the current wave of budget mini PCs, NUC-alikes and fanless firewall boxes. The EQ13 pairs it with LPDDR5 soldered to the board (no user upgrade path on RAM, which is the one spec worth knowing before buying rather than after), an M.2 2280 NVMe slot for the actual storage, and — the feature that sets this specific model apart from the crowd — dual 2.5 gigabit Ethernet ports, each running off its own controller rather than sharing bandwidth through an internal switch chip. Street price for the configuration most homelabbers actually buy sits in the same rough band as other N100 boxes with dual NICs, comfortably under what a low-end NAS chassis costs before you’ve added drives.

None of that is exotic. What makes it worth a dedicated review is how it holds up doing a specific job for a month rather than how it benchmarks in isolation.

Why two 2.5GbE ports change what this box is for

A single-NIC N100 box is a compute node: plug it into your existing network, run services, done. A dual-NIC box is implicitly being sold as something that sits between two networks — most obviously a router or firewall, but just as usefully as a NAS-and-server combo where one port faces the LAN at full 2.5Gb and the second port is reserved for a dedicated backup or storage network, kept separate from general household traffic without needing a managed switch to enforce that separation.

I used it the second way: one port on the general home LAN, the second dedicated to a point-to-point link with a NAS for backup jobs, so a large nightly backup doesn’t compete with anyone streaming video or a video call in progress on the same wire. This is the kind of thing you can also do with VLANs on a single NIC, and I’ve covered segmenting a home network with VLANs as the more flexible general approach — but a genuinely separate physical NIC removes an entire class of “did I get the VLAN tagging right” troubleshooting, at the cost of a port you can’t repurpose without physically rewiring.

Power draw over a full month

A cheap inline power meter left in place for the full month is the only honest way to answer “what does this actually cost to run,” and the shape of the number matched what independent measurements of N100 boxes generally report: idle draw sitting in roughly the 6-9W range with the display off and no active transcode or backup job running, climbing into the high teens under sustained CPU load across all four cores, and briefly higher for a few seconds during NVMe writes on a backup job. Over a full month of genuinely mixed use — mostly idle, punctuated by nightly backup windows and the occasional heavier task — the average sat closer to the idle end of that range than the load end, which tracks with what this class of box is actually doing most hours of the day: answering DNS queries, serving a handful of lightweight containers, and waiting.

At UK electricity prices, an always-on device averaging somewhere in the region of 8-10W works out to roughly £18-24 a year — genuinely trivial next to what an old tower server or a repurposed desktop pulls at idle, and the entire reason N100 boxes displaced older, more powerful but far less efficient hardware for this exact role. The fuller version of that comparison, including where a more powerful older box still wins on raw compute despite the power penalty, is worth reading if you’re deciding between a refurbished business desktop and a new N100 box for the same job — I’ve laid out the actual power-bill maths of mini PCs against old servers and a specific refurb OptiPlex against a new N100 box elsewhere, and the EQ13’s numbers sit right where those comparisons would predict for this class of hardware.

Thermals and fan noise, the part spec sheets don’t tell you

The N100’s low TDP means the EQ13 doesn’t need much cooling, and it shows: the fan is small, runs at a low, mostly inaudible speed at idle, and only becomes noticeably present — a soft whir rather than anything sharp — during sustained load like a backup window with simultaneous container activity. CPU temperatures under that kind of sustained mixed load settled in the 55-65°C range over the course of the month, consistent with the sort of figures independent N100 reviews report for similarly cooled designs, and comfortably away from anything approaching thermal throttling. This isn’t a chip that’s ever going to struggle to keep itself cool; the low core count and modest clocks mean there simply isn’t enough sustained heat generation to challenge a cooling solution this size, which is a large part of why fanless N100 designs exist at all for lighter-duty roles.

What it’s actually running

By the end of the month the box was carrying a fairly typical small self-hosted stack: a DNS sinkhole, a reverse proxy terminating TLS for a handful of internal services, a lightweight monitoring agent, and the backup job mentioned above syncing to the NAS over the dedicated NIC. None of it individually taxes a four-core chip, but running all of it concurrently, plus periodic container image updates, is a more honest test of “whole home server” than any single benchmark:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22

# docker-compose.yml (genericised)
services:
  dns:
    image: adguardhome/adguardhome
    networks: [lan]
    ports:
      - "53:53/tcp"
      - "53:53/udp"
    restart: unless-stopped

  proxy:
    image: caddy:latest
    networks: [lan]
    ports:
      - "443:443"
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile:ro
    restart: unless-stopped

networks:
  lan:
    driver: bridge

Every service sat comfortably within the four cores with room to spare, and CPU usage across the month, sampled via a lightweight dashboard, rarely broke double digits as a percentage of total capacity outside the nightly backup window. That headroom is the practical answer to “is an N100 enough” for this specific mix of duties — plenty, right up until you ask it to do something genuinely CPU-heavy like real-time video transcoding for several simultaneous streams, which is a different workload entirely and one this chip was never marketed for.

First boot and the setup friction nobody mentions in the marketing

Out of the box the EQ13 boots to a stock Windows installation on most retail channels, which the vast majority of homelab buyers immediately wipe in favour of a Linux distribution or a hypervisor. That’s a five-minute job with a USB installer and nothing specific to this board complicates it, but it’s worth knowing going in rather than being surprised that a “server” box ships consumer-OS-first — the dual-NIC, homelab-flavoured marketing doesn’t extend to the out-of-box software.

BIOS access and settings are unremarkable AMI UEFI, with the handful of options that matter for this role — boot order, the AC power-loss behaviour mentioned below, and a fan curve — all present and where you’d expect them. A firmware update was available at the point I set the box up, and applying it was a normal UEFI flash process with no surprises, though it’s worth checking for one before committing to a final OS install, since some early production units shipped with a BIOS revision that had since been superseded specifically around power-state handling.

Storage: what the single NVMe slot actually gets you, and where it doesn’t

The single M.2 2280 slot is the ceiling on this box’s storage ambitions, and it’s worth being honest about what that means in practice. One drive means no redundancy at the hardware level — a failed NVMe drive on this box is a full restore from backup, not a degraded array you swap a disk into and rebuild. For the DNS-and-reverse-proxy-and-monitoring role it was carrying, that’s an acceptable trade: none of those services hold irreplaceable data, and the actual bulk storage and redundancy live on the NAS this box talks to over its dedicated second NIC.

That division of labour is deliberate and worth calling out explicitly, because it’s the honest answer to “why not just use this as your NAS too.” A single NVMe slot with no redundancy is the wrong foundation for anything you’d be upset to lose, and trying to make this box into both the compute layer and the storage-of-record layer defeats the actual advantage of keeping them separate — a NAS with proper redundancy handles the data you can’t regenerate, and a cheap, low-power compute node handles the services that touch that data without needing its own redundant array. If you’re weighing a dedicated NAS chassis against building storage into a box like this one, the trade-offs are laid out in more depth in Synology’s DS423 against a DIY N100 storage build, and the short version is that this box was never meant to compete with that decision — it’s the thing that talks to whichever answer you land on.

Troubleshooting: what actually went wrong

The eMMC-versus-NVMe distinction matters more than the spec sheet implies. Some EQ13 configurations are sold with a small onboard eMMC module in addition to the NVMe slot, and a fresh install occasionally defaults to installing onto the slower eMMC rather than the NVMe drive if the installer isn’t explicitly pointed at the right target during setup — worth double-checking at install time rather than discovering weeks later why disk-bound tasks feel sluggish.

The dedicated backup NIC needed one deliberate step that isn’t obvious from the box: without an explicit static route or a second subnet configured on that interface, the OS’s default routing picked whichever NIC came up first for all outbound traffic, effectively ignoring the second port for anything except traffic explicitly addressed to a host on its specific subnet. Assigning the backup NIC its own subnet, distinct from the primary LAN, and pointing the NAS at that specific address resolved it — the two ports won’t automatically load-balance or fail over between each other without additional configuration such as keepalived or bonding, which is worth knowing before assuming “two NICs” means “two NICs cooperating” out of the box.

The only other genuine friction was BIOS-level: resuming reliably after a power cut required an explicit “power state after AC loss” setting to be changed from its default, which otherwise left the box sitting off after an outage rather than restarting automatically — a one-time fix, but one that would otherwise mean discovering it after an actual power cut rather than before.

Is it worth it for this specific role

For a box whose entire job is DNS, a reverse proxy, light monitoring and backup duty over a dedicated link, a month of real use didn’t surface anything that would make me second-guess the purchase. The dual 2.5GbE is the genuine differentiator over a cheaper single-NIC N100 box, and it’s worth the modest price premium specifically if you have a concrete use for the second port — a dedicated backup path, a small internal-only network segment, or router duty. If your workload is a single NIC’s worth of traffic and no plan to separate anything physically, the extra port is dead weight and a cheaper single-NIC N100 box does the same job for less. For anything approaching real transcoding or heavier compute, this isn’t the chip for it regardless of how many Ethernet ports it has — that workload belongs on a box with a discrete GPU or a more capable CPU, and no amount of networking headroom changes what four Alder Lake-N cores can sustain. What a month of continuous use actually confirmed is the less exciting but more useful thing: nothing caught fire, nothing needed rebooting outside a deliberate update, and the one BIOS setting worth changing was a five-minute fix rather than a recurring annoyance. For a box whose job is to be quietly reliable rather than impressive, that’s close to the best outcome a review can report.