// the find
KusionStack/kusion
Declarative Intent Driven Platform Orchestrator for Internal Developer Platform (IDP).
Kusion is a Go-based platform orchestrator sitting between app developers and infrastructure, letting platform engineers define reusable modules and workspaces while app devs write a single AppConfiguration spec without needing to know the underlying cloud specifics. It's a CNCF Sandbox project backed by Ant Group. The target audience is platform engineering teams building internal developer platforms.
The Day 0 / Day 1 split is a genuinely good design — platform engineers own modules and workspace definitions, app developers consume them without touching Terraform or Kubernetes YAML directly. Multiple state backends (local, S3, OSS, GCS) means you're not locked into one cloud for state storage. Having both CLI and a long-running Server mode lets teams start small and grow into the UI and API surface. The domain model (Project/Stack/Workspace/Run) maps cleanly to how most platform teams actually organize work.
KCL (the KusionLang config DSL) is a hard dependency with a tiny ecosystem — you're betting on a language almost nobody outside Ant Group uses, and if it stalls you own the migration. The multi-cloud branding is mostly Kubernetes-centric in practice; Kusion Server explicitly requires a kubeconfig to function, so you're not escaping k8s. The concept overhead is steep: Backends, Sources, Workspaces, Projects, Stacks, Modules, Runs — you're configuring the platform before you deploy anything. 1,311 stars for something this ambitious means production war stories outside Ant Group are scarce, so you're an early adopter taking on real risk.