# Environmental Impact Environmental Impact data at Exoscale is available in two forms: - **Reports** - showing the impact of past usage (e.g. the monthly impact report) - **Estimations** - the impact of future use of a given resource (e.g. when choosing an Instance type) Both estimations and reports are calculated using the same Lifecycle Assessment (LCA) methodology, which is based on the [ADEME Product Category Recommendations](https://librairie.ademe.fr/economie-circulaire-et-dechets/6105-7697-product-category-rule-pcr-for-cloud-services-and-data-centre-it-hosting-services.html#/44-type_de_produit-format_electronique). You can read more in [Methodology](/platform/environmental-impact/methodology/). ## Impact Reports ### Console Access Reports on your organization's environmental impact can be accessed in the portal, under `Organization > Environmental Impact`. ![](report-page.png "Environmental Impact Report") These reports show the impact of the aggregated usage across all of your organization's resources. Impacts are estimated across a number of different *impact indicators*, such as Global Warming Potential (GWP), acidification, and eutrophication. You can read more about the impact indicators we use in the [ResilioDB documentation](https://db.resilio.tech/docs/what-is-lca). Reports are monthly, with the current month's report updated daily to reflect your month-to-date impact. ### API Access For programmatic access to impact report data, you can use the [`environmental-impact/report`](https://community.exoscale.com/reference/api/general/environmental-impact/#get-impact-report) endpoint, available to all customers. This endpoint returns the aggregated impact for your organization, broken down by zone and resource type. This endpoint is not limited to monthly data, and can be queried across an arbitrary date range. #### Parameters - `from` (required): the start date of the report (format `YYYY-MM-DD`) - `to` (optional): the end date of the report (format `YYYY-MM-DD`); defaults to today #### Impact Report JSON Structure The API returns aggregated impact data in the following format, with the top-level `impact` showing the total, and `zones` giving the breakdown by zone, and by product: ```json { "impact": { "ADPe": { "unit": "kg Sb eq", "value": 0.00017 }, "GWP": { "unit": "kg CO2 eq", "value": 2.2 }, // Plus remaining impact indicators }, "zones": { "ch-dk-2": { // Zone name "resources": { "compute": { // Top-level product, e.g. Compute "resources": { "instance": { // Product type, e.g. Instance "resources": { "cpu": { // Product category, e.g. Instance family "resources": { "mega": { // Product sub-category, e.g. Instance size "usage": { "unit": "hours", "value": 200 }, "impact": { "ADPe": { "unit": "kg Sb eq", "value": 0.0001 }, "GWP": { "unit": "kg CO2 eq", "value": 1.72 }, // Plus remaining impact indicators } }, // Plus other CPU Instance types } }, "standard": { "resources": { "medium": { "usage": { "unit": "hours", "value": 720 }, "impact": { "ADPe": { "unit": "kg Sb eq", "value": 0.000077 }, "GWP": { "unit": "kg CO2 eq", "value": 1.31 }, // Plus remaining impact indicators } }, // Plus other standard Instance types } } } } } } } } } } ``` #### CLI Usage ```bash exo api get-impact-report --from 2026-07-01 --to 2026-08-01 ``` Note that `--to` is optional and will default to today. The response will be in the same format as that shown for the API. ## Impact Estimations ### Console Access Impact estimations are shown in the console on certain product creation pages. These give you an indication of the impact these products will have when run for a certain period of time. For example, on the Instance creation page, you will see an estimated environmental impact per day when selecting the Instance type. ### API Access For programmatic access to impact estimations, you can use the [`environmental-impact/estimate`](https://community.exoscale.com/reference/api/general/environmental-impact/#get-impact-estimate) endpoint, available to all customers. The endpoint returns the estimated impact per unit of usage of the given product. For example, this would be for one hour of usage of a given Instance type. #### Parameters - `sku` (required): the SKU of the product or products you want to get impact for A SKU is a code that identifies a specific product or group of products available in the Exoscale product catalog. Some examples are: - `compute:ch-gva-2:instance:standard:medium` - a standard medium Instance in the `ch-gva-2` zone - `compute:ch-gva-2:instance:standard:*` - all standard family Instances in the `ch-gva-2` zone - `compute:*:instance:standard:*` - all standard family Instances in all zones #### Impact Estimate JSON Structure The API returns impact estimates in the following format, where `impact` holds a map of SKUs to maps of impact indicators. The SKUs included in the `impact` map will be those that matched the SKU passed in the request. ```json { "impact": { "compute:at-vie-1:instance:cpu:colossus": { "ADPe": { "unit": "kg Sb eq", "value": 9.539079791353054E-7 }, "GWP": { "unit": "kg CO2 eq", "value": 0.04487839483283493 }, // Plus remaining impact factors }, "compute:at-vie-1:instance:cpu:extra-large": { "ADPe": { "unit": "kg Sb eq", "value": 7.186477013504592E-8 }, "GWP": { "unit": "kg CO2 eq", "value": 0.04487839483283493 }, // Plus remaining impact factors } } } ``` #### CLI Usage ```bash exo api get-impact-estimate "sku: compute:ch-gva-2:instance:standard:medium" ``` The output format will be the same as that of the API.