Deployments covers how applications land on your clusters: the per-installation git repositories that make every deployment auditable, the inputs editor, sources, and the package model that ties it all together. Every installation gets its own private git repository, whether a customer purchased your product or you installed a tool directly. That repository is the source of truth for the deployment: the customer’s wizard inputs, the composition logic, and the rendered Kubernetes resources your cluster applies.Documentation Index
Fetch the complete documentation index at: https://akua-1dce587a.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Installation repositories
The git-backed model behind every installation: what it stores and how to use it.
Customize an installation via git
Edit inputs, patch resources, and roll out changes with a push.
Application sources
GitHub repositories, Helm charts, and Docker images as package sources.
Customizing inputs
Wizard editor, per-install overrides, and staged rollouts.
Package generation
How Akua generates a per-install package from your sources.
Package versioning
How commit history maps to deployments and how to roll back.
Two ways to install
Product-based installations
Product-based installations are created when customers purchase your products through the marketplace, or when you install a product manually from your dashboard. Each installation is customer-scoped, can carry Stripe billing, and is managed through your product. Use product-based installations when you are selling software to customers, need billing integration, or want marketplace distribution.Direct installations
Direct installations let you deploy applications without a product or pricing configuration. They are ideal for supporting systems (shared databases, monitoring stacks, API gateways) that your products depend on but that are not sold individually. Use direct installations when you are setting up infrastructure, internal tools, or services that do not need per-customer billing. Both installation types follow the same underlying model: a package is selected, an installation repository is provisioned, the cluster syncs the rendered manifests, and Akua monitors the lifecycle.Related topics
Products
Create sellable packages for the marketplace.
Clusters
Set up infrastructure for your installations.
Marketplace
How customers discover and install your products.
Akua packaging
The open-source substrate behind every Akua installation.