Software Carbon Footprint Monitoring
Measure software carbon emissions — including AI workloads — with Carbonara: your IT team delivers SCI-aligned answers with almost no extra effort, using established green software frameworks.
What you get
Gather data transparently
IT measures the software carbon footprint in the workflow they already run; you use SCI-aligned numbers to decide
Answers from your IT team
With Carbonara, carbon data comes from the editor and CI pipeline developers already use — so IT can measure software carbon emissions as part of normal delivery, not as a separate reporting programme.
Established frameworks
Answers rest on tools the green software community already trusts: the Green Software Foundation's Impact Framework, CodeCarbon, and the Green Metrics Tool — integrated through Carbonara, not reinvented.
SCI you can defend
Assessment based on Software Carbon Intensity (SCI) — ISO/IEC 21031 — a published, vendor-neutral methodology for the carbon intensity of software.
Carbon-aware hosting
Where region or timing is a real lever, shift workloads with carbon-aware computing — less energy-intensive hosting based on your measured footprint, not a generic checklist.
Built on, not instead of
Green software tools
Carbonara brings established frameworks into the IT workflow you already run
Lets IT measure software carbon emissions with almost no extra effort: sits in the editor and CI pipeline, applies established frameworks (Impact Framework, CodeCarbon, Green Metrics Tool, SCI), and turns day-to-day engineering into defensible emissions data.
The Green Software Foundation's open-source framework for modeling software environmental impacts — used as a foundation rather than reinvented.
An established open-source Python package for tracking carbon emissions of running code, widely used for AI carbon emissions and ML workloads.
Open-source measurement of energy and carbon impact of software — used alongside the tools above depending on what your stack needs.
Software Carbon Intensity (SCI)
ISO/IEC 21031 — a rate of carbon emissions for software, without building a measurement stack from scratch
Carbonara includes a Software Carbon Intensity (SCI) assessment aligned with ISO/IEC 21031, so the answers your IT team produces reflect a published methodology. SCI is a rate (emissions per functional unit), complementary to a total software carbon footprint — useful for engineering decisions, not a substitute for a GHG inventory.
The specification leaves real choices to the implementer — which software boundary to draw, which functional unit to scale by, and whether to use measured or modeled data — so a generic default rarely fits every organization well. We help you make those choices deliberately, so the resulting score is one you can defend and act on.
From baseline to ongoing signal
IT stays in their workflow; you get comparable SCI and footprint answers from established frameworks
-
Assess your stack
Measure your current software carbon footprint and AI workload emissions with the tools above — starting from data, not assumptions.
-
Define your SCI boundary
Choose the software boundary and functional unit that make your Software Carbon Intensity score meaningful for your actual systems.
-
Identify the real levers
Carbon-aware hosting, workload scheduling, and architecture affect emissions differently depending on your stack. Prioritize based on measured data.
-
Monitor over time
Once Carbonara is in the editor and CI pipeline, software carbon emissions data keeps coming with almost no extra effort from IT — an ongoing signal instead of a one-off project.
Analyse disclosed IT carbon emissions
With Open Sustainability Analyst — for what companies report, not only the software carbon footprint you can measure yourself
This service measures the software carbon footprint of your own stack — code, deployments, and compute. Open Sustainability Analyst (OSA) works at another level: it analyses what companies (suppliers, portfolio holdings, peers) have already disclosed about carbon emissions in sustainability reports.
Need to measure your own software carbon emissions? Stay on this page. Need to analyse how others report IT and carbon emissions? Use OSA. Many teams use both — for example, to compare a supplier's disclosed emissions with an independent technical assessment of systems you can measure directly.
Related reading
View all posts »More on software carbon footprint, green software, and the Carbonara project.
Research & Development Collaboration in Climate Science
Work with leading experts for innovative research collaborations in climate science.
ESG Consulting & Sustainability Roadmaps
A pragmatic sustainability roadmap: build the in-house data you need, fill gaps with curated sources, and use that intelligence to drive environmental, social, and governance decisions, including your business model.
ESG & AI: Revolutionizing Real Estate Investment
Discover how AI is shaping the future of ESG in real estate investments for a sustainable and profitable tomorrow.
Climate Risk Assessment Services
A pragmatic path from materiality analysis to a data foundation you control to custom vulnerability models for the assets that matter most.
Frequently asked questions
Did you build Impact Framework, CodeCarbon, or Green Metrics Tool?
No. These are established open-source projects maintained by their own communities (the Green Software Foundation, in the case of Impact Framework). We integrate them through Carbonara and help you apply them correctly.
What is Carbonara?
Our open-source tool for IT teams: it sits in the code editor and CI pipeline and applies established green software frameworks (Impact Framework, CodeCarbon, Green Metrics Tool, SCI) so you can measure software carbon emissions with almost no extra effort from engineering — not a separate measurement programme.
Will this create a lot of work for IT?
That is the point of Carbonara: carbon assessment lands in the workflow developers already use. Once set up, answers come from existing delivery pipelines using established frameworks, rather than from ad-hoc spreadsheets or a one-off consulting audit every year.
What is Software Carbon Intensity (SCI)?
SCI is the Green Software Foundation methodology — standardised as ISO/IEC 21031 — for calculating a rate of carbon emissions for a software system. It complements a total software carbon footprint: SCI drives efficiency decisions; a GHG inventory covers absolute totals for disclosure.
Can this cover AI carbon emissions?
Yes. AI training and inference are often the largest and least visible source of software-related emissions in a modern stack, and tools like CodeCarbon are widely used in the ML community for exactly this.
How is this different from OSA?
This measures your own software carbon footprint directly. Open Sustainability Analyst analyses how companies disclose carbon and IT-related emissions in sustainability reports. They answer different questions and work well together.
Can you help reduce emissions, not just measure them?
Measurement is the starting point. Where carbon-aware hosting, scheduling, or architecture changes would meaningfully reduce your measured footprint, we help you prioritize and implement those changes.
Tell us about your stack
We'll say honestly what we can measure today, and what would need custom work.