Solutions
Self-host with one command.
Give your customers a helm install that just works — including the upgrades and rollbacks that usually don’t.
Shipping a tarball isn’t self-hosting.
It’s the start of a support queue.
Hand a customer a chart and a README and you’ve signed up for every environment difference, every missed upgrade, and every drift incident that follows. Akua wraps what you already ship as one versioned, signed package — the chart unchanged — and keeps every install in sync from one place.
How it works.
-
Wrap your chart as a package
Your existing Helm chart is wrapped as-is; the package adds typed inputs around it. akua.toml records intent, akua.lock records resolved digests and signatures.
-
Customer installs in one command
They get managed Kubernetes in minutes or bring their own cluster. The package does not change between clouds.
-
Stay in sync from your side
Each install renders into its own git repository and Argo CD reconciles it. Updates land as a reviewed change, never a push straight to main.
Install, upgrade, roll back.
-
One command
The customer runs a single install. The package’s typed inputs become the setup screen; no per-customer runbook to maintain.
-
Upgrades that land
Bump the version once; the platform proposes the change to every install. No customer is left on a forgotten release.
-
Rollbacks that mean it
A revert of rendered state, not a guess at the last good inputs. The repository is the source of truth.
One command for them.
One package for you.
The chart you already ship, kept in sync across every install — with the repository still theirs to take.