Skip to main content
Version: v0.11


Welcome to Kusion! This introduction section covers what Kusion is, the problem Kusion aims to solve, and how Kusion compares to other software. If you just want to dive into using Kusion, feel free to skip ahead to the Getting Started section.

What is Kusion?

Kusion is an intent-based Platform Orchestrator that enables developers to specify their desired intent in a declarative way and then using a consistent workflow to drive continuous deployment through application lifecycle. Inspired by the phrase Fusion on Kubernetes, Kusion aims to help application and platform developers to develop and deliver in a self-serviceable, fast, reliable, and collaborative way.


Why Kusion?

Developers should be able to deploy and run their applications and services end to end. "You build it, you run it", the original promise of DevOps.

But the modern day for most software organizations this promise quickly become unrelalistic since the increasingly complex cloud-native toolchains, while cloud native technologies made huge improvements in areas such as scalability, availability and operability, it also brings downside - the growing burden on developers, which leads to the rise of Platform Engineering.

Another challenge we saw is that a series of antipatterns emerge when regular software organizations tries to implement true DevOps. Without well proven reference architecture and supporting tools, it's much more difficult to accomplish the original promise.

On one hand, Kusion was build to minimize developer's cognitive load. With application-centric configuration model, you don't need to deal with tedious infrastructure and configuration management tooling, all you need to be familiar with is AppConfiguration. This approach shields developers from the configurational complexity of Kubernetes but still enable standardization by design.

On the other hand, Kusion defines a new way for different engineering organizations to collaborate. With the separation of concerns, different roles could focus on their aspects of the configuration based on their knowledge and responsibility, whereas Kusion will dynamically manage and "glue" the opinionated configurations together. Through such a division of labor, the platform team can better manage the differences and complexities of the platform, and app developers could participate in ops work with much less cognitive load.

Kusion Highlights

  • Platform as Code

    Specify desired application intent through declarative configuration code, drive continuous deployment with any CI/CD systems or GitOps to match that intent. No ad-hoc scripts, no hard maintain custom workflows, just declarative configuration code.

  • Dynamic Configuration Management

    Enable platform teams to set baseline-templates, control how and where to deploy application workloads and provision accessory resources. While still enabling application developers freedom via workload-centric specification and deployment.

  • Security & Compliance Built In

    Enforce security and infrastructure best practices with out-of-box base models, create security and compliance guardrails for any Kusion deploy with third-party Policy as Code tools. All accessory resource secrets are automatically injected into Workloads.

  • Lightweight and Open Model Ecosystem

    Pure client-side solution ensures good portability and the rich APIs make it easier to integrate and automate. Large growing model ecosystem covers all stages in application lifecycle, with extensive connections to various infrastructure capabilities.


Kusion is an early project. The end goal of Kusion is to boost Internal Developer Platform revolution, and we are iterating on Kusion quickly to strive towards this goal. For any help or feedback, please contact us in Slack or issues.