re:Invent 2025 confirmed FinOps' shift from reporting cloud costs to ongoing efficiency.
The FinOps conversation changed at re:Invent 2025. After years of focusing on visualizing cloud spend, a new fundamental truth is emerging:
Visibility alone doesn't lead to efficiency. Nearly every enterprise has dashboards, alerts, and allocation models, yet waste persists, engineering backlogs grow, and "optimization" remains reactive rather than an operational discipline. In 2025, cloud cost management remains a key challenge for 84% of organizations.
At re:Invent, we participated in many conversations with nearly everyone, from engineers to Fortune 500 leaders, expressing a similar sentiment. We don't need another unused-volume alert. We need to better understand the architecture.
AWS confirmed the shift toward ongoing efficiency by introducing its new Cost Efficiency Metric. The Cost Efficiency Metric is a standardized score that compares your last 30 days of optimizable cloud spend against today's potential savings. But this only addresses part of the problem: it quantifies your optimization gap but doesn't close it.
To address this gap, organizations are emphasizing an emerging discipline: ongoing efficiency.
Ongoing efficiency reduces costs by continuously monitoring how workloads consume resources and detecting architectural waste early. It gives teams the context they need to fix issues as they occur, not months later. This creates a stable efficiency posture regardless of how environments evolve...
Here is our take on why 2026 belongs to ongoing efficiency:
The End of Surface-Level Rightsizing
For more than a decade, billing data flagged basic waste like unattached volumes, idle nodes, or simple rightsizing opportunities.
This worked when infrastructures were predictable, monolithic, and VM-centric. But modern architectures like microservices, serverless, Kubernetes, managed databases, and AI inference workloads are too dynamic and interconnected for such shallow detection. Waste today hides as normal usage patterns. Modern waste identification requires deep analysis of workload behavior, scaling logic, configuration drift, token usage, data movement, and cross-service dependencies. Billing data offers no insight.
Engineers Reject Tools That Don't Speak Their Language
Context Is the Currency of Trust
The biggest barrier to cloud efficiency is credibility. Engineers ignore optimization recommendations when alerts lack context.
Legacy Cloud Cost Management (CCM) tools generate large volumes of non-actionable alerts. Alerts without consistent, reliable context deliver little value and are ignored, creating a barrier to ongoing efficiency. When the tools engineers are supposed to rely on miss performance realities and architectural context like dependency chains, scaling behavior, ownership, and nuance, engineers spend more time validating than acting. It becomes easy to lose trust.
Cloud Efficiency Posture Management (CEPM) tools differ from CCM tools. Rather than focusing on cost management alone, they focus on ongoing efficiency. This approach gains engineering trust by delivering Context-Rich Intelligence, the "who, what, and why" behind every insight:
- Who owns the resource
- What the workload does
- Why does the inefficiency exist
- How the inefficiency affects resilience, latency, and cost
- What the validated fix looks like
With CEPM tools, you can further solidify engineering buy-in with Detection Tuning. Detection Tuning allows you to adjust thresholds, override scopes, and align logic to each environment's architecture. The resulting alerts have fewer false positives and highly tailored insights. This leads to engineering buy-in.
Reliable detection turns "cost policing" into an Engineering-Native Workflow, bringing efficiency into how systems are designed, reviewed, and operated, and is a major step toward achieving ongoing efficiency.
Solving The Automation Trust Gap With CEPM
Automation is one of the most desired, least trusted aspects of cloud efficiency. Enterprises want faster, safer remediation, but can't grant open-ended write access. Automation that acts without transparency is a dealbreaker. CEPM addresses this trust gap by including and empowering engineers through engineering-native capabilities that drive action with confidence.
- Contextual Detection ensures every recommendation is rooted in actual workload behavior rather than basic billing anomalies.
- Conversational Validation (MCP) brings CEPM intelligence directly into developer workflows, enabling natural-language exploration of metrics, ownership, impact, and remediation paths — all inside the IDE or AI assistant.
- AI Guided Remediation (Prompt Remediation) generates IaC-aligned fixes through secure prompts that engineers review, adjust, and deploy via existing CI/CD pipelines.
Automation accelerates the work, but engineers authorize the action. This model preserves speed and accuracy without sacrificing control.
CEPM: The New Operating Model for Cloud Efficiency
CEPM is the engineering-native approach to ongoing efficiency. In addition to continuously monitoring your environment for hidden waste, CEPM tools integrate directly with familiar tools like Jira and ServiceNow.
CEPM doesn't replace the working mechanisms teams rely on, like reports, alerts, tickets, and scripts. Instead, it elevates their capabilities to match the complexity of modern cloud environments:
- Reporting evolves into continuous detection, surfacing deeper architectural inefficiencies.
- Alerts evolve into context-rich insights, grounded in ownership, behavior, and business impact.
- Tickets evolve into workflow-native engineering artifacts, pre-validated and ready for action.
- Scripts evolve into trusted automation paths, generated with guardrails through secure developer tools.
- Episodic optimization evolves into continuous posture management, embedding efficiency into daily operations.
Cloud Efficiency Moves Into the Engineering Workflow
2026 will be the year cloud efficiency becomes an engineering competency, not an afterthought, cost-center mandate, or reactive cleanup ritual.
With CEPM, organizations enter a new era where:
- inefficiencies are surfaced early and accurately
- insights arrive with context engineers trust
- remediation accelerates through trusted, transparent automation
- efficiency is woven into daily workflows, not bolted on afterward