What it is

KubeVela is an open-source modern application delivery platform that runs on Kubernetes and makes deploying and operating applications across hybrid and multi-cloud environments easier, faster and more reliable. It is written in Go, released under the Apache-2.0 license, and listed in the CNCF topic set alongside continuous delivery and control plane tooling. The project lives in the cloud native ecosystem, where it acts as a control plane that glues infrastructure capabilities together and orchestrates them as reusable modules. Its delivery model is built around the Open Application Model, with CUE used to define and extend application and workflow logic.

The concrete problem it solves is the sprawl of ad-hoc deployment scripts and glue code that accumulates when teams ship to more than one cluster or cloud. KubeVela practices a "render, orchestrate, deploy" workflow: a deployment plan is declared as a workflow and executed automatically by any CI/CD or GitOps system. Workflow steps can be extended or re-programmed with CUE instead of bespoke scripts. That gives platform teams one control plane for progressive rollout across test, staging and production environments, automatic canary and blue-green strategies, continuous verification, and placement across clusters and clouds.

Key capabilities

• Deployment as code: declare a deployment plan as a workflow and run it automatically from any CI/CD or GitOps system.
• Workflow extensibility through CUE, allowing existing steps to be extended or re-programmed without ad-hoc scripts or glue code.
• Multi-cloud and hybrid-environment delivery treated as a first-class concern, with progressive rollout, canary, blue-green and continuous verification.
• Rich placement strategy across clusters and clouds, plus automated cloud environment provisioning.
• Built-in multi-tenancy and multi-cluster authorization and authentication, including out-of-the-box LDAP integrations and fine-grained RBAC modules.
• Automated observability dashboards covering the delivery process.
• Lightweight control plane deployable as a single pod with 0.5c1g resources, extended through a growing addon collection.

Who uses it and how

• Platform engineers who define application delivery workflows once and let CI/CD or GitOps systems execute them, rather than maintaining per-team deployment scripts.
• Teams running progressive rollouts across test, staging and production environments, with canary, blue-green and continuous verification handled by the control plane.
• Organizations operating hybrid or multi-cloud estates that need a consistent placement strategy across clusters and clouds, including automated provisioning of cloud environments.
• Platform builders who need multi-tenancy with LDAP-backed authentication and fine-grained RBAC customized to their own supply chain requirements.
• Operators who want delivery observability, using the automated dash