A carbon-aware CI/CD agent that measures, compares, and reduces the carbon footprint of your pipelines. Built on the GitLab Duo Agent Platform with Anthropic. Three specialist agents. One MR comment. Zero excuses.
CI/CD pipelines run thousands of times per day. Developers have zero visibility into their environmental impact. GitLab has no native sustainability features — only docs pointing to Eco-CI, a third-party tool that passively measures energy without recommending alternatives. The EU's CSRD requires Scope 3 reporting. Cloud CI/CD is Scope 3.
Running the same pipeline in Stockholm vs Mumbai produces 88x different carbon emissions. But developers can't see this — runner region selection is invisible.
Every DevOps team will need this data for CSRD compliance. Today nobody provides it inside GitLab.
A GitLab Duo agent that measures, compares, and actively recommends lower-carbon runner regions on every merge request.
Not just measurement — actionable routing. Not a dashboard — native MR comments. Not a separate tool — built into the workflow.
Named specialist agents collaborate in a GitLab Duo custom flow (v1 YAML spec). Each has its own system prompt, toolset, and role. Triggers on pipeline success. Routes through Carbon Scout → Green Analyst → Green Reporter.
Summary above the fold. Details collapsible. Routing suggestion with specific savings. Methodology always transparent.
| Energy | ~0.0008 kWh |
| Carbon | ~0.4 gCO2e |
| Grid intensity | 443 gCO2/kWh (Virginia) |
| SCI | ~0.4 gCO2e/pipeline |
eu-north-1
(Stockholm, 8 gCO2/kWh) would reduce emissions by 98%.
At 50 pipelines/day, that's ~7 kgCO2e/year saved.
Annual lifecycle emissions (gCO2eq/kWh) from ENTSO-E, EIA eGRID, and IEA. The same code, same pipeline, same result — radically different carbon cost depending on where it runs.
Eco-CI is the only existing CI/CD sustainability tool. Here's why GreenPipe is fundamentally different.
| Feature | Eco-CI | GreenPipe |
|---|---|---|
| Architecture | YAML task in pipeline | Native Duo Agent — triggers automatically |
| Carbon data | Fixed 472 gCO2/kWh default | 21 regions with real grid data |
| Routing recommendations | None | Optimal region + savings % |
| SCI compliance | No | ISO/IEC 21031 |
| Cross-region comparison | No | 5 alternatives ranked |
| Output location | Pipeline artifact | MR comment |
| Setup | Edit .gitlab-ci.yml per project | One trigger config |
| Approach | Passive measurement | Active recommendation |
GreenPipe uses established methodologies from the green software engineering community. Every estimate is labeled as approximate, every source is cited, every calculation is reproducible.
Based on the Cloud Carbon Footprint methodology (Thoughtworks). Uses SPECpower-derived CPU power curves with 50% default utilization and provider-specific PUE values.
energy = (watts / 1000) × hours × PUE
Location-based grid emissions from ENTSO-E (Europe), EIA eGRID (US), and IEA (global). Annual lifecycle averages in gCO2eq/kWh. 21 regions across AWS, GCP, Azure.
Stockholm: 8 · Virginia: 443 · Mumbai: 708
Follows the Software Carbon Intensity specification (ISO/IEC 21031, Green Software Foundation). Offsets and RECs are excluded — only physical emission elimination counts.
SCI = (E × I) per pipeline
The EU's Corporate Sustainability Reporting Directive requires Scope 3 emissions reporting. Cloud CI/CD infrastructure is Scope 3. GreenPipe generates the per-pipeline and per-project carbon data that compliance teams need — directly from GitLab, without manual audits.
Platform teams managing runner fleets across regions can use GreenPipe's cross-region comparison to make data-driven decisions about runner placement. Route flexible workloads (tests, builds) to greener regions while keeping latency-sensitive jobs local.
Most developers have never seen the carbon cost of their pipeline. GreenPipe makes it visible on every MR — not as a guilt metric, but as actionable information. "Your tests could run 98% greener in Stockholm" is a concrete choice, not an abstract obligation.
Teams adopting the Green Software Foundation's SCI standard need tooling that computes SCI scores automatically. GreenPipe implements the ISO formula per pipeline and generates the data needed for SCI reporting without modifying existing CI/CD configuration.
Copy the .gitlab/duo/ directory into your project. The flow YAML and agent config are all you need. No dependencies, no build step.
Go to Automate → Triggers in your project. Create a trigger for pipeline succeeded events. Point it at the GreenPipe flow. Assign your service account.
That's it. Push a commit, let the pipeline run, and GreenPipe will comment on the merge request with a full carbon report including energy estimates, SCI score, and routing recommendations.