{ Software Carbon Intensity Web Calculator | Software Carbon Intensity (SCI)

The Software Carbon Intensity (SCI) specification is a standard developed by the Green Software Foundation to measure the carbon emissions from software applications. It provides a metric for assessing the environmental impact of software based on both operational and embodied emissions, helping developers make more sustainable choices.

Operational Emissions

Emissions from energy consumed during system use

Emissions generated by software during its active use. This may include energy consumed by servers, devices, and network operations or a portion of the system while running the software. Generally, it's up to the user to decide what is possible for them to measure and what is representative of the work being done.

×

Emissions related to the geographical location of hardware. Some regions have cleaner energy grids, affecting the overall carbon footprint.


0

Embodied Emissions

Emissions from production, transport, and disposal of hardware needed to run software

The cumulative carbon emissions resulting from the entire lifecycle of hardware associated with the software—including manufacturing, transport, maintenance, and disposal—are referred to as Life Cycle Assessment (LCA) values.

×

The total hours for which hardware resources are allocated or reserved for running the software, regardless of actual usage.

÷

The estimated number of years the hardware is expected to remain operational and effective before replacement. We assume that hardware is installed for about 5 years.

×

The quantity of hardware resources (such as CPU, memory, or storage) allocated for software use, regardless of actual consumption.

÷

The full capacity of hardware resources (e.g., CPU, memory, storage) accessible on the system for software operations, representing the maximum potential usage.


0

Software Carbon Intensity (SCI)

Operational Emissions + Embodied Emissions

This value normalizes the carbon emissions to understand the efficiency and environmental impact of the software per unit of its functional output.

0