groundcover Launches Autonomous Infrastructure Beta, Using Production Data It Already Collects to Right-Size Kubernetes Workloads
SAN FRANCISCO -- Nov. 3, 2026 - groundcover, the world’s leading bring-your-own-cloud (BYOC), eBPF and OpenTelemetry (OTel)-native observability platform, today announced the beta of groundcover Autonomous Infrastructure, which continuously adjusts CPU and memory requests for Kubernetes workloads based on how they behave in production. Autonomous Infrastructure is built on technology from Wand, the Kubernetes resource optimization platform groundcover acquired in September, and runs on the groundcover eBPF sensor. The beta is available at no additional cost.
The groundcover sensor already collects the production telemetry Autonomous Infrastructure needs, meaning teams on a supported sensor version don't need to install anything new or wait for data to accumulate. The first time they open it, they see how much CPU and memory each workload requests compared to what it uses, what it could save, and which workloads are running short on the resources they need. Nothing changes until an engineer turns it on and chooses which workloads, namespaces or clusters it manages.
"Last month we said you need to see what's happening before you can understand it, and understand it before you can safely act," said Shahar Azulay, CEO and co-founder of groundcover. "Autonomous Infrastructure is where those steps come together for our customers. They can open it today and see what their clusters could save, using production data that already lives in their own cloud, before they let it change anything."
The Cost of Setting Resources Once
Kubernetes asks teams to set CPU and memory requests before a workload runs under real load, and those settings are rarely revisited. Teams typically learn a request was wrong in one of two ways: a service starts hitting out-of-memory errors and slows down, or the monthly cloud bill arrives higher than expected.
Cutting requests to save money works until the next traffic spike, when the same cut can cause a production incident. Because few teams tune requests continuously, these problems tend to surface a week or a month after they start.
Autonomous Infrastructure combats this using telemetry the groundcover eBPF sensor already collects to adjust resource requests in real time, within bounds the customer sets. It balances two goals that pull in opposite directions:
- Cost: Lowering requests for over-provisioned workloads to remove headroom that goes unused.
- Stability: Raising requests for workloads running short, before throttling or out-of-memory errors.
The Autonomous Infrastructure view shows estimated monthly savings next to the number of under-provisioned workloads, and charts potential savings against achieved savings over time. During the beta, customers set their own price per CPU and memory unit to calculate dollar figures.
groundcover plans to add billing integration in stages, starting with publicly available cloud pricing and later connecting to billing data such as the AWS Cost and Usage Report (CUR). Coverage also appears in views engineers already use in groundcover, showing how many workloads are managed autonomously in each cluster and namespace.
Engineers Decide What Autonomous Infrastructure Manages
Most resource optimization tools size each workload on its own. A request that looks right for one service can still starve its neighbors on a crowded node. Autonomous Infrastructure makes stability its first constraint and sizes workloads with the full environment in view. Before raising a request, it considers how workloads pack onto the node and how much headroom remains, so an increase for one workload does not push the node out of resources.
Drawing on the full-fidelity data the groundcover eBPF sensor collects across applications and infrastructure, Autonomous Infrastructure sees how a workload behaves alongside everything else running on the node and in the cluster, rather than relying on a narrow set of resource metrics.
It's opt-in at every level:
- It is off by default; an administrator turns it on for individual deployments or for every deployment in a namespace or cluster.
- Policies set minimum and maximum bounds for CPU and memory requests, and any setting can be kept as-is.
- During the beta, it changes resource requests only; limits stay as they are, and raising one requires user confirmation.
- Every policy change is versioned, and an audit log records who assigned each workload to a policy and when.
Teams can start with lower-risk workloads, such as development namespaces, and leave others untouched, such as a production database that needs room to grow.
"Most teams find out their resources were wrong a week or a month late, from an out-of-memory error or from the cloud bill," said Shon Lev-Ran, co-founder of Wand and architect at groundcover. "Autonomous means the system keeps up with those changes for you. It doesn't mean you give up control. You choose which workloads it touches and the bounds it works within, and you can see every change it made."
Availability
The Autonomous Infrastructure beta is available now to all groundcover customers running the groundcover sensor on Kubernetes, at no additional cost. groundcover is also inviting design partners to work directly with its product team during the beta. groundcover will demonstrate Autonomous Infrastructure at KubeCon + CloudNativeCon North America in Salt Lake City, Nov. 9–12, at booth #111.
To learn more about how Autonomous Infrastructure works, visit the website and read our blog post.
About groundcover
groundcover is the full-stack observability platform for engineers & agents, allowing teams to monitor everything they run in their cloud, without compromising on data, control, or cost. It’s deployed inside the customer’s cloud premises and provides complete visibility into applications, infrastructure, and AI workloads without operational overhead. The platform offers unlimited data coverage at a fraction of the cost of legacy observability tools. Founded in 2021, the company is backed by leading global investors, including One Peak, Morgan Stanley Expansion Capital, Zeev Ventures, Angular Ventures, Heavybit and Jibe. Learn more at https://www.groundcover.com.
Media Contact
Chris Churilo, VP of Marketing
