{
  "id": 21261573,
  "title": "Cloud costs were never a technology problem",
  "url": "https://urgent.news/2026/11/22/cloud-costs-were-never-a-technology-problem",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-22T18:32:24.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/vlad_z_16b6320e21f32bee0d/cloud-costs-were-never-a-technology-problem-1ecb"
  },
  "original_language": "en",
  "account": "Cloud costs are not a technical problem, but a human one. The technology behind cloud providers like AWS and GCP is well-designed, and the pricing is documented. Optimization tools and knowledge are readily available to the professionals. The issue lies in the gap between building new resources quickly and reviewing them thoroughly. There is often a disconnect between the person who provisions a resource and the one who reviews the bill. This results in engineers being excellent at their jobs, but lacking a system for maintaining visibility over their built infrastructure. The remedy is simple: know what you're running, its cost, its purpose, and review it regularly, fixing what doesn't make sense and documenting decisions deliberately. Teams that follow this practice consistently avoid crisis conversations, as they rarely find themselves scrambling to explain why infrastructure costs have tripled. Efficient infrastructure support allows teams to focus on building something worth the investment.",
  "summary": "I've been sharing what I see inside cloud accounts for months now Real accounts. Real numbers. Real messes and real fixes Here's what it all adds up to Cloud costs are not a technical problem The technology is fine. AWS and GCP are well-designed systems. The pricing is documented. The optimization tools exist. The knowledge is available The problem is human. It's the gap between the speed of…",
  "key_points": [
    "Cloud costs stem from human factors, not technical issues",
    "Disconnection between resource provisioners and bill reviewers leads to visibility gaps",
    "Regular review and documentation prevent cost crises"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}