Sustainability & software engineering: what every developer should know

Sustainability is no longer only the responsibility of industrial engineers, climate scientists, or corporate teams. Whether you are a software engineer looking to make your work more climate friendly, or you are helping clients calculate and report their CO₂ emissions to meet sustainability regulations, understanding the language of sustainability matters.

Companies are under growing pressure to follow sustainability rules like the CSRD or to report emissions using the GHG Protocol. That requires tools, often software based, that can measure, monitor, and display environmental impact. To do this well you need more than good coding skills. You need to understand the concepts behind the requirements. Terms like life cycle assessment, cradle to gate, and the GHG Protocol are not buzzwords. They are essential for building solutions that are accurate, compliant, and aligned with real sustainability requirements.

This guide walks through the key sustainability concepts and practices every software engineer should know to write smarter, more sustainable code and build tools that genuinely make an impact. It is the same foundation we rely on when we use in our sustainability accelerator.

Key sustainability concepts

Life cycle assessment (LCA)

Life cycle assessment, standardised under ISO 14040/44, is a structured method for evaluating the environmental impact of a product across all of its stages: raw material extraction, production, use, recycling, and disposal. It helps identify hotspots, the points where improvements or optimisations can reduce the overall footprint.

Cradle to gate

Cradle to gate is an LCA phase that evaluates a product's environmental impact within the boundaries of raw material extraction up to the point the product leaves the manufacturing facility. It excludes distribution, use, and end of life processes.

Cradle to grave

Cradle to grave is the full product life cycle. It expands cradle to gate to include distribution, use, and disposal or recycling.

Cradle to cradle

Cradle to cradle is a concept used in circular economy models. It is a regenerative approach that focuses on materials being reused indefinitely with no waste.

Key sustainability frameworks and regulations

Environmental, social, and governance (ESG)

ESG is a framework for evaluating a company's sustainability and ethical impact. Environmental covers effects on the planet, such as emissions, energy use, and waste. Social addresses relationships with people, including labour practices, diversity, and community impact. Governance focuses on leadership, ethics, transparency, and compliance.

ESG is used by investors, regulators, and stakeholders to assess long term risks, opportunities, and alignment with sustainability goals.

Corporate Sustainability Reporting Directive (CSRD)

The Corporate Sustainability Reporting Directive is an EU regulation that mandates companies to disclose their environmental, social, and governance performance with the same level of detail and reliability as financial data. The CSRD standardises what sustainability information is disclosed, covering topics like greenhouse gas emissions, resource use, social impact, and governance practices.

The CSRD applies to roughly 50,000 EU companies. Its goal is to improve transparency, comparability, and accountability so investors, regulators, and the public can assess a company's true sustainability performance and risks. Building software that produces audit ready CSRD data is exactly the kind of work we do on our data engineering and sustainability accelerator engagements.

GHG Protocol (Greenhouse Gas Protocol)

The GHG Protocol is a globally recognised standard for measuring and managing greenhouse gas emissions. It defines three categories:

• Scope 1: direct emissions from owned or controlled sources

• Scope 2: indirect emissions from purchased energy

• Scope 3: all other indirect emissions across the value chain, such as supply chains, travel, and product use

For software engineers, Scope 3 is especially relevant, since cloud usage, purchased hardware, and digital services all fall under it.

Task Force on Climate-related Financial Disclosures (TCFD)

The Task Force on Climate-related Financial Disclosures, created by the Financial Stability Board in 2015, developed a global framework for companies to disclose climate related risks and opportunities across governance, strategy, risk management, and metrics and targets.

By 2023 its recommendations had been widely adopted and integrated into regulations and standards worldwide. After its final status report, the TCFD was disbanded, and responsibility for advancing and monitoring its framework transferred to the International Sustainability Standards Board (ISSB), whose IFRS S2 standard builds directly on TCFD principles.

Sustainable software engineering practices

Understanding the frameworks is half the picture. The other half is writing code and designing systems that actually reduce emissions. These are practical green coding habits any engineer can apply.

Optimise network usage

Reduce data transfer by using delta updates (sending only changes instead of full datasets), applying compression like GZIP or Brotli, and replacing frequent polling with event driven models such as webhooks.

Fact box: Transferring 1 GB of data over the internet can emit between 3 g and 7 g of CO₂e depending on network type. A single inefficient API design at scale can cost hundreds of kilograms of CO₂e per year.

Be conscious of cloud usage

Use autoscaling or serverless compute to avoid idle resources, schedule automatic shutdowns for non production environments, and choose cloud regions powered by renewable energy when possible. Designing efficient, right sized infrastructure is a core part of our cloud development work.

Fact box: Idle cloud VMs can consume up to 60% of their peak energy. Choosing a renewable energy data center region can cut compute emissions by 50 to 90%.

Use AI consciously

Querying large AI models consumes significant compute resources and generates CO₂ emissions due to energy intensive data centers. Limit unnecessary queries, use smaller models or cached results where possible, and design efficient prompts to reduce retries.

Fact box: Training GPT-3 emitted roughly 500 tons of CO₂e, about five cars' lifetime emissions. Each query may emit 0.5 g to 4 g of CO₂e, depending on model size and complexity.

Improve data storage efficiency

Archive or delete stale data, avoid unnecessary duplication, and store large datasets in efficient formats like Parquet instead of CSV.

Fact box: Storing 1 TB of cloud data for a year can emit 3 to 10 kg of CO₂e depending on storage tier. Cold storage can be 90% less energy intensive than hot storage.

Practice email and notification hygiene

Batch notifications into digests, send only necessary alerts, and let users opt out or customise preferences to reduce unnecessary processing.

Fact box: Sending one standard email emits roughly 4 g of CO₂e; an email with large attachments can reach 50 g or more. Cutting unnecessary notifications for 10,000 users can save hundreds of kg of CO₂e annually.

Build sustainable coding habits

Profile code to eliminate inefficiencies, use lazy loading to avoid unnecessary resource use, and group operations like database inserts into batches to cut runtime and power usage.

Fact box: A 30% CPU efficiency gain on a high traffic service can reduce compute emissions by tens of tons of CO₂e per year. Inefficient loops or queries in production can add hours of extra CPU time daily.

Why this matters for the software you build

Sustainability requirements are moving from nice to have into law. The engineers who understand life cycle thinking, the GHG Protocol, and green coding practices are the ones who will build the compliant, efficient, trustworthy tools companies now need. Whether you are reducing the footprint of your own systems or building the platforms that measure someone else's, the language of sustainability is becoming part of the job.

At RUBICON we build the data platforms and applications behind real sustainability outcomes, from Scope 3 emissions tracking to CSRD ready reporting. Explore our sustainability accelerator to see how we turn these concepts into production software.

Frequently asked questions

What is sustainable software engineering?

Sustainable software engineering is the practice of designing, building, and running software in ways that reduce its environmental impact, especially energy use and carbon emissions. It combines green coding habits, efficient cloud architecture, and an understanding of sustainability frameworks like the GHG Protocol.

What is the difference between cradle to gate and cradle to grave?

Cradle to gate measures a product's environmental impact from raw material extraction up to the point it leaves the factory. Cradle to grave extends that boundary to include distribution, use, and end of life disposal or recycling, covering the full life cycle.

What is the GHG Protocol?

The GHG Protocol is the globally recognised standard for measuring and managing greenhouse gas emissions. It groups emissions into Scope 1 (direct), Scope 2 (purchased energy), and Scope 3 (all other value chain emissions).

Why is Scope 3 relevant to software engineers?

Scope 3 covers indirect emissions across the value chain, which includes cloud usage, purchased hardware, and digital services. Most of the emissions a software team is responsible for fall under Scope 3, which is why efficient cloud and code decisions matter.

What is the CSRD?

The Corporate Sustainability Reporting Directive is an EU regulation requiring around 50,000 companies to disclose ESG performance with the same rigour as financial data. It is a major driver of demand for accurate, audit ready sustainability software.