Skip to main content
A package authoring loop from package files and inputs through render, preview, and installation.
Akua is the open-source packaging substrate behind Akua’s per-installation renders. Every install on Akua is an akua Package: a typed, signed, deterministically-rendered KCL program that turns customer inputs into Kubernetes manifests. You don’t have to author an akua Package by hand to use Akua. The platform can synthesize one from supported sources, such as Helm charts or container images. See Packages for the platform contract around Package versions.

​
What akua provides

SurfacePurpose
package.kInstall composition: KCL logic that turns inputs into Kubernetes resources
akua.toml + akua.lockPinned dependencies (Helm charts, other Packages, KCL libraries) with cosign signatures
akua renderExecutes the Package against customer inputs, produces deploy-ready manifests
akua exportEmits the Package’s input schema as standards-pure JSON Schema 2020-12 / OpenAPI 3.1
A programmatic API exists for embedding akua in your own tooling. See the akua repo for details.

​
How Akua uses akua

Akua runs akua at three points in the install lifecycle:
  1. Schema for the install wizard: Akua exports the Package’s Input schema as JSON Schema; the wizard renders from it. UI hints from @ui(...) decorators flow through as x-ui extensions.
  2. Per-install rendering: for every customer install, Akua renders the Package against the customer’s inputs.yaml, vendoring upstream deps and writing the rendered manifests into the installation repository.
  3. Version selection: when an installation moves to a different Package version, Akua renders that installation independently.

​
Where to start

Package format

Authoring package.k: the Input schema, @ui annotations, composition.

Offers

How @ui drives the install wizard at /i/<hash> and what offers carry.

Akua repo on GitHub

Source code, full CLI reference, SDK docs, examples.

Installation repositories

The per-install git repo that materializes a rendered Package.

​
Status

Akua is pre-alpha. The Package format and CLI contract are stable enough to build on, but the CLI verb set is still iterating. Akua pins to a specific akua version per release and bumps deliberately. For canonical, always-fresh references, the akua repository is authoritative. The pages here are curated for product authors building on akua within Akua; full architecture, embedded engines, security model, and roadmap docs live in the akua docs directory.

Installation repositories

The per-install git repository that materializes a rendered Package.

Offers

How your Package’s schema drives the install wizard.

Customizing inputs

Wizard, overrides, and reviewed repository changes.

Products

Wrap a Package into a sellable product with billing.