45 questions answered
Frequently asked questions
Short, direct answers to the questions we hear most often, each linking to the guide that covers the topic in depth.
Getting started
What is a homelab?
A homelab is a collection of computers and network equipment you own and control, used to learn and to run services for yourself and your household. It can be one old laptop or a full rack. What makes it a lab is that you are free to build, break and rebuild it. Start with Start Here.
Do I need a rack or a real server to start?
No. A retired desktop, an old laptop or a single mini PC is enough to learn virtualization, containers, networking and backups. Many of the best labs never use a rack at all. Our Shelf Lab fits on one bookshelf and idles at about 50 W.
How much does a homelab cost to run?
Mostly it depends on idle power. Every 10 W that runs all year uses about 87.6 kWh. A small lab of efficient devices may cost well under $100 a year to run, while a rack of older servers can cost several hundred. Measure your devices at the wall and use our Power Cost Calculator. For buying costs too, see Budgeting a Homelab.
What should my first project be?
Pick something you will actually use. Good first projects are a DNS filter for the whole house, a file server with snapshots, a photo library or an uptime dashboard. Each one teaches networking, storage and backups along the way. Whatever you choose, set up its backup before you trust it with data.
Will a homelab help my career?
Often, yes. Hiring managers tend to value evidence of genuine interest, and a documented homelab is exactly that. Put it near the top of your resume and be ready to talk about what broke and how you fixed it. Our field note The Homelab as a Career Lab covers certifications and interviews.
Hardware and power
Should I buy a used enterprise server?
Only if you need what it offers, such as many drive bays, lots of memory or enterprise features to learn on, and you have somewhere for the noise and heat. Used servers are cheap to buy and expensive to run. Read The Real Cost of a Free Server before you decide.
How much memory do I need?
Memory runs out long before CPU in most homelabs. 16 GB is enough to learn on, 32 GB comfortably runs household services plus experiments, and 64 GB per host suits busy labs that run several full desktop operating systems as VMs. See Choosing Homelab Hardware.
Do I need ECC memory?
It is good practice on any machine that holds the only copy of important data, and it comes standard on used servers. It is not a requirement for ZFS or any other filesystem, and its absence is not a reason to avoid filesystems with checksums.
Can a single-board computer run my whole lab?
It can run several small always-on services well, such as DNS filtering, monitoring and home automation. It is a poor choice for storage-heavy work, and many firewall and NAS distributions only run on x86. Use an SSD rather than an SD card, and the correct power supply.
Do I need a UPS?
For anything with spinning drives or a database, yes. A small line-interactive UPS rides through brief outages and gives servers time to shut down cleanly, which prevents corruption. Put your modem, firewall, switch and access points on it first so the household stays online. See Racks, Power and Cooling.
Networking
Do I need VLANs at home?
Not on day one, but they are the most valuable networking upgrade most homes can make. Start with one VLAN for IoT devices with internet access only. Remember that VLANs only separate traffic; firewall rules between them provide the actual protection. See VLANs and Segmentation.
How many VLANs should I have?
As many as you can give a clear purpose and maintain rules for. Trusted, IoT and guest networks cover most homes, with lab, management, camera and storage networks added as the lab grows. One VLAN per device creates more rules than anyone can maintain and breaks casting and discovery.
Should I virtualize my firewall?
It is a great way to learn, but the firewall the household depends on belongs on its own small device. A virtualized firewall takes the internet down every time the host reboots, and leaves you unable to download the fix you need. See Firewalls and Routing.
Is 10 GbE worth it?
Between storage and the machines that move large amounts of data, often yes. For everything else, gigabit is plenty. Inside a rack, used SFP+ cards and direct-attach cables are the cheapest way to get it. Test real throughput before blaming storage for slow transfers.
Why does my wireless still have dead spots?
Usually because one device in a cabinet is trying to cover the whole house. One or two wired access points mounted high and central almost always outperform a more expensive router or a wireless mesh. See Home Network Fundamentals.
Which IP address range should I use?
Use private space from 10.0.0.0/8 or 172.16.0.0/12, and avoid 192.168.0.0/24 and 192.168.1.0/24, which collide with most networks you will connect from over a VPN. Our example plan uses 10.42.0.0/16 with the third octet matching the VLAN ID. Try it in the Subnet Calculator.
Storage and backups
Is RAID a backup?
No. Redundancy keeps you running when a drive fails. Deletion, ransomware, fire, theft, a failed controller and filesystem corruption all reach every drive in the array at once. You need separate, versioned copies. See Backup Strategy.
Should I use ZFS or Btrfs?
For a dedicated NAS with several drives, ZFS is the common choice for its mature redundancy, snapshots and replication. Btrfs is excellent for single-disk systems and workstations, especially with automatic snapshots before updates, but avoid its parity RAID modes for important data. See ZFS and Filesystems.
How full can I let a storage pool get?
Plan to stay below about 80 percent. Copy-on-write filesystems slow down and fragment as they fill, and a pool near 95 percent can become painfully slow. Set an alert well before you get there.
I have two NAS boxes. Do I still need an off-site copy?
Yes, for anything irreplaceable. Two boxes in the same house share the same fire, flood, theft and power surge. An encrypted copy at a relative's house or in cloud object storage protects against all of them.
Should I encrypt my backups?
Encrypt every copy that leaves your home, on your own system before upload. Then store the key somewhere that would survive losing the house, such as your password manager and a sealed paper copy elsewhere. A backup whose key was lost with the server is unreadable.
Virtualization and containers
Should I use containers or virtual machines?
Decide per application. Use containers when the application supports them, for their small footprint and easy rebuilds. Use virtual machines for other operating systems, firewalls, anything that needs its own kernel and services that need strong isolation. Most labs run containers inside a VM. See Containers.
Do I need a cluster?
Most homes do not. Two or three independent hosts with good nightly backups recover from a failure in minutes without the complexity of quorum and shared storage. Build a cluster when you want to learn clustering. See Virtualization.
Do I need a container orchestration platform?
Not for household services. A single, well-backed-up container host is simpler and more reliable. Orchestration platforms are valuable career skills and excellent lab projects, so learn them in a separate area where breaking them costs nothing.
Can I run my applications on my NAS?
You can, and for applications whose job is storage it can make sense. In general we keep the NAS as a storage appliance and run applications on other hosts, because NAS app catalogs often lag behind and every app adds risk to the box that holds your data.
Security and remote access
Is it safe to forward a port to a service?
For management interfaces, remote desktop, SSH, file shares, databases and camera recorders, no. Automated scanners find exposed services within minutes. Reach your lab through a VPN or mesh overlay instead. See Remote Access and VPNs and Keep Management Off the Internet.
Which VPN should I use to reach my lab?
For personal access, a WireGuard VPN on your firewall is fast, simple and well reviewed. If your provider uses carrier-grade NAT, or you want many devices and sites connected, a mesh overlay works without any open ports. Either way, write access rules.
Should I pay for a commercial privacy VPN?
It is useful on untrusted public wireless, for reaching region-restricted content and for keeping experiments from tracing back to your home address. It does not make you anonymous and does not protect weak passwords. A VPN back to your own home often covers the public wireless case for free.
How would I know if my lab was compromised?
Alert on events that should be rare: SSH and admin logins you did not make, new devices, unexpected outbound connections and sustained CPU use on normally idle hosts. Keep logs on a separate machine, scan your public address from outside and audit regularly. See Securing Your Homelab.
Should servers install updates automatically?
Yes, at least security updates, with notifications and scheduled reboots. A broken update is an afternoon of work; a compromised server is a rebuild and a round of password changes. Snapshot before major upgrades so you can roll back.
Self-hosting
Should I run my own email server?
We recommend against it. Residential connections are widely blocked by receiving servers, deliverability needs constant attention and mail servers are heavily attacked. The part worth owning is the domain: put a hosted mailbox on it and you can switch providers without ever changing your address. See our notes on email.
What is a good first self-hosted service?
A photo library with automatic phone uploads is often the most appreciated service in a household, and it teaches storage, databases, reverse proxies and backups. Make sure its backups are tested before the family relies on it. See Self-Hosting Services.
Can AI assistants manage my lab for me?
They are useful for explaining logs and drafting scripts. Give them read-only access at most, sandbox any agent in its own VM and network, keep a human approving every change and never give an assistant a shell on your firewall or NAS. See Local AI in the Homelab.
Projects and learning
Do I need a hypervisor, ZFS or a NAS for my first server?
No. A plain server Linux install with a container engine runs DNS filtering, a password vault, a photo library and file shares perfectly well. Add a hypervisor, ZFS or a separate NAS when you can name the problem each one solves. See Choosing a Platform and Your First Self-Hosting Weekend.
Is 8 GB of memory enough to start?
For one or two small services on hardware you already own, yes. Run a photo library and a media server together and you will hit the limit quickly. For anything you buy, treat 16 GB as the floor and 32 GB as comfortable for several virtual machines, and buy machines with the memory already installed. See Budgeting a Homelab.
Will a hypervisor or ZFS wear out my SSD?
Wear comes mostly from heavy writes such as constant logging, not from ZFS itself. Hypervisors do write a lot, so watch the SSD wear indicator, keep logging at sensible levels and plan replacements before they are urgent. See Maintenance Routine.
Does a home server actually save money?
It can pay for itself within a year if it replaces several subscriptions and you actually cancel them. Electricity, drives and your time all count against it. Try your own numbers in the Payback Calculator.
Should I practice networking on simulators or real switches?
Both, in that order. Simulators and emulators teach most configuration for free; one or two real managed switches teach cabling, console access and how hardware behaves. See Switching and Routing Practice Lab.
How do I keep a security practice lab away from my home network?
Put lab machines on internal or host-only virtual networks, never bridge vulnerable machines onto your real network, and prove the isolation by trying to reach home devices from inside the lab. See Networking and Security Study Lab.
Why does streaming from my media server stutter away from home?
Remote playback is limited by your home connection's upload speed. Lower the remote quality, enable hardware transcoding, or download episodes to the device before you leave. See Home Media Stack.
What if I set everything up wrong and have to start over?
That is normal, and part of learning. Keep data on separate storage, keep configuration in files and keep backups, and starting over becomes an afternoon of reinstalling rather than a disaster. Treat your first build as a learning build.
About this site
Who writes About Homelabs?
Five editors who run homelabs of their own, with backgrounds in systems administration, Linux training, incident response, hardware testing and self-hosting. Every guide is tested on the Bench, our shared test lab. Meet everyone on the About Us page.
Why do you not name specific products or brands?
Products change, get renamed, get acquired and lose support, while the underlying technology and practice last much longer. Describing equipment and software by what it does keeps our guides accurate for longer and keeps us independent of every vendor. See Editorial Standards.
How is the site funded? Is there a newsletter?
The editors fund the site themselves. We carry no advertising, affiliate links or sponsored content, and we do not run a newsletter, accounts, comments or a contact form. That keeps the site fast and private and leaves our time for writing and testing.
How often are guides updated?
Every guide and project is reviewed at least once a year and whenever something important changes. Each page shows its last review date, and the Changelog records what changed and when.
No questions match that filter. Try the glossary or browse the guides.