Skip to content

Homelab design & build

A homelab, designed and built properly.

The same engineering as the rest of this site, at the scale of a home or a small office: chosen to fit what you want to run, backed up and restored before handover, and documented so it does not depend on whoever built it. Three tiers, described by what is in them. Every homelab starts from something different, so each one is quoted on request.

Starter

One well-run box that you can trust and restore.

You want a home server or a first homelab done properly, without turning it into a hobby of its own.

Included

Handed over

A written runbook: what is where, how to update it, and how to restore it.

Full professional

A homelab run to the standard of a production estate.

Your lab is where you learn production habits, or it quietly became production for your household or a small business.

Included

  • Everything in Sweet spot, with high availability for the services that need it and failover performed, not assumed. Shown in a write-up
  • Single sign-on with MFA on administrative interfaces, backed by a central directory. Shown in a write-up
  • A read-only security review with a numbered findings list, and secret scanning on your repositories. Shown in a write-up
  • An operations display of the whole estate, driven by live data and legible from across a room. Shown in a write-up

Handed over

Full documentation, a verification harness that re-runs the checks, and the option of an ongoing arrangement.

Hardware is billed at cost, with no markup. You can also bring your own: the design starts from what you already have.

How it starts

Describe what you have, and what you want it to do

The same three steps as any other engagement.

  1. Describe what you are running

    What the estate is, and what is currently going wrong with it. No inventory spreadsheet required — a paragraph is enough to tell whether there is useful work here.

  2. A short call to scope it

    We agree which shape fits, what would be in scope, and what the finished thing has to be able to demonstrate. If the answer is that you do not need anyone, you get told that instead of a proposal.

  3. Written scope, then work

    Scope written as verifiable outcomes rather than a component list, because a component list can be delivered without the system working. Access is scoped to the task and revoked at handover.