The News
At KubeCon + CloudNativeCon Europe 2026, StormForge used its briefing to sharpen a message that goes beyond simple Kubernetes cost savings. The company highlighted new capabilities across in-place pod resizing, Kubernetes cost allocation, policy-based configuration, deployment-aware optimization, and MCP support, all aimed at making automated rightsizing easier to trust and safer to deploy at scale.
Analysis
The Kubernetes Optimization Market Is Moving Past Basic Visibility
The Kubernetes cost and optimization market is entering a more mature phase. Most platform teams already know there is waste in their environments. The harder question is no longer whether optimization is needed, but whether recommendations can be safely operationalized without breaking production. That is an important shift in market posture, especially as platform teams are being asked to balance cost control with reliability, developer velocity, and AI-era infrastructure growth.
AI and infrastructure remain major spending priorities, with 74.3% of organizations prioritizing AI/ML, 60.7% prioritizing cloud infrastructure, and 43.6% prioritizing DevOps automation. At the same time, application environments are getting faster and more complex: 46.5% of organizations say deployment speed must improve by 50% to 100% versus three years ago, and another 24.7% say the increase needs to be 2x or more. In that environment, optimization tooling cannot just promise savings. It has to fit the reality of fast-moving production systems.
That is where StormForge appears to be repositioning. In the briefing, the team described the market as having moved beyond awareness. “People are at the point where they know what rightsizing tools are,” but the real issue now is “the trust of whether they’re willing to deploy the tools and it needs to just work.” That is a useful framing because it captures the current market challenge more accurately than generic FinOps messaging does.
StormForge Is Building Around Objection Handling, Not Just Recommendations
The most interesting part of StormForge’s KubeCon + CloudNativeCon Europe 2026 story is that its recent product work seems aimed less at producing recommendations and more at eliminating the reasons customers hesitate to apply them. That distinction matters. In many organizations, the blocker is not identifying waste. It is fear of workload disruption, uncertainty around application behavior, and the operational friction of scaling optimization policies across large estates.
That came through repeatedly in the briefing: “I was expecting everything to break,” and the key surprise from the proof of concept was that “it didn’t.” That is a striking quote because it gets to the emotional center of the buying problem. Platform and cloud teams do not reject optimization because they dislike savings. They reject it when savings appear to come with operational risk.
StormForge’s newest capabilities map directly to those concerns. In-place pod resizing is especially relevant here because it gives teams a path to resize resources without forcing restarts, which remains a major concern for organizations with workloads that are still not restart-tolerant. Policy-based configuration also pushes the platform further toward centralized governance, allowing platform teams to manage optimization rules across clusters, namespaces, and workload types without relying on manual tuning at every layer. Deployment-aware optimization may address another real-world problem by automatically recognizing relationships across blue-green, DR, and short-lived AI workloads rather than treating each workload in isolation.
Taken together, these updates suggest StormForge is trying to operationalize trust. The product is moving toward a model where customers do not have to constantly explain exceptions, manage rollout edge cases, or manually reconcile deployment patterns before they can safely act on recommendations.
Market Challenges and Insights
Developers and platform teams have previously handled these business challenges through a mix of overprovisioning, manual tuning, maintenance windows, and caution-driven delay. Those are rational responses. When teams do not fully trust automation, they protect reliability by leaving extra headroom in place or by making changes slowly and manually. The result is predictable: persistent waste, slower optimization cycles, and a gap between theoretical savings and realized savings.
That challenge intersects with broader observability and reliability pressures. 60.5% of organizations say real-time insights are a top observability priority, while 51.3% prioritize tracing and fault isolation for root cause analysis. Meanwhile, 45.7% say they still spend too much time identifying root cause and believe more observability investment would help. Those numbers matter here because rightsizing is rarely judged in isolation. It is judged in the context of whether teams can still diagnose problems, hit SLAs, and recover quickly when something goes wrong.
StormForge’s patent around HPA-aware rightsizing also fits this picture. The company emphasized that it can preserve HPA scaling behavior while rightsizing workloads, which speaks directly to a common customer objection: savings are not useful if they distort autoscaling patterns or destabilize runtime behavior. Similarly, the addition of network cost support in Kubernetes cost allocation is less flashy than some AI features, but strategically important. It helps StormForge compete more directly in replacement conversations where buyers want cost visibility and optimization in a single experience rather than separate tools.
The Pega example, while not yet public by name, also offers a telling signal. According to the briefing, StormForge identified more than 75% waste in a large environment and framed the opportunity in eight-figure savings terms. More notable than the size of the result, though, was the buying pattern. The initiative spanned FinOps, cloud leadership, and performance engineering, underscoring that Kubernetes optimization is not owned cleanly by one persona anymore. It is becoming a cross-functional operational issue, which raises the stakes for how vendors explain ROI, governance, and safe rollout.
Why This Matters Going Forward
What StormForge is surfacing at KubeCon + CloudNativeCon Europe 2026 is that the future of Kubernetes optimization may be less about recommendation quality alone and more about the pathway from recommendation to adoption. That is an important market transition. Customers increasingly expect tools to understand workload context, deployment topology, and runtime constraints before asking teams to trust automation in production.
That is also why the company’s internal message around “automation at the speed of trust” is directionally strong, even if it still needs refinement. The underlying point is sound: organizations already know there is waste, but they move only as fast as their operational confidence allows. The better StormForge can remove the practical objections up front, the more likely those savings are to become real rather than theoretical.
For developers and platform teams, that could matter in a few ways. It may reduce the need to choose between cost optimization and reliability. It may also make rightsizing more governable as platform teams expand policies across larger estates, especially where AI workloads and dynamic deployment patterns introduce more complexity. And over time, if StormForge continues adding more responsive, reliability-oriented behavior rather than static recommendation logic, it could help shift rightsizing from a periodic cost exercise into a more continuous operational discipline.
Looking Ahead
The optimization market is getting more crowded, but the real differentiation is beginning to move away from dashboards and into deployment safety, runtime awareness, and proof of operational reliability. Kubernetes teams do not need another reminder that waste exists. They need tooling that can help them act on it without destabilizing production or adding yet another management burden.
StormForge’s KubeCon + CloudNativeCon Europe 2026 briefing suggests the company understands that change in buyer psychology. Its recent launches are less about showing that optimization is possible and more about showing that it can be applied safely, repeatedly, and at scale. If that message continues to mature alongside stronger economic validation and public customer stories, StormForge may be well positioned in a market that increasingly values trusted execution over theoretical savings.
Edge Intelligence Moves From Experimentation to Production Scale
Open Kubernetes Meets AI Infrastructure in a More Composable Stack
Kubernetes Rightsizing Shifts From Cost Math to Operational Trust
OpenSearch Expands Its Role in AI Infrastructure and Open Collaboration
Local Cloud Development Emerges as the Missing Layer for AI-Driven AppDev
