Zesty Automates GPU Sharing Optimization for Kubernetes Teams

The News

Zesty, a Kubernetes optimization platform founded in 2019, has announced the extension of its resource management capabilities to GPU infrastructure with a new product called Autonomous GPU Resource Management. The announcement builds directly on recent NVIDIA advances in software-based GPU sharing, including Multi-Instance GPU (MIG), Multi-Process Service (MPS), and time-slicing, which introduced the technical flexibility for workloads to receive specific fractions of GPU memory and compute. Zesty’s layer adds continuous, policy-driven automation to those primitives, deciding in real time which workloads share each GPU, how much memory and compute each receives, and when to adjust, without requiring changes to applications, models, or Kubernetes manifests.

Analyst Take

The real problem isn’t GPU sharing. It’s the manual overhead that follows.

NVIDIA’s software-based GPU partitioning was a meaningful infrastructure advancement. MIG, MPS, and time-slicing collectively removed the hard constraint of whole-GPU allocation, giving platform teams the technical means to pack more workloads onto each card. But flexibility without automation creates a new class of operational burden. Someone still has to profile each workload, estimate its memory footprint, decide which workloads can safely cohabitate on a single GPU, and revisit those decisions as demand shifts. In practice, that someone is a platform engineer with too many competing priorities. The flexibility that NVIDIA provided was real. The capacity to act on it continuously was not.

That’s the gap Zesty is aiming to fill. Its autonomous agent draws on GPU memory usage, historical workload behavior, latency profiles, and out-of-memory event history to make allocation decisions continuously, within policies that teams configure per workload. This is the same model Zesty already applies to CPU and memory in Kubernetes: measure real demand, right-size allocations, adjust in motion. Extending it to GPUs is architecturally consistent and commercially logical given where infrastructure spending pressure is concentrated right now. GPU capacity is expensive, constrained, and increasingly central to both AI inference workloads and training pipelines that organizations are deploying at scale.

What ITDMs should understand about the cost math

For ITDMs, the business case here is straightforward but easy to underestimate. GPU overprovisioning is not a rounding error. When teams size GPU allocations statically, they’re sizing for peak demand and leaving substantial capacity idle the rest of the time. Across a fleet of workloads, that idle capacity compounds. Zesty’s pitch is that autonomous right-sizing converts that idle capacity into room for additional workloads, delaying or reducing the need to procure additional GPU hardware. The deployment model reinforces this: it operates as a lightweight agent alongside NVIDIA Run:ai and the Kubernetes scheduler, with no application changes required. The adoption friction is low, and the unit economics argument scales with GPU fleet size.

What developers and platform engineers should watch

For developers and platform engineers, the key architectural detail is that Zesty operates within policies set per workload, which means teams retain control over performance and availability guarantees. The system won’t sacrifice latency SLOs to pack in one more workload. That policy-driven constraint matters for AI inference specifically, where latency variance can affect model serving quality. The agent also deploys without manifest changes, which removes a common objection to platform-layer tooling. Teams running heterogeneous GPU workloads, mixing inference, batch training jobs, and developer experimentation, will find the most immediate value, because those workload types have very different demand profiles and are natural candidates for intelligent co-location.

The AI coding tool surge is relevant context here. According to ECI Research’s Google GovTech Survey, 49.6% of respondents estimated that 26% to 50% of their organization’s code will be assisted or generated by AI within the next 12 months. More AI-generated code means more AI inference infrastructure to run it, and more pressure on GPU capacity that most organizations haven’t fully planned for. Separately, ECI Research found that 54.4% of respondents described infrastructure provisioning as a moderate bottleneck, with provisioning taking a few days and multiple tickets. Autonomous GPU allocation sits directly in that bottleneck, removing a layer of manual capacity planning that currently slows teams down.

Looking Ahead

Zesty is making a calculated bet that GPU infrastructure management will follow the same maturation curve as Kubernetes compute optimization: first, teams get the raw primitives; then, automation layers emerge to make those primitives operationally viable at scale. The timing is credible. GPU demand is accelerating across enterprise AI workloads, procurement lead times for new hardware remain significant, and the cost of overprovisioning is no longer abstract. Vendors who can credibly demonstrate utilization improvement on existing GPU fleets will have a compelling conversation with CFOs and infrastructure leads in equal measure.

The competitive question is how durable Zesty’s position is as the hyperscalers and NVIDIA itself build more intelligence into their own scheduling and orchestration layers. NVIDIA Run:ai already competes in the GPU scheduling space, and Zesty’s agent works alongside it for now rather than against it. That positioning could shift. Over the next 12 to 18 months, watch whether Zesty deepens its integration with observability and FinOps platforms, where real-time utilization data becomes the connective tissue for broader infrastructure cost governance. The companies that win in autonomous infrastructure optimization won’t be the ones with the best algorithm for a single resource type. They’ll be the ones that build the most complete picture of workload demand across compute, memory, storage, and now GPU, and act on all of it simultaneously.

Authors

  • Paul Nashawaty

    Paul Nashawaty, Practice Leader and Lead Principal Analyst, specializes in application modernization across build, release and operations. With a wealth of expertise in digital transformation initiatives spanning front-end and back-end systems, he also possesses comprehensive knowledge of the underlying infrastructure ecosystem crucial for supporting modernization endeavors. With over 25 years of experience, Paul has a proven track record in implementing effective go-to-market strategies, including the identification of new market channels, the growth and cultivation of partner ecosystems, and the successful execution of strategic plans resulting in positive business outcomes for his clients.

    View all posts
  • Samantha Weston

    With over 15 years of hands-on experience in operations roles across legal, financial, and technology sectors, Sam Weston brings deep expertise in the systems that power modern enterprises such as ERP, CRM, HCM, CX, and beyond. Her career has spanned the full spectrum of enterprise applications, from optimizing business processes and managing platforms to leading digital transformation initiatives.

    Sam has transitioned her expertise into the analyst arena, focusing on enterprise applications and the evolving role they play in business productivity and transformation. She provides independent insights that bridge technology capabilities with business outcomes, helping organizations and vendors alike navigate a changing enterprise software landscape.

    View all posts