Temper documentation
Everything you need to install the platform, protect your first workload, and run it in production — written buyer-facing but technically true. Start with the quickstart; it takes about 15 minutes on a real cluster.
Getting started
Getting startedQuickstarthelm install to a protected node in ~15 minutes: build images, install the chart, verify, assign a PriorityClass, know the kill switch.
ConceptsArchitectureThe three layers (node enforcement, cluster intelligence, management plane), what talks to what, and why everything stays in-cluster.
Capabilities
ConceptsKernel-level QoS enforcementFive tiers derived from Kubernetes PriorityClasses, mapped to kernel scheduler layers sized from real resource requests.
ConceptsWorkload thread profilesPer-thread-group scheduling inside a single pod: builtin profiles, file-based custom profiles, and the training pipeline.
PlatformSLO-safe density & overcommitThe density-aware scheduler plugin, the reversible overcommit webhook, and complement mode under Karpenter or Cast AI.
PlatformFleet management planeExplorer, logs, manifests and diffs, audit-logged actions, RBAC, the savings methodology, and the multi-cluster hub.
PlatformObservability & rightsizing/metrics, /observe, Grafana dashboards, the placement linter, kernel trace capture, and the thread-aware rightsizer.
Operations & reference
OperationsSafety & rollbackThe kernel revert contract, the safe-mode kill switch, measured failover, churn cost, and the honest cpu.max disclosure.
OperationsOperationsCanary upgrades, the rollback runbook, monitoring the agent, and sizing guidance for protected tiers.
OperationsPlatform supportThe verified matrix — including the honest AKS and Autopilot noes — kernel requirements, and ARM status.
ReferenceFAQHPA/VPA coexistence, CPU limits under sched_ext, air-gap operation, licensing and source access, and more.