Varcio Carbon reports what your cloud estate emitted as the cloud providers report it, by month, provider, service and region, with a GHG-ready export. An inventory-based estimate sits beside the reported figures, never inside them.
A sustainability report needs numbers that trace to a provider file and a stated method.
What AWS, Azure, Google Cloud or Oracle publish for your own usage, imported from the provider’s carbon export. Each figure keeps the file it came from and shows both GHG Protocol Scope 2 methods: location-based (the grid’s average) and market-based (after the provider’s renewable purchases).
An activity-based estimate over your inventory, useful now and for resources the provider does not break out. It is shown beside the reported figures and is never added to them.
A month with no reported data is shown as having none. Presenting it as zero would read as a clean month.
Provider carbon exports use different column names and change them between versions.
Varcio reads the provider’s carbon export and proposes a column mapping.
You confirm or correct the mapping before anything is stored, and the source file is retained for provenance.
Carbon-cost fusion attaches emissions to the waste you are already acting on.
Every waste opportunity detected for AWS and Google Cloud compute carries an estimated kg CO2e per month beside its dollar saving. A detector family also flags material spend that sits in a high-grid-intensity region when the same provider offers a materially lower-intensity one.
The scope is deliberately limited to AWS EC2 and Google Cloud Compute Engine instances, the resource types where instance type and region are both already in inventory.
Cite the reported figures, which come from the provider’s own carbon export, keep the file they came from and state the Scope 2 method. Estimated figures are labelled as estimates and are kept separate.
Reported emissions can be imported from AWS, Azure, Google Cloud and Oracle carbon exports. The inventory-based estimate attached to cost findings covers AWS EC2 and Google Cloud Compute Engine instances.
Location-based uses the average emissions of the grid where the usage ran. Market-based reflects the provider’s renewable energy purchases. Both are GHG Protocol Scope 2 methods and Varcio shows both.
Pro, Business and Enterprise.
Import your provider carbon exports and see reported and estimated figures side by side. Free trial, no credit card required.
