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.
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.

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.