Presented by

Want to appear here? Talk with us

TOGETHER WITH FINOPSLY
The New FinOps Model: Interactive Assessment

How ready is your team for Value-Control?

  • Cloud waste is still high

  • AI spend is harder to predict

  • Control still happens too late

Assess whether your team can:

  • Estimate before spend is committed

  • Act before waste becomes budget impact

  • Prove savings become realized value

See where your FinOps model stands today.

Get your maturity score in 5 minutes.

OPEN SOURCE
How to use Open Source for Government Development Efficiency

The UK Government Digital Service is working on a new way to help local councils use open-source software more safely and effectively.

Right now, when government talks about open-source, it's usually about making their own code public so others can use it. But GDS wants to flip that around and help councils adopt proven open-source tools that already exist.

LocalGov Drupal shows what's possible when councils use mature open-source products. About 60 councils now use this open-source content management system, and the numbers are striking:

  • Website rebuilds cost 30% to 50% less

  • Developer costs drop by £30,000-£90,000

  • Ongoing costs can be 50% lower

  • Councils avoid around £50,000 per year in license fees

The missing piece: There's no standard process across UK government for checking if open-source products are safe and reliable enough for public use.

GDS is building an assurance framework that would evaluate products on seven key areas: maturity and stability, community health, security practices, fit for public sector needs, long-term support options, runtime efficiency, and responsible AI use.

ONLINE EVENTS
FinOps Weekly Extend Summit

Infrastructure is moving faster than FinOps tools built for the pre-AI era can track. AI workloads shift weekly. Kubernetes adds cost layers by the hour.

Extend Summit 2026 puts the seven companies solving this on one stage, and shows where Finout sits at the center of it.

📅​ Date: June 4th
🕗​ Time: 12:00 PM EST / 18:00 CEST
📍 Online

MEETUPS
FinOps Weekly Events

Subscribe to our Events

CLOUD PROVIDERS
AWS Billing Conductor fills Billing Gaps

AWS

AWS Clean Rooms now lets teams reassign who pays for SQL, ML, and data jobs, giving better control over shared cloud costs.

AWS Billing Conductor now shows accounts with billing gaps so you can fix missing billing group setups before they cause problems.

DocumentDB Serverless on version 8.0 can save up to 90% compared to always provisioning for peak capacity.

CUDOS v5.8.0 adds Bedrock cost-per-token visuals and Savings Plans coverage, making AI and database spend easier to track in one place.

Read All AWS Updates

Google Cloud

Cloud CDN now supports cache policies at multiple URL map levels, so teams can reduce egress costs by caching traffic more precisely by hostname, path, or headers.

Read All GCP Updates

Azure

Azure Virtual Network raised default limits for NSGs and route tables, helping teams scale without hitting limits that force costly architecture rework.

Read All Azure Updates

VIDEOS & PODCASTS
FinOps Interview & Hiring Tips

Learn how to ace a FinOps interview and how to hire top FinOps talent. In this episode, Puja from Epsilon shares insider advice on the skills, certifications, soft skills, and mindset that make a great FinOps practitioner.

WASTE
Idle Cloud Cost: Why It's Architectural Rent, Not Waste

Idle cloud costs have become the new surprise line item on your bill, and they're harder to fix than egress costs ever were. Idle costs look like waste on your dashboard, but they're often required by your architecture.

Three Types of Idle Cost You Can't Optimize Away

  1. Latency Reservation: GPU pools and pre-warmed Kubernetes nodes that must stay ready to avoid cold-start delays. A reserved H100 GPU at 5% utilization costs the same as one at 95%, but you can't right-size it because you need it available for burst workloads.

  2. Control Plane Residency: Management infrastructure that can't scale to zero, like Kubernetes control planes, service meshes, and security tools.

  3. Elasticity Floor Debt: Autoscaling that can't go below a minimum due to licensing requirements, replication needs, or reserved instance commitments. Your environment might scale up and down, but it never reaches zero.

Why Your FinOps Tools Miss This: Cost visibility tools flag idle resources as waste because they were built for a different era. They see unused capacity and recommend rightsizing.

But they can't tell the difference between a provisioning error and an architectural requirement. When your platform team designed a pre-warmed node pool to meet a latency SLA, they made a deliberate trade-off. Your cost dashboard sees waste, but the architecture review saw a requirement that couldn't tolerate a 30-second scale-up delay.

What This Means for Your Organization: Stop treating all idle capacity as waste. Start asking whether idle resources exist because of a forecasting error or an architectural requirement.

The industry still treats idle cost as operational waste, but increasingly it's architectural rent you're paying for specific service properties.

AI FINOPS
[CODE] Agent Reporting: Making AI Agents Visible to the People Who Pay For Them

Most companies can tell you if their AI agent works. Far fewer can tell you who owns it, what it costs per month, or which business outcome it actually supports. Douwe van de Ruit's third article in his Accountable Agents series tackles this gap head-on.

He argues that enterprise AI agents exist in a strange middle ground between traditional applications and human users.

Two Types of Accountability: An agent is "accountable" when it leaves behind evidence of what it did, which tools it used, how much it cost, and what value it created. A human still needs to own the business purpose, fund the agent, manage its lifecycle, and accept its risks.

What Should Actually Be In An Agent Report

Van de Ruit recommends tracking these elements for each agent:

  • Owner name and email (the person managing the technical side)

  • Sponsor name and email (the person accountable for business results)

  • Business stream it supports

  • Usage metrics (sessions, tool calls, tasks completed)

  • Direct costs (with room to add indirect and platform costs later)

  • Attributed value (both efficiency gains and outcome contributions)

  • Open risks (security, compliance, operational issues)

  • Azure Advisor recommendations for the resources supporting the agent

  • Recommended actions for owners or sponsors

The key insight: a report that only shows data gets ignored. A report that clearly shows what needs review becomes part of the operating rhythm.

🎖️ MENTION OF HONOUR
[CODE] Azure Full Subscription Inventory Script

You need to know what's running in your Azure environment, and you need to know it now. This comes up all the time in FinOps work. Most teams make this harder than it needs to be.

They try to export data from multiple portal views or jump straight into writing custom scripts. But Azure Resource Graph gives you a faster way to get a full inventory of your estate in seconds. Shannon made a single shot query that pulls the essentials:

It shows you subscription ID, resource group, resource name, resource type, location, SKU, tags, and the full resource ID. That covers most of the questions you need answered for cost analysis and governance work. You can run this in the Azure portal using Resource Graph Explorer, scope it to your subscriptions, and export to CSV. Or use the Azure CLI to output the results directly to a file. Either way, you get a spreadsheet you can sort, filter, and share with stakeholders.

This approach is especially valuable when you're starting a FinOps assessment. Before you can optimize costs or fix governance gaps, you need to know what's actually deployed. It's also helpful in environments that have grown organically over time through multiple teams or acquisitions.

Save 20% on FinOps Certifications

The job market is hungry for certified professionals who can prove results. Don't let your company's budget leak due to a lack of specialization.

Use code: FINOPSWEEKLY_20 to get an instant 20% discount on the most prestigious certification bundles:

  • FinOps Certified Practitioner (The foundation for success).

  • FinOps Certified Engineer (For high-level technical profiles).

  • FinOps Certified FOCUS Analyst (Specializing in data standards).

  • FinOps for AI (The frontier of modern efficiency).

Save $300 and get access to FinOps X

If you want to be in the room where the big decisions are made, you need to be at FinOps X. We’ve secured preferred access for our community:

  • Code: FINOPSWEEKLYX26

  • Your Savings: $300 USD.

  • Final Price: $899 (Official Price: $1,199).

COMMUNITY TOP 10 CONTRIBUTORS



1. @Afor Linda Odoma - 655.9000000000001 (Level 4)
2. @Ashley Bar-Shay - 194.56 (Level 3)
3. @Ben - 181.54000000000002 (Level 3)
4. @Diana - 132.5 (Level 3)
5. @Sam Nord - 129.52 (Level 3)
6. @Jackie MacRobert - 128.12 (Level 3)
7. @James Johnson - 119.44 (Level 3)
8. @Ramprasath - 103.98 (Level 3)
9. @Karna - 96.94 (Level 2)
10. @Diana - 95 (Level 2)

Increase your ranks by:
1. Replying to other people
2. Reacting to other people
3. Sharing knowledge and asking questions

Full ranking at: https://finopsweekly.com/community

Rate Today's Newsletter

Feedback = Better Newsletter for You

Login or Subscribe to participate

Recommended for you