Cloud Sustainability Tools

Every large cloud provider now gives its customers a carbon report, and each one counts a little differently. They differ on whether electricity is counted by what the local grid emits (location-based) or after the provider's renewable energy purchases (market-based), on whether the emissions from manufacturing the hardware are included, and on how they share a data center between customers. The figures also arrive weeks after the month they describe. That is fine for a sustainability report and too late for an engineering decision.

The tools in this section work the other way round: they estimate before you deploy, with open coefficients you can read, so the same workload can be compared across providers and locations on one basis.

The largest single lever is location. The carbon intensity of the electricity grid varies by more than a hundred times between the cleanest and the dirtiest regions with published data, which no amount of tuning inside one region can match. After location come the levers FinOps already pulls: idle and oversized resources, storage kept in a hotter tier than it needs, and data moved further than it has to go. Those usually cut cost and carbon together, but not always. The cheapest region is sometimes one of the dirtiest, so every tool here shows both numbers side by side and lets you decide.

Each figure names its source. The coefficients page lists the watts per vCPU, the power usage effectiveness, the storage and network factors and the grid intensities behind every estimate, and the calculators that show no carbon number say why.