Meilleur matériel serveur domestique 2026
Comment choisir CPU, RAM, stockage et alimentation pour un serveur domestique efficace et fiable, avec des recommandations pour chaque budget.
Choosing home server hardware comes down to one question: what will this machine actually run, and for how many years? Buy for that, not for a spec sheet. A server runs 24 hours a day, so the right machine is quiet, efficient and boring — not the fastest one on the shelf.
This guide walks through every decision in the order it matters: workload, CPU, RAM, storage, networking, power protection and running cost. At the end you will find three example builds and a checklist to run through before you buy.
Step 1: Start with your workload
Write down the services you want to run in the next year. Hardware requirements follow directly from that list.
| Workload | What it needs | Typical hardware |
|---|---|---|
| DNS filtering (Pi-hole), a VPN, a few small containers | Almost nothing; 1–2 GB RAM | Raspberry Pi 4/5, old laptop |
| File sync, photos, notes (Nextcloud, Immich) | 4–8 GB RAM, fast storage for databases | Intel N100/N150 mini PC |
| Media server (Jellyfin/Plex) with 1–3 streams | Hardware transcoding (Intel Quick Sync) | Intel mini PC with an iGPU |
| NAS with redundancy and snapshots | RAM for ZFS, several SATA ports | Small tower or 2–4 bay NAS chassis |
| Virtualization, labs, many VMs | 32 GB+ RAM, 6+ cores | Ryzen mini PC or small tower |
If you are unsure, start small. Containers are light, and it is cheap to migrate to bigger hardware later, because everything you configure lives in a few Compose files and a backup. See our beginner's guide for how to plan the first project.
Step 2: CPU — efficiency beats raw power
For a machine that runs around the clock, idle power draw matters more than peak performance. Most of the day your server is waiting for something to do.
- Intel N-series (N100, N150, N305): idle around 6–10 W for a complete mini PC, enough to run dozens of containers, and include Quick Sync hardware video transcoding. This is the default recommendation for a first server.
- Intel Core (8th gen and newer): more headroom, good Quick Sync, still efficient when idle if the platform is well chosen. Used small-form-factor business PCs from Dell, HP and Lenovo are a great value here.
- AMD Ryzen mobile chips (in mini PCs): the best choice when you want many VMs or heavy CPU work. Idle power is a bit higher than N-series but usually still modest.
- Raspberry Pi 4/5: fine for DNS, a VPN and light services. Limited I/O, no hardware transcoding of modern codecs on the Pi 5, and SD card storage is a reliability risk, so boot from an SSD.
Hardware transcoding matters if you stream media to phones or TVs that cannot play your files directly. An Intel iGPU handles several 1080p transcodes for a handful of watts, which is why Intel is popular in Jellyfin and Plex builds. If you only stream to devices that direct-play your files, you do not need it.
Step 3: RAM — the first limit you hit
RAM is the first resource a growing home server exhausts, especially with virtual machines or ZFS.
- 8 GB: fine for Docker with a media server and a handful of apps.
- 16 GB: comfortable for most self-hosting stacks and a few small VMs. This is the sweet spot for most people.
- 32 GB or more: for ZFS with larger pools, many VMs, or databases and search indexes.
Two practical notes. First, check whether the RAM is upgradeable or soldered; many thin mini PCs solder it. Second, ECC memory protects against silent bit flips and is nice to have for a NAS holding irreplaceable data, but it requires a supporting CPU and motherboard and is not essential for home use if you keep good backups. More on that in our ZFS primer.
Step 4: Storage — separate the OS from your data
Use two tiers:
- A small, fast SSD for the operating system, containers and databases. A 250–500 GB NVMe or SATA SSD is plenty. See the best SSDs for a home server and best NVMe drives.
- Large hard drives for bulk files and media. Buy CMR (conventional recording) drives rated for NAS use, and avoid SMR drives for RAID or ZFS because their sustained write performance collapses during rebuilds. See the best NAS hard drives.
Plan capacity with room to grow, and plan redundancy separately from backup. RAID keeps a service running when one drive fails; it does not protect you from deletion, ransomware, a failed controller or a fire. Read RAID explained and build a backup strategy before you commit to a layout. The storage planner and RAID calculator help you size a pool.
Step 5: Networking
Gigabit Ethernet is enough for most home servers. Consider 2.5GbE if you move large files between a NAS and a fast client, because it is now cheap and many mini PCs include it. Remember that every device in the path — NIC, cable, switch and the other machine — must support the higher speed. If you plan to run a firewall or router VM, look for a machine with two Ethernet ports. Our networking guide and switch buying guide explain the options.
Prefer wired connections for the server itself. Wi-Fi works for experiments, but latency, drops and power-save quirks make it a poor choice for something other people depend on.
Step 6: Power protection and cooling
A UPS prevents data corruption during outages and lets the server shut down cleanly. It is cheap insurance for a machine holding data you care about. Choose a unit sized in watts with a few minutes of runtime and USB monitoring, then configure automatic shutdown. See the best UPS units.
For cooling, small passively cooled or low-power machines are the easiest to live with. Give any server some airflow, keep it off carpets, and check drive temperatures from time to time with SMART monitoring. Our monitoring guide shows how.
What it costs to run: the math
Electricity is the largest lifetime cost of an always-on server, so calculate it.
Annual cost = watts ÷ 1000 × 24 × 365 × price per kWh
A machine idling at 10 W uses about 88 kWh a year. A machine idling at 60 W uses about 526 kWh. At a price of 0.30 per kWh, that is roughly 26 versus 158 per year. The 50 W difference pays for a more efficient machine in a couple of years. Use our power consumption calculator with your own electricity price, and read how to reduce your server's power consumption.
Three example builds
These are starting points, not exact shopping lists. Prices change often, so check current listings.
| Build | Hardware | Good for | Approximate idle power |
|---|---|---|---|
| Starter | Raspberry Pi 5, SSD boot, 8 GB | Pi-hole, VPN, notes, a few containers | 3–6 W |
| All-rounder | Intel N100/N150 mini PC, 16 GB, 500 GB NVMe, plus one or two USB or SATA drives | Docker, Jellyfin with transcoding, Nextcloud, Immich | 8–12 W |
| Power user | Ryzen mini PC or small tower, 32–64 GB, NVMe plus 2–4 CMR drives, 2.5GbE | Proxmox, ZFS, many VMs, a full media stack | 20–45 W |
For specific mini PC models and what to look for, read our mini PC buying guide.
Used enterprise gear: is it worth it?
Old rack servers are cheap and plentiful, and they teach you real datacenter skills. They are also loud, hot and can idle at 100 W or more. For a home that is a cost you pay every month. A used office small-form-factor PC usually gives you 80 percent of the capability at a fraction of the power and noise. Buy rack gear when you want to learn enterprise tooling, have somewhere to put it, and accept the running cost.
Pre-purchase checklist
- Does it idle at a power level you are happy to pay for every month?
- Is the RAM upgradeable, and does the board support the capacity you may need?
- Does it have an M.2 or SATA slot for the OS drive and room for data drives?
- Is there a 2.5GbE or dual Ethernet port if you need it?
- Does it have an Intel iGPU if you plan hardware transcoding?
- Can you set the BIOS to power on after a power failure?
- Do you have a UPS and a backup plan ready?
Match the hardware to your goals, prioritise efficiency and RAM, and always add a UPS and a backup plan. When you are ready for the software side, continue with choosing a home server operating system.
Articles connexes
Réduire la consommation de votre serveur domestique
Conseils pratiques pour diminuer la facture électrique sans sacrifier fiabilité ni performances.
How to Choose the Right Home Server OS
Ubuntu Server, Debian, Proxmox, TrueNAS, Unraid or CasaOS? Compare the options by skill level, hardware and goals, with a decision guide and migration tips.
Qu'est-ce qu'un serveur domestique ? Introduction simple
Une explication pour débutants : ce qu'est un serveur domestique, ce que vous pouvez en faire et comment décider si vous devez en construire un.