Kusion is an intent-driven Platform Orchestrator, which sits at the core of an Internal Developer Platform (IDP). With Kusion you can enable app-centric development, your developers only need to write a single application specification - AppConfiguration. AppConfiguration defines the workload and all resource dependencies without needing to supply environment-specific values, Kusion ensures it provides everything needed for the application to run.

Kusion helps app developers who are responsible for creating applications and the platform engineers responsible for maintaining the infrastructure the applications run on. These roles may overlap or align differently in your organization, but Kusion is intended to ease the workload for any practitioner responsible for either set of tasks.

As a Platform Orchestrator, Kusion enables you to address challenges often associated with Day 0 and Day 1. Both platform engineers and application engineers can benefit from Kusion.

There are two key workflows for Kusion:

1. Day 0 - Set up the modules and workspaces: Platform engineers create shared modules for deploying applications and their underlying infrastructure, and workspace definitions for the target landing zone. These standardized, shared modules codify the requirements of stakeholders across the organization including security, compliance, and finance.

   Kusion modules abstract the complexity of underlying infrastructure tooling, enabling app developers to deploy their applications using a self-service model.

   

2. Day 1 - Set up the application: Application developers leverage the workspaces and modules created by the platform engineers to deploy applications and their supporting infrastructure. The platform team maintains the workspaces and modules, which allows application developers to focus on building applications using a repeatable process on standardized infrastructure.

   

Starting With Kusion v0.14.0, we are officially introducing Kusion Server with a Developer Portal.

Kusion Server runs as a long-running service, providing the same set of functionalities as the Kusion CLI, with additional capabilities to manage application metadata and visualized application resource graphs.

Kusion Server manages instances of Projects, Stacks, Workspaces, Runs, etc. centrally via a Developer Portal and a set of RESTful APIs for other systems to integrate with.

To get started with Kusion Server:

1. First, follow the Installation Guide to install Kusion Server.

Note that you need to configure your kubeconfig properly according to the guide, as Kusion Server requires access to a Kubernetes cluster to function properly.

2. Then, follow the QuickStart Guide to learn how to use Kusion Server to deploy your first application.

This guide will cover:

1. Install Kusion CLI.
2. Deploy an application to Kubernetes with Kusion.

# tap formula repository Kusionstack/tap
brew tap KusionStack/tap

# install Kusion 
brew install KusionStack/tap/kusion

# install Kusion latest version
powershell -Command "iwr -useb https://www.kusionstack.io/scripts/install.ps1 | iex"

For more information about CLI installation, please refer to the CLI Installation Guide for more options.

To deploy an application, you can run the kusion apply command.

To rapidly get Kusion up and running, please refer to the Quick Start Guide.

Check out these case studies on how Kusion can be useful in production:

• Jan 2025: Configuration Management at Ant Group: Generated Manifest & Immutable Desired State
• Jan 2024: Modeling application delivery using AppConfiguration

If you have any questions, feel free to reach out to us in the following ways:

• Slack | Join

• DingTalk Group: 42753001 (Chinese)

• WeChat Group (Chinese): Add the WeChat assistant to bring you into the user group.

  

If you're interested in contributing, please refer to the Contributing Guide before submitting a pull request.

Kusion is under the Apache 2.0 license. See the LICENSE file for details.