Open-source tool for measuring and reducing cloud emissions across AWS, Azure and Google Cloud.
- Pricing
- Free
- Category
- Sustainable Cloud
- Compliance
- Not stated
Use case
How procurement and sustainability teams should assess cloud emissions tooling, from provider reports to allocation by service.
Cloud emissions now appear in several reporting obligations at once: scope 2 for purchased electricity, scope 3 category 1 for services bought from providers, and customer or investor questionnaires that arrive with their own definitions. Hyperscaler carbon dashboards were built for annual disclosure, but the teams being asked to act are platform, procurement and finance teams that manage accounts, regions and service catalogues.
The data is fragmented by design. Providers publish monthly totals with a lag, sometimes only at billing-account level, using their own methodology for grid intensity, PUE and renewable procurement. Customers hold usage and cost data at much finer granularity but no direct measurement of provider facilities. Market-based instruments such as renewable energy credits change the reported scope 2 figure without changing the electricity actually consumed, and the GHG Protocol Scope 2 Guidance requires both location-based and market-based results to be visible.
Failures usually show up at reconciliation. Provider totals do not match the figure in the corporate inventory, the same megawatt-hour is counted twice, a methodology change is not restated, or a managed service is omitted because it is not a virtual machine. Dashboards that allocate everything neatly by tag often hide a large unallocated remainder.
Evaluate tooling on methodology disclosure, allocation rules, dual scope 2 reporting, period close and export. Ask for the raw calculation behind a single service line and check that it reconciles to the provider's own report for the same period.
Methodology and factor transparency
Ask whether the tool uses provider-specific factors or public grid averages, which PUE assumption it applies, which market instruments it counts, and whether the methodology is versioned by reporting year.
Allocation to accounts and products
Check allocation by account, tag, service and region, and whether totals reconcile to the provider invoice and usage data, with the unallocated remainder shown rather than spread silently.
Scope 2 dual reporting
Location-based and market-based scope 2 should be presented side by side under the GHG Protocol Scope 2 Guidance, with the contractual instruments listed so the difference between the two is explainable.
Period close and late data
Test a month-end close: can the tool lock a reporting period, handle provider data that arrives late, and record a restatement instead of changing past figures without notice?
Coverage of managed services
Confirm coverage beyond virtual machines, including storage, networking, managed databases and SaaS, and that estimated figures are flagged separately from metered ones.
Export and audit evidence
Request raw usage data, factors and calculation details in a machine-readable export, plus a snapshot of the methodology used, so an external reviewer can retrace the reported total.
Open-source tool for measuring and reducing cloud emissions across AWS, Azure and Google Cloud.
Power BI app showing Microsoft-reported carbon emissions attributable to an organisation's Azure usage.
AWS console service for viewing account-level carbon emissions and water withdrawals.
Open API for assessing the environmental impacts of servers, cloud instances and ICT equipment.
Last verified 2026-10-22. Figures on the linked tools are checked against the sources above; confirm pricing and compliance coverage before signing.