Skip to main content
Modern Homelab describes a homelab spanning a Home environment and a Cloud environment. Its definition keeps control and default data authority at Home and requires explicitly declared connections and publication between locations.

​
In plain words

A normal homelab lives in one place. Modern Homelab describes one that spans two: your home and a cloud server. Today this is an early definition that you can read, initialize, validate and generate. It is not a finished way to run a two-location homelab, so it is meant for exploring and not for family photos or passwords.
Modern Homelab is an alpha definition archive without a supported installation path. You can initialize, validate and generate it with the released CLI. Downloading its archive does not establish a working connection between hosts, protected application access or recovery across locations. Use Basement Kit or Cloud Kit for an existing installation guide.

​
What the alpha archive contains

The public StackKits release includes Modern Homelab definition archives alongside the CLI. They describe the intended sites, application placement, connections and authority boundaries. Review the release’s release-evidence.json for the runtime evidence that is actually attached to that version. The toolchain-only installation guide explains how to download the CLI and Modern definitions. A complete Modern deployment still needs concrete connection, identity, routing, TLS and location-failure behavior. A configuration or generated plan alone does not verify those behaviors.

​
What you need first

  • Experience with one of the kits, ideally a working Basement Kit. Read Before you start if you are new.
  • A host at home and a cloud host with a domain you control, if you want to follow the definition’s intended shape.
  • The CLI, installed as described in the toolchain-only guide above.

​
What you can try today

  1. Install the CLI and the Modern definitions. Expect the tool to be available on your computer, with nothing changed on a server.
  2. Initialize and validate a workspace. Expect a configuration file and a report on whether it is valid.
  3. Generate and read the plan. Expect files and a plan that describe the intended layout, not a running system.

​
What is stored where

The definition and generated files stay in your workspace folder. The definition keeps control and default data authority at Home. Nothing in the alpha archive moves data between locations on its own.

​
If something goes wrong

  • Validation or generation fails: read the log with stackkit logs latest --json and see Troubleshooting.
  • You need a working homelab now: use Basement Kit or Cloud Kit.
  • You are unsure what a result proves: a generated plan alone does not verify connections, access or recovery.

​
Choose an entry path

Choose Basement Kit for an existing Linux host at home, or Cloud Kit for an existing cloud host with a domain you control. Their guides keep configuration bootstrap and release-specific runtime evidence separate. Keep the same distinction when exploring Modern: protect existing data and retain each workspace’s configuration and operation output. Do not assume that an application remains available during a connection or Cloud outage until the selected release has evidence for that behavior. See Choose a StackKit for all entry paths and application delivery compatibility for the capabilities declared by the published application adapters.