What we do
About Homelabs publishes practical, independent guidance for people who build and run private homelabs: the computers, networks, storage and services that live in a home and are owned by the people who live there. We cover the whole journey, from choosing a first machine to running services a household depends on, with an emphasis on fundamentals that transfer between products and outlast them. Guides explain how things work, step-by-step projects walk through building them, and reference builds show complete labs measured at the wall.
Everything we publish is meant to be useful to someone standing in front of real equipment. That means specific numbers where we have them, clear trade-offs instead of hype, and honest notes about what has gone wrong for us.
How it started
About Homelabs began in 2019 as a shared notebook between friends who kept answering the same questions for each other: which disks, which layout, why the backups had stopped, why the wireless dropped in the kitchen. The notebook became a wiki, the wiki became a habit, and in 2021 we cleaned it up and published it as this site.
Our backgrounds are deliberately varied. Between us we have spent decades looking after small office networks, teaching Linux administration, responding to security incidents, testing hardware and running self-hosted services for families who expect them to just work. Those perspectives disagree often enough to keep each other honest.
The editors
ME
Mara Ellison
Founding editor
Mara spent two decades as the systems administrator that small offices call when the file server stops answering. Mara writes our networking, firewall, ZFS and backup guides and still keeps a printed copy of the restore runbook next to the rack.
Covers: Networking, firewalls, ZFS, backups, maintenance and out-of-band management
CN
Caleb Navarro
Co-founder and technical editor
Caleb taught Linux administration for years before co-founding About Homelabs. Caleb edits every guide for technical accuracy and believes that any task done twice by hand is a script waiting to be written.
Covers: Linux, DNS, automation, containers and documentation
IV
Ines Varga
Security and monitoring editor
Ines came to homelabs from incident response work and brought the habit of assuming breach. Ines writes our security, remote access, monitoring and troubleshooting material and runs the quarterly audit of the Bench.
Covers: Security, remote access, monitoring and troubleshooting
TB
Theo Brandt
Hardware editor
Theo measures everything at the wall before forming an opinion about it. Theo maintains our reference builds, tests used and older hardware, writes about storage hardware and virtualization hosts, and owns more power meters than anyone needs.
Covers: Hardware, power and cooling, storage hardware, virtualization hosts and reference builds
WH
Wren Halvorsen
Self-hosting editor
Wren runs the services a household actually uses, from photo libraries to the automation that turns the porch light on. Wren writes about self-hosting with one test in mind: would the least technical person in the house be happy with it?
Covers: Self-hosted services, home automation and local AI
A small group of contributors and technical reviewers helps us check facts and test procedures, and every guide is reviewed by at least one editor other than its author.
The Bench
Every guide on this site is tested on the Bench, our shared test lab. It is a modest twelve-unit open rack in a basement, plus a desk covered in power meters:
- A dedicated fanless firewall appliance and a managed switch with 10 GbE uplinks, plus a small separate switch for management interfaces.
- Two short-depth hypervisor hosts with management controllers. They are deliberately not clustered; if one fails, its VMs are restored onto the other.
- A self-built eight-bay ZFS NAS for primary storage, and a separate turnkey four-bay NAS that pulls nightly backups with its own credentials.
- A single-board computer running uptime monitoring, a serial console server and remote keyboard and video access.
- Off-site copies kept at a family member's house and, for the most important data, in encrypted cloud storage.
When a guide says "on the Bench", this is what it means. Hardware we test and then return or pass on is measured on the same desk with the same meters.
Independence and funding
About Homelabs is funded by its editors. We do not carry advertising, affiliate links or sponsored content, and we do not accept payment or conditions in exchange for coverage. When we test borrowed equipment, nobody outside the team sees our conclusions before they are published.
That independence is also why we describe hardware and software by what they do rather than by brand. Our Editorial Standards page explains the policy in full.
What we do not do
We keep the site simple on purpose. There are no accounts, comments, newsletters, contact forms or tracking scripts. Every hour we do not spend moderating, answering a queue or managing personal data is an hour spent writing and testing. We find and fix errors through our own review cycle, and record corrections publicly in the Changelog.
Where to begin
If you are new, start with Start Here. If you know what you are looking for, browse the guides or the glossary. And if you only read one thing on this site, make it Backup Strategy.