Presented by

Want to appear here? Talk with us

Cloud environments are quickly evolving. Complexity is rising, AI is reshaping what’s possible, and governance is becoming essential to keep innovation sustainable and cost controlled. Last quarter, we introduced FinOps+, a framework to accelerate value in this new landscape. In this next session, we’re taking it further.

Join us for a new webinar to explore:

Don’t miss this opportunity to learn practical strategies to scale governance, optimize spend, and integrate AI into your FinOps journey beyond just public cloud.

I'm releasing all FinOps Summit 2025 slides.

Most summits lock content behind paywalls.

We're doing the opposite.

What you'll get access to:

20+ slide decks from industry experts
Keynote presentations on cost management
Cloud optimization strategies that saved millions
Frameworks you can implement Monday morning
Real FinOps case studies from Fortune 500 companies
Best practices from the biggest names in cloud finance

Why am I doing this?

Because FinOps knowledge should be accessible.
Because these speakers created incredible value.
Because your team deserves to learn from the best.

AWS Amazon ECS Managed Instances is now generally available across all commercial regions. This fully managed compute option automatically scales EC2 instances to match workloads and optimizes task placement to reduce infrastructure costs.

Predictive Scaling for EC2 Auto Scaling expanded to six more regions. It learns from historical patterns to proactively launch instances before demand spikes, helping avoid over-provisioning and reducing EC2 costs. Works alongside existing policies like Target Tracking.

AWS Resource Explorer now supports 47 additional resource types including Bedrock, Shield, and Glue. This broader visibility helps FinOps teams find and categorize resources faster for cost allocation, tagging audits, and cleanup efforts.

Amazon EBS launched new CloudWatch metrics: per-volume average IOPS/throughput and instance limit detection. These help pinpoint performance bottlenecks, align provisioned capacity with actual usage, and catch misprovisioned instances—all at no additional charge.

Lambda async payload limit increased from 256 KB to 1 MB, simplifying event-driven architectures and reducing workarounds. Note the pricing model: first 256 KB counts as 1 request, then each 64 KB increments charges.

Read All AWS Updates

Major Azure outage traced to Azure Front Door configuration change affected 12+ services including Databricks, Maps, and Virtual Desktop. Downstream impacts hit Microsoft 365 and production systems like Alaska Airlines. Microsoft rolled back to last known good state, with full mitigation taking ~8 hours.

Capacity Reservation Groups can now be shared across subscriptions in Public Preview. Previously limited to single subscriptions, on-demand CRGs now enable centralized capacity management, resource reuse, and cost-effective scale-out across teams and business units.

Read All Azure Updates

Cloud SQL for PostgreSQL now proactively cancels high-memory connections to prevent out-of-memory failures. This reduces instance crashes, forced restarts, and emergency scaling costs—delivering more stable database behavior and fewer operational fire drills.

Read All GCP Updates

This doesn’t stop! Looking forward to have you all the 13th of November to explore the Hybrid FinOps.

Discover how FinOps 2.0 strategies deliver comprehensive optimization across your entire technology portfolio.

You'll Learn How To:

Achieve total cost visibility across data centers, multi-cloud, SaaS, and AI infrastructure

Optimize the complete technology stack with unified intelligence and automation

Break down silos between FinOps, ITAM, procurement, and engineering teams

Jeremy Chaplin, Gerhard Behr & Victor Garcia

Two teams that used to work separately are now joining forces to help companies manage their technology spending better. FinOps handles the money side of cloud and tech costs. ITAM keeps track of software licenses and contracts. When they work together, companies save money, avoid problems, and run smoother.

Money Savings

One big company was spending over 150 million dollars each year on cloud and software. Different teams were buying things on their own without talking to each other. FinOps brought all the spending data together and showed everyone what they were buying. ITAM tracked all the contracts and when they needed to be renewed. Together, they helped the company negotiate better prices and make smarter choices about what to keep and what to cancel.

Avoiding Big Fines

Another company had a scary problem. Teams were buying software through different channels without telling anyone. Some bought things with credit cards. Others used cloud marketplaces. Nobody knew what licenses they actually owned. This meant they could get hit with huge fines during audits. FinOps found all the hidden spending in the cloud. ITAM checked if they had the right licenses for everything.

Stopping Waste

One organization made a common mistake. They got a great discount by agreeing to buy 1,000 software licenses. But they only used 500 of them in the first year. They were paying for 500 licenses that nobody touched. FinOps tracked how many people actually used the software. ITAM showed what the contract required. Together, they helped the company renegotiate the deal to match what they really needed.

When FinOps and ITAM work as one team, companies get a complete picture of their tech spending, make better buying decisions, and avoid expensive surprises.

Read More

In this episode, we dive deep into the Hybrid FinOps Challenge — where cloud, on-prem, SaaS, and AI collide.

Learn more about Hybrid FinOps on our event with Flexera

AWS just made it easier to track how much money you spend on different apps running in your Kubernetes clusters. They added a new feature that lets you use Kubernetes labels to split up and understand your costs better.

Two real world examples show why this matters.

Setting this up takes three main steps. You turn on split cost allocation in your billing settings. You activate the labels you want to track as cost allocation tags. Then you set up your cost reports to include this split cost data.

After you turn it on, AWS scans all your Kubernetes pods and pulls in their labels. Within 24 hours, you'll see new columns in your cost reports showing the costs broken down by these labels. You can keep adding, removing, or changing labels as your needs change.

We teach you how to implement tagging policies to control your Kubernetes costs in our Mastering FinOps Course with Alfonso San Miguel, now available on demand with special pricing.

Read More

Spending on public cloud services will hit $723 billion in 2025, up more than 20 percent from last year. The problem is simple: the cloud makes it too easy to use more resources than you need. Anyone in a company can spin up new servers instantly, and those costs add up fast.

Most companies are wasting about one-quarter of what they spend on cloud services. This happens for three main reasons. First, they guessed wrong about how much they would actually use. Second, they moved old systems to the cloud without fixing them to work better there. Third, they forgot to turn off their old equipment, so now they're paying for both the cloud and their old data centers at the same time.

Most companies with big cloud bills are good at negotiating better contracts. But they're not as good at making sure they only use what they need, and they rarely redesign their systems to run more cheaply.

Special tools can help track and control cloud spending across different teams and cloud providers. These tools do more than the basic ones that come with each cloud service. They can show you exactly where money is going and automatically fix common problems.

The real fix requires changing how companies think about cloud costs. It's not just an IT problem anymore. Finance teams need to know the total spend. Business units need to see their own costs. IT teams need the right tools to keep things running well without wasting money.

Read More

Technology decisions directly impact business outcomes, yet cost often arrives too late in the conversation. Cost-aware architecture brings economics into design from the start, not after deployment.

A Simple Framework

Combine three approaches: use TOGAF to structure the lifecycle, FinOps to operationalize cloud spend (tagging, allocation, commitments), and TBM to standardize cost taxonomy into business views. Together they create a closed loop from architectural intent to real-time cost telemetry to portfolio decisions.

Where to Start

Begin with a short Options Analysis comparing T-shirt sized alternatives (S/M/L) showing run-rate costs, risks, features, and operational footprint. Capture decisions in a one-page Architecture Decision Record (ADR).

Maintain an Efficiency Matrix in your architecture repo: track unit economics (cost per order/API call), spend attribution, efficiency levers, and reliability targets. Review monthly alongside ADRs to keep design, cost, and outcomes aligned.

Read More

Azure FinOps MVP

Mike was one of the first ones I talked about FinOps. His work on Azure is great, and love the interviews he does (as someone who chatted with him several times!) Always good to have people like this in the community.

Connect with the Professional of the Week

We’ve created Learn FinOps Weekly because we believe that hands on learning is the way to make real impact with IT Budgets.

With courses made by FinOps Professionals, well-known Authors in the industry.

Carefully curated with the FinOps Weekly Team to align with our actionable way of doing things.

We have a limited time offer for the launch that ends today.

Please take advantage as we are increasing pricing in the coming days.

Let’s learn actionable FinOps together

See you all inside!