> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kombify.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Techstack operating modes
> Choose between standalone StackKits and optional Techstack orchestration
Techstack extends an existing StackKits environment. It does not replace the
standalone path.
## Standalone StackKits
The public StackKits CLI initializes, validates, generates, applies, and
verifies a stack without Techstack, an account, or a hosted kombify endpoint.
This is the default path for a local homelab or an existing VPS you operate.
## Local orchestration
The Techstack product contract adds a visual operator experience, runtime
inventory, and coordinated Day-2 operations around the same released StackKits
CLI. This mode keeps the stack and its owner authority local.
The [Windows Alpha](/techstack/install-windows) is now a public, unsigned
download. It supports account-free local operation; Cloud sync remains a
separate connected path.
## Connected operation
A connected runtime may project account context and remote status into the
operator experience. Connection is optional: local owner identity, local
credentials, and the ability to operate the stack remain with the local
environment.
## Managed placement
In managed operation, Techstack owns provider selection, resource leases,
provider credentials, lifecycle receipts, and terminal cleanup. These paths
require explicit admission and remain preview scope; the public documentation
does not claim general availability.
## Advanced Mode
Advanced Mode is a bounded Techstack-to-StackKits seam. Techstack can issue a
short-lived capability for an approved advanced operation, while the pinned
StackKits CLI validates and executes it. Techstack does not become a second
renderer or bypass StackKits validation.
Review the current public and preview boundaries before choosing a path.