CloudFinOpsKit
@cloudfinopskit.com
One-click FinOps cost assessments for Azure, AWS and Google Cloud. Find the waste, prove the savings. cloudfinopskit.com
A cheaper model that fails twice costs more than an expensive one that works first time.
The cost of failure never lands on the model that failed. Retries inflate call volume. Escalations show under the premium model's line. Rework shows up in salaries.
Built a calculator.
The cost of failure never lands on the model that failed. Retries inflate call volume. Escalations show under the premium model's line. Rework shows up in salaries.
Built a calculator.
September 29, 2026 at 5:53 PM
A cheaper model that fails twice costs more than an expensive one that works first time.
The cost of failure never lands on the model that failed. Retries inflate call volume. Escalations show under the premium model's line. Rework shows up in salaries.
Built a calculator.
The cost of failure never lands on the model that failed. Retries inflate call volume. Escalations show under the premium model's line. Rework shows up in salaries.
Built a calculator.
Reposted by CloudFinOpsKit
DOGE demanded root access.
Not auditor access. Not admin.
They were given “tenant owner” privileges in Azure — full control over the NLRB’s cloud, above the CIO himself.
This is never supposed to happen.
Not auditor access. Not admin.
They were given “tenant owner” privileges in Azure — full control over the NLRB’s cloud, above the CIO himself.
This is never supposed to happen.
April 18, 2025 at 12:11 AM
DOGE demanded root access.
Not auditor access. Not admin.
They were given “tenant owner” privileges in Azure — full control over the NLRB’s cloud, above the CIO himself.
This is never supposed to happen.
Not auditor access. Not admin.
They were given “tenant owner” privileges in Azure — full control over the NLRB’s cloud, above the CIO himself.
This is never supposed to happen.
Wasted cloud spend sits near 30% in most surveys, and a disciplined first year recovers 20-35% of it.
Almost none of that is architecture.
Here is the AWS waste sweep, in the order I run it.
Almost none of that is architecture.
Here is the AWS waste sweep, in the order I run it.
September 29, 2026 at 5:28 PM
Wasted cloud spend sits near 30% in most surveys, and a disciplined first year recovers 20-35% of it.
Almost none of that is architecture.
Here is the AWS waste sweep, in the order I run it.
Almost none of that is architecture.
Here is the AWS waste sweep, in the order I run it.
Before you pay for an AWS cost tool, exhaust the free ones.
Cost Explorer, Budgets, Cost Anomaly Detection, Compute Optimizer, Cost Optimization Hub. All native, all free, genuinely capable.
We put our own tool on the list too, and said where it does not belong.
Cost Explorer, Budgets, Cost Anomaly Detection, Compute Optimizer, Cost Optimization Hub. All native, all free, genuinely capable.
We put our own tool on the list too, and said where it does not belong.
September 29, 2026 at 5:25 PM
Before you pay for an AWS cost tool, exhaust the free ones.
Cost Explorer, Budgets, Cost Anomaly Detection, Compute Optimizer, Cost Optimization Hub. All native, all free, genuinely capable.
We put our own tool on the list too, and said where it does not belong.
Cost Explorer, Budgets, Cost Anomaly Detection, Compute Optimizer, Cost Optimization Hub. All native, all free, genuinely capable.
We put our own tool on the list too, and said where it does not belong.
Amazon Bedrock breaks the FinOps playbook, because there is nothing to right-size.
No instance. No resource to delete. The unit of cost is the token, and the bill is driven by HOW you call the model - not what you provisioned.
Per-model token visibility comes first.
No instance. No resource to delete. The unit of cost is the token, and the bill is driven by HOW you call the model - not what you provisioned.
Per-model token visibility comes first.
September 29, 2026 at 5:22 PM
Amazon Bedrock breaks the FinOps playbook, because there is nothing to right-size.
No instance. No resource to delete. The unit of cost is the token, and the bill is driven by HOW you call the model - not what you provisioned.
Per-model token visibility comes first.
No instance. No resource to delete. The unit of cost is the token, and the bill is driven by HOW you call the model - not what you provisioned.
Per-model token visibility comes first.
A cost spike caught on day 2 costs you two days.
The same spike found on next month's invoice costs you thirty.
AWS Cost Anomaly Detection is free, ML-based, and learns your pattern per service. Five minutes to set up.
Most teams still have not switched it on.
The same spike found on next month's invoice costs you thirty.
AWS Cost Anomaly Detection is free, ML-based, and learns your pattern per service. Five minutes to set up.
Most teams still have not switched it on.
September 29, 2026 at 5:19 PM
A cost spike caught on day 2 costs you two days.
The same spike found on next month's invoice costs you thirty.
AWS Cost Anomaly Detection is free, ML-based, and learns your pattern per service. Five minutes to set up.
Most teams still have not switched it on.
The same spike found on next month's invoice costs you thirty.
AWS Cost Anomaly Detection is free, ML-based, and learns your pattern per service. Five minutes to set up.
Most teams still have not switched it on.
AWS commitments, ranked by what you give up:
Compute Savings Plan ~66% - flexes across family, region, even Graviton
EC2 Instance SP ~72% - locked to family + region
Standard RI ~72% - no family change, but sellable
Convertible RI ~54% - exchangeable
Depth costs flexibility.
Compute Savings Plan ~66% - flexes across family, region, even Graviton
EC2 Instance SP ~72% - locked to family + region
Standard RI ~72% - no family change, but sellable
Convertible RI ~54% - exchangeable
Depth costs flexibility.
September 29, 2026 at 5:16 PM
AWS commitments, ranked by what you give up:
Compute Savings Plan ~66% - flexes across family, region, even Graviton
EC2 Instance SP ~72% - locked to family + region
Standard RI ~72% - no family change, but sellable
Convertible RI ~54% - exchangeable
Depth costs flexibility.
Compute Savings Plan ~66% - flexes across family, region, even Graviton
EC2 Instance SP ~72% - locked to family + region
Standard RI ~72% - no family change, but sellable
Convertible RI ~54% - exchangeable
Depth costs flexibility.
Since February 2024, AWS bills every public IPv4 address - attached or not, used or not.
Which quietly turned "we have a few spare Elastic IPs" into a line item.
Releasing idle ones is the cheapest cleanup in AWS. No performance risk, no sign-off, no downside.
Which quietly turned "we have a few spare Elastic IPs" into a line item.
Releasing idle ones is the cheapest cleanup in AWS. No performance risk, no sign-off, no downside.
September 29, 2026 at 5:13 PM
Since February 2024, AWS bills every public IPv4 address - attached or not, used or not.
Which quietly turned "we have a few spare Elastic IPs" into a line item.
Releasing idle ones is the cheapest cleanup in AWS. No performance risk, no sign-off, no downside.
Which quietly turned "we have a few spare Elastic IPs" into a line item.
Releasing idle ones is the cheapest cleanup in AWS. No performance risk, no sign-off, no downside.
Send a thousand rows to a model as a JSON array and you just paid for eight field names a thousand times.
As CSV the headers are declared once. Models read delimited data fine.
Same answer, a fraction of the input tokens.
Token count is a property of your code, not the model.
As CSV the headers are declared once. Models read delimited data fine.
Same answer, a fraction of the input tokens.
Token count is a property of your code, not the model.
September 29, 2026 at 3:10 PM
Send a thousand rows to a model as a JSON array and you just paid for eight field names a thousand times.
As CSV the headers are declared once. Models read delimited data fine.
Same answer, a fraction of the input tokens.
Token count is a property of your code, not the model.
As CSV the headers are declared once. Models read delimited data fine.
Same answer, a fraction of the input tokens.
Token count is a property of your code, not the model.
A 20-step agent does not cost twice what a 10-step agent costs. About four times.
Models are stateless, so the orchestrator re-sends the whole history every step. Step 10 pays for steps 1-9 again.
Cost grows with the SQUARE of the step count.
max_tokens does not bound a loop.
Models are stateless, so the orchestrator re-sends the whole history every step. Step 10 pays for steps 1-9 again.
Cost grows with the SQUARE of the step count.
max_tokens does not bound a loop.
September 24, 2026 at 8:01 PM
A 20-step agent does not cost twice what a 10-step agent costs. About four times.
Models are stateless, so the orchestrator re-sends the whole history every step. Step 10 pays for steps 1-9 again.
Cost grows with the SQUARE of the step count.
max_tokens does not bound a loop.
Models are stateless, so the orchestrator re-sends the whole history every step. Step 10 pays for steps 1-9 again.
Cost grows with the SQUARE of the step count.
max_tokens does not bound a loop.
Most common AI finding we see: a model deployment that served zero requests in 30 days and billed anyway.
Someone ran a POC. The project moved on. The deployment did not.
No quality trade-off, no code change, no A/B test. Just delete it.
Cleanest money on any AI bill.
Someone ran a POC. The project moved on. The deployment did not.
No quality trade-off, no code change, no A/B test. Just delete it.
Cleanest money on any AI bill.
September 24, 2026 at 7:57 PM
Most common AI finding we see: a model deployment that served zero requests in 30 days and billed anyway.
Someone ran a POC. The project moved on. The deployment did not.
No quality trade-off, no code change, no A/B test. Just delete it.
Cleanest money on any AI bill.
Someone ran a POC. The project moved on. The deployment did not.
No quality trade-off, no code change, no A/B test. Just delete it.
Cleanest money on any AI bill.
Most common AI finding we see: a model deployment that served zero requests in 30 days and billed anyway.
Someone ran a POC. The project moved on. The deployment did not.
No quality trade-off, no code change, no A/B test. Just delete it.
Cleanest money on any AI bill.
Someone ran a POC. The project moved on. The deployment did not.
No quality trade-off, no code change, no A/B test. Just delete it.
Cleanest money on any AI bill.
September 24, 2026 at 1:51 PM
Most common AI finding we see: a model deployment that served zero requests in 30 days and billed anyway.
Someone ran a POC. The project moved on. The deployment did not.
No quality trade-off, no code change, no A/B test. Just delete it.
Cleanest money on any AI bill.
Someone ran a POC. The project moved on. The deployment did not.
No quality trade-off, no code change, no A/B test. Just delete it.
Cleanest money on any AI bill.
Terminate an EC2 instance and any volume with DeleteOnTermination=false survives it.
It drops to "available", attached to nothing, billed in full - EBS bills provisioned capacity, not usage.
A forgotten 500GB io2 with 5k IOPS is about $4,700 a year.
It drops to "available", attached to nothing, billed in full - EBS bills provisioned capacity, not usage.
A forgotten 500GB io2 with 5k IOPS is about $4,700 a year.
September 22, 2026 at 1:43 PM
Terminate an EC2 instance and any volume with DeleteOnTermination=false survives it.
It drops to "available", attached to nothing, billed in full - EBS bills provisioned capacity, not usage.
A forgotten 500GB io2 with 5k IOPS is about $4,700 a year.
It drops to "available", attached to nothing, billed in full - EBS bills provisioned capacity, not usage.
A forgotten 500GB io2 with 5k IOPS is about $4,700 a year.
Ask three clouds what a resource cost last month and you used to get three schemas, three definitions of "cost", three discount models.
FOCUS ends that. One billing schema, and every major cloud now emits it natively - Microsoft, AWS, Google, Oracle.
One query, any provider.
FOCUS ends that. One billing schema, and every major cloud now emits it natively - Microsoft, AWS, Google, Oracle.
One query, any provider.
September 11, 2026 at 12:57 PM
Ask three clouds what a resource cost last month and you used to get three schemas, three definitions of "cost", three discount models.
FOCUS ends that. One billing schema, and every major cloud now emits it natively - Microsoft, AWS, Google, Oracle.
One query, any provider.
FOCUS ends that. One billing schema, and every major cloud now emits it natively - Microsoft, AWS, Google, Oracle.
One query, any provider.
Before you panic about a cloud bill spike, check the date range.
The most recent 1-2 days of cost data are ESTIMATES, and they often revise down.
A good share of "our bill exploded" turns out to be unfinalized days.
Rule out the false alarm before you start the hunt.
The most recent 1-2 days of cost data are ESTIMATES, and they often revise down.
A good share of "our bill exploded" turns out to be unfinalized days.
Rule out the false alarm before you start the hunt.
September 11, 2026 at 12:57 PM
Before you panic about a cloud bill spike, check the date range.
The most recent 1-2 days of cost data are ESTIMATES, and they often revise down.
A good share of "our bill exploded" turns out to be unfinalized days.
Rule out the false alarm before you start the hunt.
The most recent 1-2 days of cost data are ESTIMATES, and they often revise down.
A good share of "our bill exploded" turns out to be unfinalized days.
Rule out the false alarm before you start the hunt.
Kubernetes is where cloud cost goes to hide.
You do not pay for pods. You pay for nodes.
The scheduler packs by what pods REQUEST, not what they use - so most clusters run at 30-40% real CPU while paying for 100% of the nodes.
That gap is the bill.
You do not pay for pods. You pay for nodes.
The scheduler packs by what pods REQUEST, not what they use - so most clusters run at 30-40% real CPU while paying for 100% of the nodes.
That gap is the bill.
September 11, 2026 at 12:57 PM
Kubernetes is where cloud cost goes to hide.
You do not pay for pods. You pay for nodes.
The scheduler packs by what pods REQUEST, not what they use - so most clusters run at 30-40% real CPU while paying for 100% of the nodes.
That gap is the bill.
You do not pay for pods. You pay for nodes.
The scheduler packs by what pods REQUEST, not what they use - so most clusters run at 30-40% real CPU while paying for 100% of the nodes.
That gap is the bill.
Azure Cost Management tells you what you SPENT.
It does not tell you what you WASTED - and that is not a flaw, it is not its job.
It will never surface an orphaned disk, an idle gateway or missing Hybrid Benefit.
Budgets and alerts there on day one. Then go looking.
It does not tell you what you WASTED - and that is not a flaw, it is not its job.
It will never surface an orphaned disk, an idle gateway or missing Hybrid Benefit.
Budgets and alerts there on day one. Then go looking.
September 11, 2026 at 12:56 PM
Azure Cost Management tells you what you SPENT.
It does not tell you what you WASTED - and that is not a flaw, it is not its job.
It will never surface an orphaned disk, an idle gateway or missing Hybrid Benefit.
Budgets and alerts there on day one. Then go looking.
It does not tell you what you WASTED - and that is not a flaw, it is not its job.
It will never surface an orphaned disk, an idle gateway or missing Hybrid Benefit.
Budgets and alerts there on day one. Then go looking.
"We stopped those VMs months ago."
Stopping a VM stops the compute bill. It does not stop the disk bill.
Every disk on every deallocated VM is still billing you at full rate, for capacity nobody has read since.
Deallocated is not deleted.
Stopping a VM stops the compute bill. It does not stop the disk bill.
Every disk on every deallocated VM is still billing you at full rate, for capacity nobody has read since.
Deallocated is not deleted.
September 11, 2026 at 12:56 PM
"We stopped those VMs months ago."
Stopping a VM stops the compute bill. It does not stop the disk bill.
Every disk on every deallocated VM is still billing you at full rate, for capacity nobody has read since.
Deallocated is not deleted.
Stopping a VM stops the compute bill. It does not stop the disk bill.
Every disk on every deallocated VM is still billing you at full rate, for capacity nobody has read since.
Deallocated is not deleted.
The AI pillar is where a CCoE's arbitration job gets sharpest, because the trade-offs are unfamiliar:
A cheaper model that fails more often can cost more overall.
Self-hosting shifts cost from marginal to fixed.
A stricter data policy may rule out the best-performing provider.
A cheaper model that fails more often can cost more overall.
Self-hosting shifts cost from marginal to fixed.
A stricter data policy may rule out the best-performing provider.
September 11, 2026 at 12:54 PM
The AI pillar is where a CCoE's arbitration job gets sharpest, because the trade-offs are unfamiliar:
A cheaper model that fails more often can cost more overall.
Self-hosting shifts cost from marginal to fixed.
A stricter data policy may rule out the best-performing provider.
A cheaper model that fails more often can cost more overall.
Self-hosting shifts cost from marginal to fixed.
A stricter data policy may rule out the best-performing provider.
Start a new CCoE with cost. Not because it matters most - because it has the least ambiguous scoreboard.
Nobody argues about whether the bill went down.
Security and reliability wins are real and hard to prove. Cost wins buy you the credibility to go after them.
Nobody argues about whether the bill went down.
Security and reliability wins are real and hard to prove. Cost wins buy you the credibility to go after them.
September 11, 2026 at 12:54 PM
Start a new CCoE with cost. Not because it matters most - because it has the least ambiguous scoreboard.
Nobody argues about whether the bill went down.
Security and reliability wins are real and hard to prove. Cost wins buy you the credibility to go after them.
Nobody argues about whether the bill went down.
Security and reliability wins are real and hard to prove. Cost wins buy you the credibility to go after them.
FinOps vs CCoE, since they get conflated:
FinOps owns one pillar in depth - cost, and the business value of spend.
A CCoE owns the operating model, and is where cost trades off against reliability, security and speed.
Small org: same people. Large org: FinOps sits inside it.
FinOps owns one pillar in depth - cost, and the business value of spend.
A CCoE owns the operating model, and is where cost trades off against reliability, security and speed.
Small org: same people. Large org: FinOps sits inside it.
September 11, 2026 at 12:53 PM
FinOps vs CCoE, since they get conflated:
FinOps owns one pillar in depth - cost, and the business value of spend.
A CCoE owns the operating model, and is where cost trades off against reliability, security and speed.
Small org: same people. Large org: FinOps sits inside it.
FinOps owns one pillar in depth - cost, and the business value of spend.
A CCoE owns the operating model, and is where cost trades off against reliability, security and speed.
Small org: same people. Large org: FinOps sits inside it.
The real test of cloud maturity isn't whether you can scale up.
It's whether scaling something DOWN is routine rather than exceptional.
Most orgs have a well-worn path for growing a resource and no path at all for shrinking one.
It's whether scaling something DOWN is routine rather than exceptional.
Most orgs have a well-worn path for growing a resource and no path at all for shrinking one.
September 11, 2026 at 12:53 PM
The real test of cloud maturity isn't whether you can scale up.
It's whether scaling something DOWN is routine rather than exceptional.
Most orgs have a well-worn path for growing a resource and no path at all for shrinking one.
It's whether scaling something DOWN is routine rather than exceptional.
Most orgs have a well-worn path for growing a resource and no path at all for shrinking one.
Performance efficiency and cost look like the same pillar. They aren't.
Performance asks: are resources matched to demand?
Cost asks: are we paying the best rate for what we use?
A workload can be perfectly sized and still overpriced, because nobody bought a commitment.
Performance asks: are resources matched to demand?
Cost asks: are we paying the best rate for what we use?
A workload can be perfectly sized and still overpriced, because nobody bought a commitment.
September 11, 2026 at 12:53 PM
Performance efficiency and cost look like the same pillar. They aren't.
Performance asks: are resources matched to demand?
Cost asks: are we paying the best rate for what we use?
A workload can be perfectly sized and still overpriced, because nobody bought a commitment.
Performance asks: are resources matched to demand?
Cost asks: are we paying the best rate for what we use?
A workload can be perfectly sized and still overpriced, because nobody bought a commitment.
Ask five teams which tier their service is.
All five will say tier one.
That's why workload tiering can't be self-assessed. Without someone owning the classification, redundancy gets applied uniformly and expensively, or inconsistently and dangerously.
Usually both.
All five will say tier one.
That's why workload tiering can't be self-assessed. Without someone owning the classification, redundancy gets applied uniformly and expensively, or inconsistently and dangerously.
Usually both.
September 11, 2026 at 12:53 PM
Ask five teams which tier their service is.
All five will say tier one.
That's why workload tiering can't be self-assessed. Without someone owning the classification, redundancy gets applied uniformly and expensively, or inconsistently and dangerously.
Usually both.
All five will say tier one.
That's why workload tiering can't be self-assessed. Without someone owning the classification, redundancy gets applied uniformly and expensively, or inconsistently and dangerously.
Usually both.
Two ways a CCoE fails:
Publish standards without paving the road -> documents nobody reads.
Become an approval gate -> a queue teams route around.
The working version makes the compliant path the easiest path. A landing zone nobody uses is a project, not an operating model.
Publish standards without paving the road -> documents nobody reads.
Become an approval gate -> a queue teams route around.
The working version makes the compliant path the easiest path. A landing zone nobody uses is a project, not an operating model.
September 11, 2026 at 12:53 PM
Two ways a CCoE fails:
Publish standards without paving the road -> documents nobody reads.
Become an approval gate -> a queue teams route around.
The working version makes the compliant path the easiest path. A landing zone nobody uses is a project, not an operating model.
Publish standards without paving the road -> documents nobody reads.
Become an approval gate -> a queue teams route around.
The working version makes the compliant path the easiest path. A landing zone nobody uses is a project, not an operating model.