Each entry explains the waste, the billing model behind it, how to detect it and how to fix it.
66 inefficiencies
Microsoft FabricCER-0337
Microsoft Fabric capacity is billed based on the provisioned SKU tier (F2, F4, F8, F16, F64, etc.) on an hourly basis, regardless of whether workloads are actively consuming those resources. Each SKU tier provides a fixed pool of Capacity...
Azure Container RegistryCER-0329
Azure Container Registry charges a fixed daily fee based on the selected tier - Basic, Standard, or Premium - regardless of whether the registry is actively used. This means a registry with zero image pulls, zero pushes, and no active...
AWS MarketplaceCER-0316
When organizations purchase third-party software through AWS Marketplace using annual subscriptions, they typically receive meaningful discounts compared to hourly pay-as-you-go (PAYG) pricing. However, when these annual subscriptions...
Azure Logic AppsCER-0309
Azure Logic Apps can quietly accumulate costs even when no workflows are actively executing, but the mechanism differs significantly depending on the deployment model. In the Consumption (multitenant) plan, Logic Apps with polling triggers...
Azure DevOpsCER-0294
Licensed Azure DevOps users remain assigned after individuals leave the organization or stop using the platform. These inactive users continue to generate recurring per-user charges despite providing no ongoing value, leading to...
AWS MarketplaceCER-0297
Teams assume AWS Marketplace SaaS purchases will contribute toward EDP or PPA commitments, but the SaaS product is not eligible under AWS's "Deployed on AWS" standard. As of May 1, 2025, AWS Marketplace allows SaaS products regardless of...
GCP Cloud LoggingCER-0262
Many organizations retain all logs in Cloud Logging's standard storage, even when the data is rarely queried or required only for audit or compliance. Log bucket cost comes mainly from the per-GiB storage charge applied when logs are...
GCP Cloud LoggingCER-0253
Some GCP services and workloads generate INFO-level logs at very high frequencies - for example, load balancers logging every HTTP request or GKE nodes logging system health messages. While valuable for debugging, these logs can flood...
GCP Cloud LoggingCER-0245
Non-production environments frequently generate INFO-level logs that capture expected system behavior or routine API calls. While useful for troubleshooting in development, they rarely need to be retained. Allowing all INFO logs to be...
GCP Cloud LoggingCER-0241
Duplicate log storage occurs when multiple sinks capture the same log data - for example, organization-wide sinks exporting all logs to Cloud Storage and project-level sinks doing the same. This redundancy results in paying twice (or more)...
AWS ConfigCER-0228
Spot Instances are designed to be short-lived, with frequent interruptions and replacements. When AWS Config continuously records every lifecycle change for these instances, it produces a large number of CIRs. This drives costs...
AWS ConfigCER-0201
By default, AWS Config is enabled in continuous recording mode. While this may be justified for production workloads where detailed auditability is critical, it is rarely necessary in non-production environments. Frequent changes in...
Showing 12 of 66
