Solutions
Bring your own cloud.
Your customers run on their own AWS, GCP, or Hetzner account. You manage the lifecycle. Their keys, their bill, your control plane.
The customer owns the infrastructure. You own the product.
Not a hosted SaaS. Not a tarball over the wall.
BYOC has always meant a choice between control and operability — give the customer the keys and lose the ability to operate, or keep operating and hold their keys. Akua removes the trade-off: the customer keeps the keys and you keep operating, because the control plane never needs an inbound path into their environment.
Who holds what.
The line between you and your customer is explicit — and it never runs through us.
- Cloud account
- The customer’s. They pay the provider directly — no compute markup from us.
- Admin keys
- The customer’s. Not shared, not escrowed.
- Network path
- Outbound-only. No inbound access from the control plane into their cluster.
- Lifecycle
- Yours. Versions, upgrades, and drift managed from one place via per-install repositories.
Their account, their keys, your lifecycle.
-
Their account
The workload runs in the customer’s own cloud account — AWS, GCP, Azure, Hetzner, on-prem. The customer picks the provider and the region.
-
Their keys
The cluster admin keys are theirs, not yours and not ours. The worker bootstrap is outbound-only — nothing reaches into their environment.
-
Your lifecycle
You manage versions, upgrades, and drift from one place. Each install is its own git repository, reconciled on the customer’s clock.
Their cloud. Their keys.
Your control plane.
Operate every customer install without ever holding their infrastructure. The export stays theirs.