stackkit CLI and MCP connector, and a local lifecycle for validating, generating, applying, and verifying a stack.
StackKits works against a host you already control; it does not require a kombify account or a hosted kombify endpoint.
Release-specific documentation
Check the use-case catalog, OS compatibility, and application delivery compatibility for listed components and declared compatibility. Each reference identifies and links the published release it describes. OS compatibility and the Lifecycle test column of application delivery compatibility come from automated lifecycle runs of that release on fresh virtual machines: install, init, generate, apply, verify, backup and restore. The use-case catalog and the declared adapter capabilities are not evidence of deployment or verification on a real host. Guides and examples that name a version describe that version. Do not assume an older example has been verified against a newer release.Kit definitions
Basement Kit
The current local, single-environment kit for hardware on your home or private network.
Cloud Kit
A released single-environment definition for an existing VPS or cloud host that you operate.
Modern Homelab (alpha)
An alpha definition archive spanning Home and Cloud; it validates and generates today but is not an install target yet.
What StackKits does not do
- create or buy a server for you
- hold provider credentials or manage provider resources
- require a hosted control plane for Standard Mode
- replace the local owner and evidence produced by the standalone lifecycle
Next steps
Quickstart
Install the released CLI and create a first Basement Kit workspace.
Use cases
Photos, files, passwords and more, with the applications that provide them.
Guides
Configure intent, inspect a plan, apply, verify, and practice recovery.
