# Introduction | Embodied Emissions methodology
Source: https://greenpixie.com/docs/methodology/cloud-embodied-emissions/introduction

Purpose, audience, and context of the methodology.

This document describes Greenpixie's methodology for estimating the greenhouse gases released in manufacturing, transporting, and disposing of the hardware that delivers a public cloud workload, being the embodied emissions of that hardware. It is intended for customers, partners, procurement teams, auditors, regulators, and technically literate readers who require a clear understanding of how Greenpixie derives its cloud embodied emissions figures.

Emissions from public cloud are reported in a cloud user's Scope 3. The cloud providers do not report the embodied emissions of their hardware at the level of the service a customer buys. Organisations reporting under that scope need a figure that can be traced to the instance family, the components it is built from, and the period of use the figure covers.

This document covers the embodied emissions term of the cloud emissions calculation. That term comprises the cradle-to-gate manufacturing of every hardware component attributable to a unit of cloud usage, the transport of that hardware, its end-of-life processing, and an allowance for the data centre shell. It forms part of the [*Greenpixie Methodology for Cloud Emission Measurement*](/methodology/cloud), which defines the evaluation boundary, the electricity calculation, the facility overhead and grid carbon intensity treatment, and the water calculation. The operational electricity of the same hardware is covered by the companion [*Greenpixie Methodology for Cloud Compute Energy Measurement*](/methodology/cloud-compute). This methodology supports AWS, Azure, and Google Cloud.

The sections that follow describe the scope, inputs, calculation process, quality controls, governance, and outputs of this methodology.