CloudCostChefs

About CloudCostChefs

CloudCostChefs is the weekly show that turns sky-high cloud bills into bite-size savings. In 10 fast minutes you’ll get no-fluff news, hand-tested optimization “recipes,” and automation hacks that keep workloads lean, fast, and budget-friendly—across AWS, Azure, GCP, OCI, and more. Hosted by cost-obsessed cloud engineers, each episode arms you with actionable tips you can run today plus the tools that make your CFO do a happy dance. Aprons on, cloud-cost warriors—let’s get cooking! Ranked #4 Top FinOps Podcast by MillionPodcasts.com

Publisher

CloudCostChefs

Category

technology

Language

en

Explicit

No

First episode

5 Jul 2025

Latest episode

14 Aug 2026

Latest episodes

35 episodes in the feed.

1. 

   14 Aug 2026

   EP20 - Everything Doubles: Google's Prepay Cutover, Gemini's Silent 2x, and the Price OpenAI Won't Publish

   Three AI vendors changed a price this week and every change was exactly 2.0x. Google's Gemini Flash models doubleon January 1, 2027 — published 32 times on the pricing page, mentioned zero times in the changelog. DeepSeek movesto peak/off-peak on Sunday, where even the "discount" tier is up to 6x today's price. OpenAI shipped a tier with nopublished rate at all. Plus: Google is force-migrating every Gemini API developer to prepay billing, where creditsexpire at twelve months and forfeited money never appears as spend. Episode 20. Tags: finops, cloud cost management, gemini api pricing, google ai studio prepay, gemini 3.7 flash, gemini 3.6flash, claude sonnet 5 pricing, anthropic price increase cancelled, openai ultrafast, gpt-5.6-sol fast mode,deepseek v4 pricing, peak off-peak pricing, cloud billing, cost forecasting, vertex ai pricing, api costoptimization, cloudcostchefs

2. 

   7 Aug 2026

   EP19 - The Exchange Window & The Speed Tax — Why Your Cost Tools Missed Both

   Four cost events in twelve days. Exactly one of them has a number you can diff. Microsoft's docs promised at least six months' notice before ending Azure reservation exchanges. That sentence was deleted 44 hours before the announcement that honoured it — and Microsoft cleared its own six-month clock by two days. No rate changed; an uncapped, penalty-free exit door closed, leaving a $50,000-capped one behind. DigitalOcean did raise a real price on August 1st — and shipped the before-and-after tables as PNGs with the alt text "image alt text". Cursor spent 23 hours and 14 minutes with no dollar column on its usage page, retroactively, and called it intentional before reversing. And Claude Opus 4.5, 4.6, 4.7, 4.8 and Opus 5 are all published at $5 in and $25 out. Five generations, one flat rate card. Add `speed: "fast"` and a beta header and the same model bills at $10 and $50 — and Anthropic's Usage API can group by that dimension while its Cost API cannot. We cover: what Azure actually changed and what it didn't; the 8-day documentation lead over the announcement feed; why AWS is the counterexample rather than a third offender; the real latency-premium band across four vendors (1.8x to 2.5x, not "everyone doubled"); why prompt caching doesn't shrink your blast radius; and the place where FOCUS 1.4 has a word for cheaper-and-slower and no word for dearer-and-faster. Plus an on-air correction to Episode 16 on DeepSeek's peak pricing.

3. 

   24 Jul 2026

   EP18 - The Broken Meter: AWS's $284 Billion Phantom, the Missing Kill Switch, and the Week the Frontier Price Card Died

   "Just got a budget alert that I owe $286,486,223.88 on a hobby aws account." On July 16–17, AWS's billing console showed customers phantom estimates — hundreds of millions on hobby accounts, $284 billion on an account that normally bills under a dollar a month. None of it was real: AWS's estimate subsystem broke, a rollback failed, and corrected data took over a day. But the damage was real anyway — one practitioner tore down his entire setup before learning his $233 million bill was fiction, AWS's own cost alarms reportedly fired on the fake data and were disabled platform-wide, and the incident re-exposed the decade-old gap underneath it all: there is still no hard spend cap on AWS. We inventory what a cap actually means on all three clouds — and why an auto-kill switch wired to a meter that can lie might be worse than no switch at all. Then: the week the frontier price card died. Claude Fable 5 went onto metered billing July 20 at $10/$50 — the priciest card on the frontier — and the market answered in days: Kimi K3 at a third of the sticker with open weights landing, router startups claiming Fable-level results at a third of the cost (we check those claims), and independent per-task numbers showing the 3.3x sticker gap is really 2.1x once token burn and a disclosed ~30% tokenizer inflation enter the math. Tokens are a broken unit. We price work in tasks instead — and end with the Monday playbook: own one meter, write the billing-incident runbook, cap what can be capped, and diarize the cliffs. This is FinOps for the AI era — for IT finance leads, CIOs, CFOs, and MSPs who need real answers before a phantom estimate or a perishable price card does the thinking for them. 🍲 Full show notes and the practitioner playbook: cloudcostchefs.com Topics: AWS billing incident 2026, AWS phantom bill, AWS estimated billing data, AWS spend cap, budget alerts, cloud billing circuit breaker, Claude Fable 5 pricing, Fable 5 metered billing, Kimi K3 open weights, AI cost per task, tokenizer costs, DeepSeek V4 pricing, LLM router proxy, FinOps, cloud cost optimization, FinOps podcast.

Reach and audience

Public platform figures. Ratings count people who left a rating, not total listeners.

Spotify

5.0 / 5

1 ratings