IT Brief Canada - Technology news for CIOs & IT decision-makers
Canada
Akuity adds fleet management to Kargo Enterprise beta

Akuity adds fleet management to Kargo Enterprise beta

Mon, 26th Oct 2026 (Today)
Sean Mitchell
SEAN MITCHELL Publisher

Akuity has added Fleet Management to Kargo Enterprise in a private beta.

The feature is aimed at platform teams managing large numbers of Kubernetes clusters, GPU nodes and edge devices. It lets them push changes across a fleet as a single release, with controls for staged rollouts, health checks and rollback.

Kargo Enterprise is the commercial edition of Kargo and runs on the Akuity Platform. The new feature replaces cluster-by-cluster release pipelines with a process that groups infrastructure into fleets, sets rollout order and applies failure thresholds across the whole group.

The move comes as companies spread workloads across more clusters, particularly for AI-related deployments. Akuity and industry analysts argue that releasing software across hundreds of environments has become an operational bottleneck for platform teams.

Teams can organise clusters into waves such as pilot, canary and broader deployment. Each cluster reports its health during rollout, and the release can pause if failures exceed a pre-set threshold, rather than stopping automatically after a single issue.

The feature also gives teams a consolidated view of release status across the fleet and supports access controls for teams responsible for only part of the estate. Rollbacks can be applied across the fleet in a single action, rather than through separate processes for each cluster.

Stephanie Walter, Practise Leader - AI Stack, HyperFRAME Research, described the release challenge as one of handling partial failures across distributed infrastructure.

"Managing partial failure is a real challenge when a release spans hundreds of clusters. Teams need to distinguish an isolated cluster problem from a bad change that should stop the rollout. Kargo Enterprise's Fleet Management brings failure thresholds, release visibility and coordinated rollback into a shared process, reducing the orchestration work platform teams must maintain. As AI accelerates development, that matters. More code should not mean more release plumbing," Walter said.

Release control

The product is designed to address several common issues in large-scale software delivery, including the risk that one cluster failure can halt a wider rollout, limited visibility across many environments, and the time spent maintaining separate pipelines and release windows.

In practical terms, a platform team could use the feature to distribute a security fix for an add-on such as cert-manager in stages. If health checks identify a problem in an early wave, the rollout can be stopped before the change reaches the rest of the estate.

The model could also reduce release backlogs by embedding wave-based promotion, checks and thresholds into a single workflow. That would cut the need for repeated sign-offs and manual coordination across clusters.

Hong Wang, Co-Founder and Chief Executive Officer of Akuity, said the growth in cluster fleets was changing the release process for software teams.

"Companies now run fleets of clusters, and the release process has become what limits how fast they can ship. Fleet Management lets them move faster while keeping each rollout under control. Platform teams that make fleet management a first-class capability now will have infrastructure that scales with the business. Those that wait will feel the gap on every release," Wang said.

Akuity was founded by the creators of Argo CD and Kargo. The company focuses on software delivery tools for platform teams managing applications and infrastructure across large, distributed environments.