Lightweight, pluggable carbon measurement that fits right into your IDE, CI pipeline, and cloud stack. Know your software's carbon footprint — without adding to it.
Five principles guide everything we build. If the tool itself becomes a carbon aggressor, it defeats the purpose.
Adds negligible overhead to builds, tests, and runtime. If you can't feel it, it's doing its job.
Works with your existing codebase, CI/CD pipelines, IDEs, and cloud platforms. Zero code changes required.
Scores, trends, and concrete suggestions you can act on today — not a 40-page report you'll never read.
Built on the GSF's SCI specification (ISO/IEC 21031:2024) and compatible with the Impact Framework ecosystem.
Community-driven, vendor-neutral, and transparent. Audit the code, contribute features, extend the plugins.
Get carbon scores while you code and as part of every pull request. Shift left on sustainability.
Carbonah is built around the Green Software Foundation's three pillars for reducing software carbon emissions.
Measures energy consumed per functional unit — per API call, per build, per test run. Understand exactly where your compute energy goes and find the hotspots worth optimizing.
Integrates real-time grid carbon intensity data to score when and where your workloads run. Shift compute to cleaner times and regions automatically.
Accounts for the embodied carbon of the infrastructure you're using. The greenest server is the one that's already been manufactured — Carbonah helps you use it wisely.
Carbonah computes the SCI score defined in ISO/IEC 21031:2024 — a standardized way to measure and compare the carbon efficiency of software systems.
E
Energy consumed by the software, measured in kWh
I
Carbon intensity of the electricity grid, in gCO₂/kWh
M
Embodied carbon share of the hardware being used
R
Your functional unit — per request, user, build, or minute
Carbonah fits into your workflow, not the other way around.
One command. Works with npm, pip, brew, or as a standalone binary. Under 5 MB.
Point Carbonah at your project and choose your functional unit. A single YAML file does it.
Run locally in your IDE or plug into CI. Get SCI scores on every build and pull request.
Follow actionable tips, track trends over time, and set carbon budgets for your team.
Join developers who care about the carbon footprint of the software they ship.