Skip to main content
The fastest StackKits path is the Install Engine: one short command on the host that should become your homelab. If you want more control, install the CLI only and run the steps yourself.

​
Fastest path

Run the Base Kit one-liner on a Linux or macOS host with root/sudo access. Without a version pin, this installs the current stable latest release (v0.4.4): 
curl -sSL https://base.stackkit.cc | sh
This installs the stackkit CLI, installs the Base Kit definitions, prepares Docker and OpenTofu, initializes the stack, generates deployment artifacts, applies the stack, and prints the service URLs.

​
Public beta path

Use the pinned beta path when you are testing the current BaseKit beta prerelease (v0.4.5-beta.1): 
export STACKKIT_RELEASE_VERSION=v0.4.5-beta.1
curl -sSL https://base.stackkit.cc | sh
Prerelease pins are explicit by design. Unpinned installers stay on stable latest until the beta evidence and public mirror CI are clean enough for stable promotion.

​
Per-kit one-liners

Use a kit-specific one-liner when you already know the StackKit standard: 
curl -sSL https://base.stackkit.cc | sh      # Base Kit stable latest
curl -sSL https://modern.stackkit.cc | sh    # Modern Homelab preview
curl -sSL https://ha.stackkit.cc | sh        # High Availability preview
StackKitUse caseComplexity
base-kitSingle-environment homelabPublic beta
modern-homelabHybrid local + cloud setupPreview
ha-kitHigh availability and failoverPreview

​
CLI-only path

Use the CLI-only installer when you want to make the technical choices yourself:
1

Install the CLI

curl -sSL install.stackkit.cc | sh
2

Initialize a StackKit

mkdir my-homelab
cd my-homelab
stackkit init base-kit
3

Prepare and generate

stackkit prepare
stackkit generate
4

Preview and apply

stackkit plan
stackkit apply
5

Check status

stackkit status

​
What you get

The Base Kit default provisions a homelab foundation with StackKits standards, add-ons, baselines, auth/routing defaults, generated infrastructure artifacts, and a service URL summary.

​
Next steps

CLI or TechStack

Compare the Install Engine, CLI tool, and kombify-TechStack UI.

Base Kit details

Learn what Base Kit deploys and how its defaults work.

Node Hub

Use the default dashboard at base.<domain> after rollout.