Backends
A backend is how an outpost runs workloads. High supports two, and picks per node.
The k8s backend
On Kubernetes nodes — k3s, EKS, GKE, AKS — High renders your release into native Kubernetes objects and lets the cluster schedule them. Use this where you already run Kubernetes or want its scheduling and autoscaling.
The raw backend
On a bare machine with no orchestrator, the raw backend runs your components directly on containerd. This is what makes a VPS or a Raspberry Pi a first-class target — no cluster required.
The backend is a property of the node, not your app. The same release runs across k8s and raw outposts at once.
Isolation
Whichever backend runs it, a workload is sandboxed. Where the hardware supports it, each one runs in its own lightweight virtual machine — a real kernel boundary, not just a shared-kernel container — so different tenants can safely share a single outpost. That boundary is what lets High treat one machine as capacity for more than one project without them ever seeing each other.