Skip Navigation

What are the minimum or recommended requirements for a personal home server?

I want to set up a home server and take advantage of everything it can offer, specialty privacy.

Raspberry PI, no matter the version, are all quite expensive here in Brazil, so that's off the table. I'll go for a regular desktop. But the the requirements for a server that "does it all" remains a mystery to me.

What specs do you guys recommend?

98 comments
  • Anything that does the job is good enough. At its core a server is just a regular PC with a dedicated purpose and software. Sure, there are specialized hardware better suitable and purpose built, but it's not a requirement.

    I for one prefer 19" rackmount stuff with disk bays in the front, but that's more of a convenience than anything.

    UPS is nice, but it'll work without it.

    I've had to deal with the Brazilian computer market and how it's ridiculously overpriced due to import fees, so in your situation I'd just get any hand-me-down computer. Servers generally don't require much unless you're doing something special or intensive.

    Get your hands on whatever you can find for free or dirt cheap (laptop or desktop doesn'tmatter), install linux, and you have a basic setup that you can work with. If your use case requires more, then that's something you can accommodate in the next iteration of your server.

    • This.

      Almost all of my gear is bought used: switches, server, even memory. My main server is an old Dell C6100 blade server I got for $250. My disk array is a 12-bay SAN that I found for $50 and took a chance on being able to get it working. It’s power hungry but it’s got redundant everything and I have spare parts on the shelf next to it.

      I’ve been branching into ARM servers a little and right now I’ve got an RK3588 board with 32G of RAM. That’s new (and expensive for me) but I got a fibre channel array for $20 that I’m going to try to make work with it. $8 FC HBA and a $12 cable along with a $30 m2-to-PCIe adapter intended for eGPUs. I’m not going for speed here, but used data centre equipment is nice and some of it is dirt cheap because it’s too slow for “real” work.

  • What are you intending to run on this server?

    • If it is just PiHole, you can basically get the weakest computer you can find.
    • If you want lots of storage space, you will need to make sure you have a case and motherboard that will accommodate the drives.
    • If you are running encryption on those drives as well, you will need a CPU more powerful than what comes in a Pi, but nothing crazy.
    • If you are running lots and lots of VMs, you will want lots of RAM. A linux VM will use maybe a few GB each depending on what software each is running internally, a windows vm will use a bit more.
    • If you are doing AI workloads, you will need a graphics card.
  • Raspberry PI

    This also shouldn't be your default option. Your default should be whatever you have laying around, and a lot of people have a Raspberry Pi sitting idle, hence why people use them.

    What specs

    That depends on what you want to do with it.

    For example, if you want to host a video server, then you'll want something that can handle transcoding. Check the Jellyfin docs for details, which recommends an N100 or better.

    List all the things you need and want, and then look up what the requirements are. Basic file hosting is pretty light, so you really don't need much (hence the Raspberry Pi rec).

    I personally use an old PC with the following specs:

    • Ryzen 1700
    • 16GB RAM
    • GTX 750 Ti GPU
    • 2 8TB HDDs (bought for the server)
    • 1 SSD for boot (128 GB, just needs to store the OS)

    This is way overkill for what I need, but I had it laying around. You could even start with a laptop, you'll just have limited storage (can get a USB emclosure of you want).

    If you don't have something, maybe a mini PC would work (minisforum, beelink, etc). Or maybe it doesn't. I don't know what you're planning to run on it. You probably don't need anything fancy, your biggest requirement might be the GPU/iGPU if you're planning to do transcoding.

  • I highly recommend you try proxmox to get the most potential out of you system. Basically can run many services and vm with little overhead, dynamically sharing the specs.

    Now about those specs… what everybody else said really but heres some pointers:

    You don't need a big dedicated gpu unless your doing something that explicitly demands it. They are tricky to setup with virtual machines also.

    If you plan on running a minecraft server i recommend at least 8gb ram. Most will probably run fine on 4. You can probably run quite a few things on 8gb but ram is cheap and its nice to have some extra room.

    For cpu, the more things you do the More sense it makes to have more cores. If you plan on buying then amd ryzen x y z is you best option where.

    X is the number you want higher Y is a number you should not care about as much Z is potentialy the letter “G” for graphics, they are often more expensive. Get them anyway because now you dont need a dedicated gpu (and even if you already own a gpu. Trust me you will thank me if that one ever has issues)

    If you really want me to draw you something decent up that will give you plenty of freedom to experiment.

    Ryzen 7 … G, 32gb ram. Small ssd for os. xTB of performence HDD ideally configured as some raid in proxmox.

    It still cannot be said often enough that a (well cared for) second hand unlabeled laptop running ubuntu is all what most people need when they start pondering about home servers.

  • a potato computer can be a server if the workload is light enough.

    i had a core 2 duo era pentium with 2gb of ram as a server once and it did the job. minecraft server for 6 people + pihole + file server.

    core 2 duos are dime a dozen in brazil and are probably more powerful than some older RPIs. you can probably get something newer too.

    • x86 will decimate most arm chips

      The new stuff is a bit more debatable but old stuff it isn't even a fight

  • Basically none. Grab whatever device you have on hand and install Docker on it.

  • As long as it's capable of booting into Linux, then you can start building a homelab...

    Initially I had a 2-bay Synology NAS, and a Raspberry Pi 3B... It was very modest, but enough to stream media to my TV and run a bunch of different stuff in docker containers.

    In my house, computer hardware is handed down. I buy something to upgrade my desktop, and whatever falls off that machine is handed down to my wife or my daughter's machines, then finally it's handed down to the server.

    At some point my old Core i7-920 ended up in the server. This was plenty to upgrade the server to running Kubernetes with even more stuff, and even software transcoding some media for streaming. Running BTRFS gave me the flexibility to add various used disks over time.

    At some point the CPU went bad, so I bought an upgrade for my desktop, and handed my old CPU donown the can, which released an Intel Core i5-2400F for the server. At this point storage and memory started to become the main limiting factor, so I added a PCI SAS card in IT mode to add more disks.

    As this point my wife needed a faster CPU, so I bought a newer used CPU for her, and her old Intel Core i7-3770 was handed down to the server. That gave quite a boost in raw CPU power.

    I ended up with a spare Intel Core i5-7600 because the first motherboard I bought for my wife was dead, so I looked up and found that for very cheap I could buy a motherboard to match, so I upgraded the server which opened up proper hardware transcoding.

    I have since added 2 Intel NUCs to have a highly available control plane for my cluster.

    This is where my server is at right now, and it's way beyond sufficient for the media streaming, photo library, various game servers, a lot of self-hosted smart home stuff, and all sorts of other random bits and pieces I want to run.

    My suggestion would be to start out by finding the cheapest possible option, and then learn what your needs are.

    What do you want your server to do? What software do you want to run? What hardware do you want to connect to it? All of this will evolve as you start using your server more and more, and you will learn what you need to buy to achieve what you want to.

    • How complex is migrating the whole thing for a the new setup when upgrading? The best I can get with my current budget probably resembles the "quality" of your second server(first upgrade).

      While on your firstly upgraded server, were there limitations to any of your self-hosting desires? Things that were only possible on your following upgrade? That's my main concern. I'm probably over thinking things, it will be my first home server, I'll probably stick the simple stuff at first.

      Right now I want to host movies, photos, automatic backups, files in general. Also use it for the smart home that I'm slowly putting together, basic stuff... for starters.

      • The only true "roadblock" I have experienced was when running on the raspberry pi, where the CPU was too slow to do any transcoding at all, and the memory was too small and unupgradable to be able to run much at the same time.

        As soon as I had migrated to a proper desktop (the i7-920) I could run basically everything I would regularly want. And from then on it was a piece of cake upgrading. Shut the machine down, unplug, swap the parts, plug in, turn on. Linux has happily booted up with no trouble with the new hardware.

        Since my first server was a classic bios, and the later machines was UEFI, then that step required a reinstall... But after the reinstall, I actually just copied all the contents of the root partition over, and it just worked.

        The main limiting factors for me has been the amount of memory, the amount of SATA connectors for disks, and whether the hardware supported hardware transcoding.

        For memory, ensure the motherboard has 4 sockets for memory, that makes it easy to start out with a bit of memory and upgrade later. For example you could start out with 2x 4GB sticks for a total of 8GB, and then later when you feel like you need more, you buy 2x 8GB sticks. Now you have a total of 24 GB.

        For SATA ports, ensure the motherboard has enough ports for your needs, and I would also strongly recommend looking for a motherboard with at least 2 PCIe 16x slots, as that will allow you too add many more SATA or SAS ports via a SAS card.

        Hardware encoding is far from a must. It's only really necessary if you have a lot of media in unsupported formats by the client devices. 95% of my library is h.264 in 1080p, which is supported on pretty much everything, so it will play directly and not require any transcoding. Most 1080p media is encoded in h.264, so it's usually a non-issue. 4k media however often come in HEVC (h.265), which many devices do not support. These files will require transcoding to be playable on devices that do not support it, but a CPU can still transcode it using "software transcoding", it's just much slower and less responsive. So I would consider it a nice convenience, but definitely not a must, and it depends entirely on the encoding of the media library.

        EDIT: Oh, I just remembered... Beware of non-standard hardware. For example motherboards from Dell and IBM/Lenovo. These often come with non-standard fan mounts and headers, which means you can't replace the fans. They also often have non-standard power supplies, in non-standard form factors, which means that if the power supply dies, it's nearly impossibly to replace, and when you upgrade your motherboard you are likely forced to replace the power supply as well, and since the size of the power supply isn't standard, the new power supply will not fix in the case... Many of their motherboards also have non-standard mounts for the motherboards, which means that you are forced to replace the case when upgrading the motherboard... You can often find companies selling their old workstations for dirt-cheap, which can be a great way to get started, but often these workstations are so non-standard that you practically can't upgrade them... Often the only standard components in these are harddrives, SSDs, optical disc drives, memory, and any installed PCIe cards.

  • I'm running an old Igel M340C thin client to run a lot of stuff, from Jellyfin to AdguardHome. Perfectly enough.

  • If you aren't planning on running a media server go for a old desktop or laptop (with Ethernet port). Your bottleneck will be your network speed 9 time out of 10. Also use a firewall and a anti scrapper (ex: Anubis) to avoid wasting resources.

  • raspberry pi's arent the best option anyway since you need to add on a hat just to get some SATA ports. i think Odroid has some boards with sata connectors. zimaboard or zimablade are some other options off the top of my head

  • But the the requirements for a server that “does it all” remains a mystery to me.

    "All" can include anything. I mean, you can include a home parallel compute render farm that will cost millions of dollars.

    You're going to have to narrow it a bit down. You can have people maybe suggest some of the things that they use their systems for. Maybe it's hosting services for a cell phone that some people use cloud-based services for. Maybe it's home automation. Maybe it's a webserver. Maybe it's AI image generation.

    EDIT: To put it another way, a self-hosted server is just a computer, often without a monitor and keyboard directly attached, that you have in your physical possession. The range of things that that might be used for and capabilities it might have is really broad. It's like saying "I want a vehicle. What is a vehicle that can do everything?" I mean, that might be a bicycle or a three-trailer road train, depending upon what you're going for.

    • You can build a render farm for not all that much money. You will pay a very high electric bill but other than that it is possible.

      • I mean, you can build a render farm on a single Raspberry Pi if you want, technically.

  • I'm using my old desktop from 2010. There's no such thing as a server that can "do it all", but any computer from the last 10 years would probably be a fine place to start. The more you do, the more likely you'll be to hit some sort of performance limit, and by that time you'll know more about what you actually want.

    In short, find old cheap/free hardware and start playing around.

  • Rather than give you specific recommendations, here's some guidance for parts

    Mobo: The more slots you have for RAM and storage, the better.

    CPU: literally anything. More cores and faster cores are ideal, but CPU requirements for these things are generally lower than a desktop.

    RAM: Buy 1 stick of the fastest and highest capacity RAM your motherboard can handle. When you're ready or you start to see slowdown, buy another of the same stick. You can get far on 16-32GB, you won't need much more until later.

    Storage: an SSD for the OS and one or more HDDs for storage.

    PSU: generally anything in the 500-700 range will be good. You'll want more if you plan to put a GPU in, though.

  • I live in Brazil too and bought a R$120 old HP computer running Windows XP on MercadoLivre. Works decently enough for a Minecraft server after an upgrade (4 to 8GB of RAM). Old computers are great for price and they're good if you can upgrade them.

    For general purposes, get something better than what I bought since it is not the fastest (even though it runs the Minecraft server software alright, it still lags). Maybe upgrading with an SSD would help performance.

  • Do you have access to Raspberry Pi clones like Orange Pis etc? They’re often cheaper and you can order them straight from China.

  • I run about thirty services off of an old Dell workstation that I “acquired” from my last corporate job. That includes a full Servarr stack. I’m pretty sure whatever you have will probably do the trick.

  • Literally any old PC is likely fine. It may be slow, it may struggle or even fail with some of the very complex software (perhaps you will encounter timeouts, or you will spend so much time waiting for memory to swap in or out to disk that it won't be worth using) but you can run Linux itself on a potato and if your machine isn't powerful enough, maybe you can get a second one and run different stuff on each, or just scale down your expectations and don't try to self-host LITERALLY everything just because you can. Certain services are very intense, others will run on a very small piece of a potato.

98 comments