but it does seem that most homelabs are big server racks with at least two CPUs and like 20 cores in total.
That's just the people that post a lot online about it.
And these racks usually start with "I found this super cheap rack server on eBay" and not an actual need.
And these racks usually start with "I found this super cheap rack server on eBay" and not an actual need.
Hey! I resemble that!
Yep, my homelab started with a laptop (includes a ups!) And as the years went on I build larger and larger. Now that I manage a full rack, I miss my laptop.
The use case is that I want beefy server hardware just because.
I have built a tiny setup in a 10" 6U rack.
It runs a k3s cluster (on dietpi) with a couple of services:
I plan to add more stuff as the need arises. And the rack has 4 more empty slots for further blades.
The total cost so far:
Total ~1050$
Mostly it is a fun learning experience, since I wanted to get better at devops. Also now I can easily use it to deploy my hobby projects (like the website) in a docker container, which makes it more fun than subscribing to a recurrent payment for a server host. Also, since I have it in my home, it doesn't matter if there is an internet outage, I can still access the backups and the data on my nextcloud. As a result my computers are very lean and I can easily replace them without having to think about moving important data from the old machine.
I wouldn't want to get rid of it now.
Whether you need a high power homelab on the other hand is up to your budget and intent. I see it similarely to cars or bikes.
But I think a prebuilt NAS is way more expensive, less flexible and really not worth it unless you really dislike the tinkering aspect.
My take (having neither but building a NAS in the background of other jobs) is that if you don't need the rack, don't buy the rack. If you already have a NAS and you really want to play with the power that a rack would give you, go for the rack. If you don't need it don't buy it, simple as.
I started with a basic as shit NAS and was happy with it.
Then i wanted Hardware Acceleration for my Plex Server because i wanted to stream high resolution content when i was out of the house.
I then rebuilt my old Gaming Rig into a server.
After i realized that i now have much more power to use i started to host a bunch of services; AdGuard, Plex, Sonarr, Radarr, Prowlarr, Overseerr, Homarr, Lidarr, SabNZBs, Kavita, Kaizoku, HomeBox, HomeAssistant, Nextcloud, FoundryVTT, PaperlessNGX, Audiobookshelf, Romm and Whisper for my HomeAssistant.
That's stuff i would've never even had the chance to host on something simple like a little NAS.
Oh and most homelabs are NOT racks with 2 cores.... in my case, old gaming PC with Ryzen 5 2600X, 16Gigs of Ram and GTX1660 Super
Same, my game desktop was so powerful (i9 with 24 cores and 64 RAM DDR5) I converted it to Proxmox, pfSense with a Wi-Fi adapter that creates an access point, I have much more control of my local network and services I host, it's fun and the power usage isn't that much.
Any reason you chose pfSense over opnSense ? I heard opnSense was better or something.
I really want to go down that rabbithole aswell and get myself some real network appliance with 10gig ethernet and take control over my network. I currently have a Fritz!Box by AVM that i bought myself so not via my ISP so it's already fairly controlled and configured by only me... but it has it's limitations; I can't setup PXE boot for example.
Having multiple sufficiently-powered virtual machines makes OS development really low friction. Though I'd personally go for a blade subrack instead.
So, convince me. Why should I get a homelab instead of a regular NAS?
Eventually it just might get out of hand and you end up with both. TLDR at bottom.
Serving out of the home and I've been racking uptime
Gotta gotta add more because I want it all
It started out with a switch how did it end up like this?
It was only a switch, it was only a switch
I started out in college with an old digital sign controller (2 core 4g RAM) and added a hard drive to a slot based on its OEM design and reflashed the bios back to OEM, what it's value-added manufacturer never intended, to get the HDD to work. It was all the right price of free. That became my first NAS. Then I got the switch, then reflashed my router to OpenWRT for features, discovered it couldn't route a gig to NAT anymore, so I did what any logical nerd would do: tried pfsense but ended up building my own Linux based firewall and everything server, also from the free electronics recycling bin. Then my old laptop got converted into a server
Once I got a job and a real budget, I started running into hardware limits. You can only run so much on hardware that is old enough to attend middle school. Out was the homebuilt router-everything server and digital sign NAS, in was the Synology DS1517+ and super micro 8 core mini server and in was the small rack. Settled on ESXi free for a hypervisor. Later, additional nodes were purchased and I upgraded from free to VMUG and added vCenter and vSAN (aggregate size: 1.5TB cache w/ 3TB capacity tier, which worked out to ~2TB total after RAID) to help manage it all. Windows Active Directory was built (had a leftover perma key from college) to coordinate my ever increasing VM count with the same password everywhere.
Timeskip forwards, and I have a pair of R720XD I got for cheap because I knew how to BIOS hack them off of their original Google Search Appliance firmware back to Dell stock, total vSAN capacity at ~8TB after RAID, the Synology is still alive but now rocks ~48TB after RAID, and one "loose" R720 with ~2TB storage and a then-new now-aging Intel NUC with 32GB RAM. All three R720 have 128GB RAM each, I have more switch ports than I'd like to count, and 15 minutes of battery backup added last year. The NAS backups up all devices with a minimum RPO of 1 week and a maximum RPO of 24h for critical stuff. RTO is 2-4h from event, and by golly that has saved my bacon a minimum of 6 times in 3 years. At this point I have more infrastructure redundancy and capacity than some medium businesses.
Could I live without it and it's monstrous power bill? Yeah absolutely I could downsize that and save some cash. But where's the fun in that? Every component I added to my system was done so with a very specific common goal: every piece of this monster was built to help me learn about something IT related. With this experience under my belt, I was able to confidently jump in to stuff at work with the mantra of "yeah I already know how to do this".
Plus, as a side benefit, its a fun learning hobby. I have an absolute blast learning about all this technology and figuring out how to get the most bang for my buck when it comes to selecting software (paid vs FLOSS) and procuring hardware. All things you need to do in the real IT world. Sure I don't get to play with the fancy spaceship servers that have multiple terabytes of RAM each like I do at work, but I don't (yet) need a multi terabyte RAM chassis at home.
Summary and TLDR: Build something that solves a problem in your life. Photo video storage? NAS! Kids want better internet? OPNsense/OpenWRT firewall with a switch! -- as two examples. But my chief most import prime directive rule: build something that makes you and your family happy.
with 1PB of storage
As data hoarder this is a goal to achieve :)
What’s the main advantage of having a huge server, compared to an average Synology NAS for example?
You can do much more things much more efficient. If you're out for a NAS, get a DiskStation, even the simple ones with 2 slots are absolutely fine. Get a Seagate Exos X20 with 20 terabyte of storage, or 2 of them for a RAID, and you're good to go. Or build something yourself with an external case and a Raspberry Pi.
Why should I get a homelab instead of a regular NAS?
Right now I'm using Docker and I'm hosting an ActivityPub server and a front-end (client) for it, a web server, a Minetest gaming server, a web Git platform and a custom application for some specific logging i'm doing. The same server also runs a reverse proxy and a Docker management platform. All on one older SOC machine with a recycled 1TB SSD. I couldn't do this with just a NAS, even if the DiskStations are (were?) very "hackable".
If you want to do anything more than just providing files via network, build a custom setup that fits your needs.
Something I'm not seeing here is many people in the cyber and info security spaces will have a homelab capable of complex configurations in order to mimic enterprise environments for their research.
This could be as simple as a single VM or as complex as multiple segregated networks to try to traverse.
Definitely go for the beefy server. You can then run benchmarks just to flex
Definitely go for the beefy server. You can then run benchmarks just to flex
Although 256gb of ram may not be enought to run matrix synapse.
I was debating between getting myself a NAS or some PC to setup my homelab. I decided for a PC as it gives me more freedom to install and personalize it the way I want.
At the moment I'm running FreeBSD with jails on a Q920 with an i5 processor, 16 GB of RAM, one internal SSD with 512 GB and 2 external USB SDDs with each 1 TB which costed me around 300 Euros.
Seems more than enough for the services I want to provide to myself which are the following.
Navidrome > serves all my music locally and remotely.
Zabbix > to monitor my servers
DNSMasq > ad blocking and local dns
gitea > repo for code and other docs
Transmission > torrenting
Radicale > webcal and webdav
Photoprism > local photo gallery
Vaultwarden > Password manager
SearXNG > search
HAproxy > to serve my public content easily to the web
Mastodon
Emby > local media server
And I run a Linux VM on bhyve to serve 2 tools that I was not able to make work easily on FreeBSD.
Besides that, the node replicates some data from my VPS as a backup solution.
And I can't complain at all. That PC is doing its job just fine. No need for any rack that uses huge amount of electricity.
I felt similar when deciding on a server for my small lab. I'll probably get a rack in a few years, but right now I'm at a point where an old desktop pc does the job and I'm happy with it.
So here's the fun thing:
A small home nas or a plex could easily do what my fileserver 'Enigma' does.
But I built Enigma in 2001. Granted she's had her upgrades and grown from 1tb (princely back in the day!) to 25, but it's the same server.
This is how most of it goes. You see a tech with a giant rig doing something that a smaller commercial unit does nowadays? That didn't exist when the custom rig was built. That's why the rig was built. To fill a need you can't commercially.
Anyway that's storage, my fuckoff ram server runs the nagios and home automation servers and is used to spin up test vms for work : P
Like others have said, it's all about your goals. If you just want to selfhost some apps or have additional storage/local backups, by all means, keep it simple and efficient.
In my case, my homelab is justified because of my job. I'm a senior systems engineer who specializes in designing, deploying, and managing distributed infrastructure. So having a dedicated server room at home with a rack, 20A circuits, and HVAC allows me to more easily emulate certain environments, test out hardware on loan from vendors, experiment with new ideas or software solutions, and stay immersed in my craft.
Aside from the work-related benefits, in return for my higher than average power bill my home network gets to rival most corporations, and I can self host anything I (or my wife) wants.
While this setup is great for me, I would never recommend it for someone who would be better off with a NAS.
The big server is all about density and convenience. The thing will run many, many VMs without having to skimp on resources, and it will be easy to admin the VMs remotely.
I have plans to pick up a big workstation to replace the little desktops I have around, and it will be more convenient since getting as console on a VM is much easier. Servers might also have a BMC, which would help admin the server.
it does seem that most homelabs are big server racks with at least two CPUs and like 20 cores in total.
I'm not sure if your premise is correct, a lot of hardware discussion I see is people repurposing old desktops/laptops or running with sff/mff pc's.
Why should I get a homelab instead of a regular NAS?
In case you want more than just storage like vpn services, hosting containerized applications, etc.
Here's my list of "maybe somedays" that I'd love to have all run off a single machine:
Hash cracking. Red teaming isn't my career yet, but it would be nice if I had the tools ready when I get to that milestone
locally served "Cloud" gaming. I'm tired of being limited to a single desktop when I could be playing skyrim on my phone, but I hate supporting *aaS models—I want to own my cake and eat it too.
VM server. Basically turn everything else into a thin client. Also, what @[email protected] said. If I ever want to do realistic training, and not just stick to hackthebox indefinitely, I'm going to need to mimic a full network's worth of computers with multiple VLANs. Or have multiple different OSes emulated to do all kinds of pentesting.
Finally start those Mastodon/Matrix/Lemmy/every other federated app instances that I've been right around the corner from hosting for ages
media server
Websites and web-apps, even if only locally served. Possibly have copies of wikipedia and archive.org and other highly usefulness-to-power-consumption ratio sites for when I eventually go off grid
maybe email... maybe. I hear it's more of a headache than it's worth, though, so maybe not
home IoT server. Handling all the functionalities so I don't have to stream security cam footage to some random company's untrustworthy server across however many hops along the way
and probably a few other ideas i've had over the years that I can't think of at the moment.
Could I accomplish all this on a couple powerful towers and a half dozen smaller/cheaper/more power efficient devices? Certainly, but this reduces cables, network overhead, and weird edge case problems having that many devices on a single-maintainer network causes. Instead of dealing with updating, upgrading, and hardening a dozen or more devices, this would give me a single point of failure that I can build resentments against whenver it has a hiccup.