Base Kit

The Base Kit is designed for professional single-server deployments. It provides a carefully curated set of services that work well together out of the box, optimized for reliability and simplicity on a standalone node. This solution is built for both efficiency and complexity management on a single host, making it suitable for any skill level requiring a standalone architecture.

The Base Kit follows an IaC-first approach using OpenTofu for infrastructure provisioning and Docker Compose for service deployment.

Overview

Available variants

Choose a variant that matches your use case:

Default (Dokploy)
Beszel
Minimal

The standard variant for users without their own domain. Port-based access.

Service	Description
Traefik v3	Reverse proxy with auto-SSL
Dokploy	Container platform (like Vercel for your homelab)
Uptime Kuma	Status monitoring with public pages
Dozzle	Real-time Docker log viewer
whoami	Debug/test service

kombination.yaml

stackkit: base-kit
variant: default

Focused on server metrics instead of uptime monitoring.

Service	Description
Traefik v3	Reverse proxy with auto-SSL
Dokploy	Container platform
Beszel	Lightweight server metrics (CPU/RAM/disk)
Dozzle	Real-time Docker log viewer
whoami	Debug/test service

kombination.yaml

stackkit: base-kit
variant: beszel

Lightweight classic stack with direct Docker management.

Service	Description
Traefik v3	Reverse proxy with auto-SSL
Dockge	Docker Compose stack manager
Portainer	Container management UI
Netdata	Real-time performance monitoring
Dozzle	Real-time Docker log viewer

kombination.yaml

stackkit: base-kit
variant: minimal

Included services

Traefik v3

Reverse Proxy & SSLAutomatic HTTPS certificates (Let’s Encrypt), routing, and load balancing for all services.

Dokploy

Container PlatformSelf-hosted PaaS like Vercel/Railway. Deploy from Git, manage databases, and scale apps.

Coolify

Alternative PaaSOpen-source alternative to Heroku. Best for users with their own domain.

Uptime Kuma

Status MonitoringMonitor your services with beautiful status pages and alerts.

Beszel

Server MetricsLightweight resource monitoring (CPU, RAM, disk, network).

Dozzle

Log ViewerReal-time Docker container log viewer in your browser.

Optional identity services

TinyAuth

Lightweight Auth ProxySimple authentication middleware for protecting services with basic auth or OAuth2.

PocketID

OIDC ProviderFull-featured OpenID Connect provider for single sign-on across your homelab.

Requirements

Resource	Low	Standard	High
CPU	2 cores	4 cores	8 cores
RAM	4 GB	8 GB	16 GB
Storage	20 GB SSD	50 GB SSD	100+ GB SSD
Variant	Forces minimal	Any	Adds Prometheus/Grafana

Supported operating systems

OS	Version	Status
Ubuntu	24.04 LTS	✅ Recommended
Ubuntu	22.04 LTS	✅ Supported
Debian	12 (Bookworm)	✅ Supported

Quick start

Create your spec file

kombination.yaml

stackkit: base-kit
variant: default

# Node configuration
nodes:
  - name: main-server
    type: local  # or vps, cloud
    connection:
      host: 192.168.1.100
      user: root
      ssh_key: ~/.ssh/id_ed25519

# Domain (optional - enables auto-SSL)
domain: homelab.example.com
email: you@example.com

# Service toggles
services:
  dokploy:
    enabled: true
  uptime_kuma:
    enabled: true
  dozzle:
    enabled: true

Validate configuration

stackkit validate

Output:

✓ StackKit: base-kit (v1.0.0)
✓ Variant: default
✓ OS: ubuntu-24
✓ Compute tier: standard
✓ All service dependencies satisfied
✓ No port conflicts detected

Ready to deploy!

Generate infrastructure code

stackkit generate

Creates:

tofu/main.tf — OpenTofu configuration
tofu/variables.tf — Variables
docker-compose.yml — Service definitions
traefik/ — Reverse proxy config

Preview and apply

stackkit plan   # Preview changes
stackkit apply  # Deploy

Configuration reference

Node settings

nodes:
  - name: main-server
    type: local              # local, vps, cloud
    os: ubuntu-24            # ubuntu-24, ubuntu-22, debian-12
    
    connection:
      host: 192.168.1.100
      port: 22
      user: root
      ssh_key: ~/.ssh/id_ed25519
      # OR password: ${SSH_PASSWORD}
    
    resources:               # Optional — auto-detected
      cpu: 4
      memory_gb: 8
      disk_gb: 50

Domain and SSL

With domain
Local only

domain: homelab.example.com
email: you@example.com

ssl:
  provider: letsencrypt
  # Optional: wildcard for *.homelab.example.com
  wildcard: true

# No domain — access via IP:port
# Dokploy will be available at http://IP:3000

ssl:
  provider: selfsigned

Service configuration

services:
  traefik:
    enabled: true           # Always required
    dashboard: true         # Enable Traefik UI
    log_level: INFO
    
  dokploy:
    enabled: true
    # Dokploy runs on port 3000 by default
    
  uptime_kuma:
    enabled: true
    public_page: true       # Enable public status page
    
  dozzle:
    enabled: true
    remote_hosts: []        # Add remote Docker hosts
    
  # Optional identity
  tinyauth:
    enabled: false
    
  pocketid:
    enabled: false

Deployment modes

The Base Kit supports two deployment modes:

Mode	Engine	When to use
Simple	OpenTofu only	Quick setup, one-time deployment
Advanced	OpenTofu + Terramate	Drift detection, Day-2 operations

Advanced mode is automatically enabled when:

driftDetection.enabled: true
autoUpdates.enabled: true
compliance.required: true

# Enable advanced mode
operations:
  driftDetection:
    enabled: true
    schedule: "0 */6 * * *"  # Every 6 hours
  autoUpdates:
    enabled: true
    schedule: "0 4 * * 0"    # Sunday 4am

File structure

After stackkit generate:

.
├── kombination.yaml          # Your configuration
├── tofu/
│   ├── main.tf              # Infrastructure definition
│   ├── variables.tf         # Input variables
│   ├── outputs.tf           # Output values
│   └── terraform.tfvars     # Generated values
├── docker-compose.yml        # Service definitions
├── traefik/
│   ├── traefik.yml          # Static config
│   └── dynamic/
│       └── routes.yml       # Dynamic routing
└── data/                    # Persistent volumes

Constraints

The Base Kit enforces these rules:

Constraint	Value	Reason
Max nodes	1	Single-node design
Traefik required	Yes	All services need routing
Min RAM	4 GB	Services won’t fit in less

If you need more than 1 node, consider:

Modern Homelab Kit — Multi-node with Headscale VPN
High Availability Kit — High-availability Docker Swarm cluster

Troubleshooting

Services not accessible

Check Traefik is running: docker logs traefik
Verify DNS resolves to your server
Check firewall allows ports 80/443
For local: Use http://IP:PORT instead of domain

SSL certificate errors

Let’s Encrypt: Domain must be publicly accessible
Self-signed: Add browser exception or use curl -k
Check rate limits at https://letsencrypt.org/docs/rate-limits/

Dokploy not starting

Check port 3000 is not in use: netstat -tlnp | grep 3000
Verify Docker socket permissions
Check logs: docker logs dokploy

Low disk space warnings

Prune unused images: docker image prune -a
Check volume sizes: docker system df
Consider adding external storage

Next steps

CUE basics

Learn how to customize StackKit schemas

Create custom StackKit

Build your own StackKit from scratch

Overview

Available Kits

How-To

Explanations

Reference

Overview

Available variants

Included services

Traefik v3

Dokploy

Coolify

Uptime Kuma

Beszel

Dozzle

Optional identity services

TinyAuth

PocketID

Requirements

Supported operating systems

Quick start

Configuration reference

Node settings

Domain and SSL

Service configuration

Deployment modes

File structure

Constraints

Troubleshooting

Next steps

CUE basics

Create custom StackKit

Overview

Available Kits

How-To

Explanations

Reference

​Overview

​Available variants

​Included services

Traefik v3

Dokploy

Coolify

Uptime Kuma

Beszel

Dozzle

​Optional identity services

TinyAuth

PocketID

​Requirements

​Supported operating systems

​Quick start

​Configuration reference

​Node settings

​Domain and SSL

​Service configuration

​Deployment modes

​File structure

​Constraints

​Troubleshooting

​Next steps

CUE basics

Create custom StackKit

Overview

Available variants

Included services

Optional identity services

Requirements

Supported operating systems

Quick start

Configuration reference

Node settings

Domain and SSL

Service configuration

Deployment modes

File structure

Constraints

Troubleshooting

Next steps