Groundcover Acquires Wand Cloud to Unify Kubernetes Observability and Autonomous Resource Sizing

Groundcover, an observability vendor operating on a bring-your-own-cloud (BYOC) architecture, announced its acquisition of Kubernetes optimization startup Wand Cloud. Wand's founding team and engineering staff are joining Groundcover, with its automated resource-tuning engine set to be embedded into Groundcover's core telemetry offering. The purchase represents Groundcover's first corporate acquisition following its recent $100M Series C funding round. Setting accurate CPU and memory requests across modern microservices remains an operational bottleneck for engineering teams. Sizing container resource requests manually usually happens before workloads face realistic production traffic patterns; overestimating requests compounds idle, unallocatable resources across clusters, driving cloud costs up, while underestimating risks CPU throttling, memory-pressure eviction, and latency spikes. Wand tackles this by co-optimizing vertical pod resizing, horizontal pod autoscaling, and cluster-level node capacity dynamically inside the customer's cluster based on active traffic and memory utilization profiles. This move highlights an accelerating transition in cloud-native management from passive monitoring to automated, closed-loop infrastructure adjustments. Standard native tools—such as the Horizontal Pod Autoscaler (HPA), Vertical Pod Autoscaler (VPA), and Cluster Autoscaler—often operate in silos or introduce configuration friction when applied concurrently to dynamic workloads. By merging eBPF-driven observability and telemetry history directly with actuation software, platforms can optimize capacity based on actual usage patterns without exporting sensitive workload metrics outside the customer's environment. In practice, infrastructure and platform engineers should evaluate how autonomous tuning impacts application stability, especially for workloads with unpredictable traffic spikes or distinct warm-up memory characteristics. Integrating vertical adjustments alongside horizontal scaling policies requires clear guardrails, strict disruption budgets, and robust testing to verify that runtime pod mutations do not disrupt critical request pathways during peak load transitions.