Together with Glassity
The Continuous Cycle of Successful FinOps Implementation
FinOps isn’t a one-time fix; it’s a continuous process. But without structure, teams get stuck in reactive mode.
Glassity turns years of FinOps experience into a repeatable 5-step framework: from identifying savings to aligning stakeholders, executing and closing the loop with measurable outcomes.
This cycle helps teams go beyond fragmented efforts and build operational muscle needed for consistent optimization. We’ve seen it work and built our platform for clarity, alignment and actionability.
FINOPS JOBS
How to Find a FinOps Job
Are you on the hunt for FinOps jobs? This video shows how to use the FinOps Weekly Job portal to find FinOps career opportunities.
Learn how to search for your next finops role, create alerts, and streamline your job search process.
All new jobs are added into our #jobs channel in Slack as well!
CLOUD PROVIDERS
GCP CUDs now covering more services + Instance Scheduler Tag-Event Tracking
AWS
Instance Scheduler adds tag-event tracking and capacity retries to improve automation reliability and reduce idle instance waste.
Amazon EBS now allows up to four volume modifications per 24 hours changing size, type, or performance without downtime to match demand dynamically.
Amazon ECR introduces blob mounting for cross-repository layer sharing, eliminating duplicate storage costs for common base images.
Google Cloud
Committed Use Discount (CUD) recommendations now cover more machine types within the FinOps hub to maximize coverage.
Backup & DR Service cost reports (GA) offer granular visibility into retention and replication spend.
BigQuery leverages Gemini Cloud Assist (preview) to detect high-cost queries, while Cloud Monitoring now links trace spans to application dashboards, helping engineers pinpoint costly performance inefficiencies.
Azure
No Updates (again …)
FINOPS EVENTS
Online Webinar: Automating Cloud Ownership Mapping at Scale
Our friends from Wiv are doing a session the 26th. It’s a hands-on, technical walkthrough built for the people doing the work: platform engineers, FinOps leads, and DevOps teams who deal with this mess every day. They’ll cover:
Why ownership breaks down in real-world orgs
What needs to be in place to fix it
How automation is being used in production today
A live walkthrough of real workflows
PODCASTS
Most FinOps Practitioners Get This Wrong
We talk with Erik Norman about adressing misalignments, creating a context-aware FinOps, adapting practices for different company sizes, overcoming challenges in large organizations.
AZURE
Azure Data Transfer Costs Full Guide
Azure data transfer costs can eat up your cloud budget if you don't understand how they work.Microsoft just published a detailed breakdown of when you pay for moving data around in Azure and when you don't.
You won't pay anything when data moves between VMs in the same virtual network. Moving data across availability zones is also free.
Data transfer gets expensive when it crosses certain boundaries. Moving data between peered virtual networks costs money on both sides - you pay for data going out and coming in. The price depends on whether your networks are in the same region or different geographic zones.
Private endpoints charge you for data processing, not just transfer. If you're reading from a storage account through a private endpoint, you pay inbound charges. Writing to storage means outbound charges.
The good news is that accessing private endpoints across peered networks only triggers the private endpoint fees, not the peering fees.
Standard load balancers charge based on rules and data volume. When you route traffic through a firewall or network appliance in a hub network, you essentially pay twice - once from the source to the firewall, and again from the firewall to the destination. This hub-and-spoke pattern is common for security, but it doubles your data transfer costs.
Data coming into Azure from the internet is free. Data leaving Azure to the internet costs money, and the price varies by region and volume.
You can choose between two routing options that affect both performance and cost. Microsoft network routing keeps traffic on their backbone longer but costs more. Internet routing hands off to transit providers sooner and costs less.
Connecting your on-premises network to Azure through ExpressRoute or VPN adds another layer of costs. Traffic from on-premises to a spoke network through a hub only charges peering fees once. But if you inspect that traffic with a firewall in the hub, you pay the full VM-to-VM rates in both directions.
Your architecture choices directly control these costs.
NETWORK
Cloud Egress Fees Guide
Cloud egress fees are the hidden tolls that can turn your cloud bill into a surprise expense.
AWS charges $0.09 per gigabyte after the first 100GB free each month. That might sound small until you're moving terabytes of data. A company transferring 50TB monthly pays over $4,000 just in egress fees. Here's how to fight back:
Use a content delivery network to cache data closer to users instead of repeatedly pulling from origin storage.
Keep your compute and storage in the same region to avoid cross-region transfer fees.
Batch your data transfers into fewer, larger movements instead of many small ones.
Set up private network connections for predictable costs at scale.
Choose cloud providers that don't punish you for accessing your own data.
Egress fees are designed to keep you locked in, not to cover actual costs. Understanding how they work gives you the power to plan around them or choose providers that won't trap your data behind a paywall.
🎖️ MENTION OF HONOUR
FinOps is About Asking Better Questions
FinOps has a reputation problem, and it's time to fix it. Too many teams see FinOps as the department that shows up to cut costs or send budget alerts that fire too late. But that's not what FinOps is really about.
FinOps is about understanding your cloud spending and making smart choices that connect to real business results. The best way to tell if your organization is doing FinOps well has nothing to do with fancy tools or dashboards.
It shows up in the questions your teams ask. Here are the questions that reveal how mature your FinOps practice really is:
Who owns FinOps in your company?
Do your teams trust the cost data?
Are you predicting costs or just reacting?
Do engineers care about costs?
And many more, available in the full article Shannon did
The most important question of all is this: If your cloud costs doubled tomorrow, would you understand why and know what to do about it?
If the answer is no, that's not failure. That's information about where you need to focus next.
Good FinOps is rarely loud.
It looks like engineers asking cost questions before anyone prompts them.
It looks like finance trusting the numbers without double checking everything in spreadsheets.
It looks like leadership being surprised less often, even when spending grows.
When FinOps is working well, cloud cost stops being a source of tension and becomes just another part of engineering quality.
PROFESSIONAL SPOTLIGHT
Afor Linda Odoma
FinOps Community Power
I can objectively say Afor Linda is a core element in our FinOps Weekly Slack. She greets everybody, making it a great place to be. I’m so grateful she’s part of this.
FINOPS COURSES
Azure FinOps Cost Optimization Course Starting Soon!
February 9th Kickoff. Enrollment closing
Alfonso is creating a masterpiece.
The biggest educational we’ve done till date.
Learn all you need to optimize resources in Azure.
199€ Super Early Bird – Ends December 21st (CLOSED)
⏭ 299€ Early Bird: Opens January 2nd – Ends Today
499€ Launch Offer: Opens XXX
699€ Starting Offer: Opens XXX
999€ Final Price