Skip to main content
StackKits are validated, reusable infrastructure blueprints that define architecture patterns for your homelab. Each StackKit describes how services relate to each other — not how many servers you need.

​
What is a StackKit?

A StackKit combines three concepts to produce your infrastructure: A StackKit is a smart configuration system that:
  1. Validates your choices against proven architecture patterns
  2. Detects your runtime environment and applies context-aware defaults
  3. Merges composable Add-Ons for additional capabilities
  4. Generates release-packaged infrastructure artifacts and rollout evidence

​
The problem StackKits solve

You want to set up a homelab. You’ve heard of:
  • Traefik (or Caddy? or nginx?)
  • TinyAuth + PocketID (or Authentik? or Keycloak?)
  • Coolify (or Komodo? or another PaaS?)
  • Immich (or Photoprism?)
Questions that keep you stuck:
  • Which tools work well together?
  • How do I configure them correctly?
  • What are the best practices?
  • How do I avoid security issues?

​
Available StackKits

StackKits are architecture patterns, not node-count definitions. The public beta scope is Base Kit; Modern Homelab and High Availability remain preview until their own evidence matrices graduate.

Base Kit

Single-environment patternAll services in one deployment target. Simple, predictable.
  • Coolify default
  • Any node count
  • Context-aware defaults

Modern Homelab Kit

Hybrid infrastructure patternBridges local and cloud environments with VPN overlay.
  • Multi-environment
  • Preview
  • Coolify PaaS
  • Public + private services

High Availability Kit

High-availability patternRedundancy, failover, and quorum-based consensus.
  • Preview
  • Docker Swarm cluster
  • Keepalived VIP
  • 3+ nodes recommended

​
The three concepts

​
1. StackKit = Architecture pattern

A StackKit defines how services relate to each other, not how many servers you have.
StackKitPatternExample
base-kitSingle-environment1 Pi running all services, or 3 servers sharing the same stack
modern-homelabHybrid previewHome server + cloud VPS connected via VPN
ha-kitHA preview3-node Docker Swarm with failover
A base-kit StackKit can run on multiple nodes in the same environment. Preview kits define architecture patterns, not public beta support commitments.

​
2. Node-Context = auto-detected environment

Each node is automatically classified based on hardware and provider metadata:
ContextDetectionAffects
localPhysical hardware, no cloud metadataSelf-signed TLS, local DNS, *.home.localhost
cloudCloud provider metadata detectedLet’s Encrypt, Coolify PaaS, public DNS
piARM + low memory or RPi detectionReduced services, ARM images, tmpfs
At Level 0 (standalone CLI), you specify context manually. At Level 2+ (with kombify TechStack agent), context is auto-detected from hardware reports.

​
3. Add-Ons = composable extensions

Add-Ons replace the old monolithic variant system. They are stackable, declare their compatibility, and layer onto any kit. The catalog currently ships 18 add-ons:
CategoryAdd-Ons
Observability & datamonitoring, backup, backup-repo-server
Apps & mediamedia, photos, vault, file-sharing, calendar, mail, gameserver
Compute & devai-workloads, dev-platform
Identity & accessauthelia, remote-desktop
Networkingvpn-overlay, tunnel
Reliabilityha
Homesmart-home
stack-spec.yaml
addons:
  - monitoring       # VictoriaMetrics + Grafana + Loki + Alloy
  - backup           # Kopia encrypted backups (3-2-1)
  - media            # Jellyfin + *arr stack
See the full per-add-on detail and the platform-service alternatives in tool alternatives. For the monitoring contract, see /stackkits/reference/monitoring.

​
Progressive capability model

StackKits operate at different capability levels depending on how you access them:
LevelNameAccess MethodCapabilities
0Standalone CLIstackkit CLI directlyCUE validation, IaC generation, direct provisioning
1Control Planekombify TechStack Web UI/APIUnifier pipeline, wizard UI, StackKit resolver
2Worker Agentkombify TechStack + gRPC AgentContext auto-detection, placement engine
3Runtime IntelligenceDay-2 operationsDrift detection, auto-remediation, cert renewal
4AI-Assisted (SaaS)kombify CloudNatural language config, predictive scaling
Level 4 capabilities are available exclusively through kombify Cloud (SaaS) and require cloud connectivity.

​
How StackKits work

​
Context-driven defaults matrix

The combination of StackKit × Context produces curated default configurations:
localcloudpi
base-kitCoolify, local .home.localhost linksCoolify or Komodo, Let’s EncryptLean profile, reduced services
modern-homelabPreviewPreviewPreview
ha-kitPreviewPreviewPreview

​
Validation flow

When you run stackkit validate or use kombify TechStack:

​
StackKit comparison

Featurebase-kitmodern-homelabha-kit
PatternSingle-environment public betaHybrid infrastructure previewHA cluster preview
Container runtimeDocker ComposeDocker + CoolifyDocker Swarm
Typical nodes1 (supports N)2+ (multi-environment)3+ (odd for quorum)
ComplexityLowMediumHigh
VPN overlayOptional (Add-On)Built-inOptional
FailoverNoNoYes
Best forFirst homelab, single VPSHybrid setups, public servicesProduction workloads

​
Choosing a StackKit

Use: base-kitStart simple with a single-environment setup:
  • Easy to understand
  • Minimal resource requirements
  • Great for learning
  • Add capabilities later with Add-Ons
Use: modern-homelabFor hybrid setups connecting different environments:
  • VPN overlay connects all nodes
  • Public services via cloud nodes
  • Private services stay local
  • Coolify manages deployments
Use: ha-kitWhen downtime is unacceptable:
  • Automatic failover
  • Database clustering
  • Load balancing with Keepalived
  • Requires 3+ nodes (odd number for quorum)

​
Next steps

Base Kit

Detailed documentation for the single-environment StackKit

CUE language basics

Learn the CUE language used in StackKits

Customization guide

How to customize StackKits for your needs

Quick start

Deploy your first StackKit