Skip to content

Comment on Launch HN: Bend (YC S22) – Automatically measure your company's carbon footprint

Comments

If any of that spend is at a cloud provider, it's an opaque, highly variable blob. How do you plan to deal with that?

Ya good point — our approach is always spend-based, so the way we'd calculate cloud spend is your AWS / GCP bill * the AWS / Google carbon intensity (what we call a 'factor'). It is true that some data center regions use cleaner energy vs. others. We consider the spend-based approach, at a minimum, a good first pass. The greener the cloud you use, the lower the emissions. And then you can further optimize within your cloud provider.

Another note — most cloud emissions only factor in the energy footprint ('scope 2' in technical greenhouse gas inventory terms). We believe this significantly undercounts emissions, because it ignores the capital expenditure of building the facility, buying all the machines, etc. The great thing about the spend-based approach is all this overhead is factored in. (BTW, Google Cloud Platform just started to layer in some of this 'scope 3' operational overhead data, but I believe AWS still ignores it, significantly undercounting emissions).

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.