Create clusters anywhere
Vanilla, K3s, Talos, VCluster and KWOK in Docker or on cloud servers, or managed EKS, GKE and AKS — with your choice of CNI, CSI and policy engine.


Running Kubernetes usually means installing and wiring together kind or k3d, kubectl, Helm, a GitOps
engine and SOPS — and every distribution does it a little differently. KSail embeds those tools in a
single binary driven by one ksail.yaml, so the same commands create, update and delete a cluster
whether it runs in Docker on your laptop or on cloud infrastructure. It writes native configs such as
kind.yaml and Talos patches, so you can keep using the underlying tools with or without KSail.
Vanilla, K3s, Talos, VCluster and KWOK in Docker or on cloud servers, or managed EKS, GKE and AKS — with your choice of CNI, CSI and policy engine.
Flux or ArgoCD built in. workload push packages your manifests as an OCI artifact and workload reconcile rolls them out.
Schema-check and security-scan your manifests offline, with no cluster — an ideal CI gate.
Encrypt, decrypt and edit secrets with built-in SOPS and Age.
Diagnose cluster health, back up and restore, mirror registries and onboard tenants.
Use the terminal, the web UI or desktop app, the VS Code extension, or an AI assistant over chat or MCP.
Browse every feature by task.
Choose your setup
Pick the distribution and provider that fit your goal. Compare →
Deliver with GitOps
The recommended workflow once your first cluster is running. Learn it →
Core concepts
How KSail separates what runs from where it runs. Understand →
Configuration
Every ksail.yaml field and how settings combine. Reference →