Delivery

Every install its own repository. Every change reviewed.

Render, deploy and verify in one transaction; roll back when a probe fails. Production changes arrive as pull requests, for people and agents alike.

A change assembled inside a glass sandbox travels on a conveyor to a glowing gate, where a fingertip approves it before it continues to the production servers

The question

What happens when an update goes wrong?

It does not reach traffic. An install renders first, deploys second, verifies third; a failed probe rolls the transaction back. Drift is detected and reported, and the change that caused it is in a repository you can read.

What is in it

Delivery, piece by piece.

What each part does, and whether you can use it today.

Atomic install

Live

Render → deploy → verify in one transaction; rollback on probe failure.

Install renders

Live

Pre-deploy manifest preview before traffic shifts.

Health & logs

Live

Per-product pod and log access without kubectl.

GitOps

Live

Continuous sync from the rendered manifests in each install repository.

Operations & notifications

Live

Typed long-running operation envelope with progress, errors, retries.

Lifecycle

Beta

Upgrade, rollback, suspend, resume, delete.

Capability gates

Beta

Block plan resolution until required CRDs / operators are present.

Drift detection

Beta

Notify on cluster divergence from desired state.

Repository change requests

Soon

Production changes via reviewable git PRs.

What it costs

The platform is a flat fee. Compute is at cost.

Free to start with one managed cluster and one machine. Pro is €20 per workspace and month. Your own cloud key removes every limit, and Akua never marks up compute.

Start with delivery
on your own terms.

Free to begin, on Akua-managed machines or your own cloud key.

Docs