The Flexera 2025 State of the Cloud Report is out, and the cloud landscape isn’t getting any simpler. For data professionals responsible for keeping systems running smoothly, the report’s insights feel familiar—and urgent.
Cost management remains the #1 challenge, multi-cloud is now standard operating procedure, and sustainability is rising fast on the priority list. These aren’t just trends—they’re reshaping how organizations think about their data workloads and cloud strategies.
To meet these challenges, organizations need more than usage dashboards and budget alerts. They need FinOps for Data—a new approach that helps teams connect operational behavior with financial impact.
The New Reality for Data Teams: More Clouds, More Cost Pressure
According to the Flexera report:
- 84% of organizations cite cloud spend as their top challenge.
- 87% are operating in multi-cloud environments.
- 22% are actively tracking cloud carbon footprints, with more planning to follow.
These numbers reflect the growing complexity of today’s IT landscape—and the mounting pressure on data teams to do more than just keep systems alive.
Data platforms—especially data warehouses and relational DBaaS—are often the biggest drivers of cloud spend, yet they’re also the least understood from a financial perspective.
That’s placing new demands on DBAs, engineers, and architects. These roles are evolving. They’re no longer just about uptime and performance—they now include:
- Justifying infrastructure and query costs
- Forecasting capacity and usage trends
- Participating in cost allocation and planning conversations
- Supporting sustainability and resource optimization goals
But these expectations can’t be met with high-level cloud billing tools alone. Visibility at the workload level is now essential.
How to Operationalize FinOps for Data
To close the gap between infrastructure usage and business impact, organizations should evolve their FinOps strategy in three key ways:
1. Go deeper than cloud bills.
Infrastructure-level data is useful—but insufficient. You need to understand what’s driving that spend. Are slow queries dragging performance? Is I/O being wasted on redundant processes? Is idle compute quietly draining budget?
Start by breaking down cost drivers at the workload, query, and instance levels—not just the service or region.
2. Incorporate performance telemetry into cost discussions.
If your cost trends are going up, but your workload hasn’t changed, you may have an efficiency issue—not a usage one. Integrate performance metrics (CPU, I/O, concurrency) into your FinOps reviews to catch these patterns before they spike your bill.
3. Use historical insights to guide future planning.
It’s not just about reacting to anomalies—FinOps maturity means identifying trends and preventing waste before it happens. Look at year-over-year workload growth, configuration drift, and code-level inefficiencies when planning budgets, sizing environments, or migrating to the cloud.
And if you’re migrating, remember: don’t just lift and shift. Use the opportunity to analyze on-prem workloads, right-size resources, and clean up technical debt. Optimizing before you migrate can result in massive cost savings down the road.
The Role of FinOps and the Expanding Influence of DBAs
The FinOps Foundation has laid out a robust framework for teams to align financial goals with engineering execution—including key capabilities like usage optimization, forecasting, and automation. But many organizations struggle to apply this framework beyond infrastructure.
That’s where database professionals can lead. With visibility into workload behavior, DBAs can:
- Surface inefficient code and propose cost-saving improvements
- Track the financial impact of tuning and indexing efforts
- Collaborate with finance to explain why certain workloads consume more
- Align technical decisions with budget goals, sustainability KPIs, and capacity planning
In short: FinOps isn’t just for finance and cloud operations anymore. It’s becoming a shared responsibility—and a huge opportunity—for data teams to step into strategic conversations.
The Bottom Line
The Flexera report confirms what many already know: cloud costs are rising, complexity is compounding, and sustainability is becoming a business imperative.
FinOps for Data offers a way forward. It empowers teams to look deeper into their data environments, understand the true cost of what’s running, and act with clarity—not guesswork. At Fortified, we believe this is the future of cloud operations—and it’s exactly why we built WISdom.
WISdom gives you a complete view of your database environment—from individual queries to cross-environment workload patterns. It helps teams:
- Identify inefficiencies that drive up cloud costs
- Analyze historical trends across servers, databases, and workloads
- Prioritize actions that improve performance and reduce spend
- Plan smarter migrations with data-backed recommendations
- Unify technical and financial teams around a shared view of impact
Whether you’re optimizing in the cloud or planning a move, WISdom helps you dig deeper, act smarter, and align technical decisions with business goals.
Curious how this could play out in your environment? Let’s talk about how WISdom’s workload intelligence can reshape your cloud strategy.