Built by an engineer who ran out of patience with wasteful CI

Mature engineering teams track compute cost, deployment frequency, test coverage, incident response time. Those numbers exist because at some point someone decided they were worth measuring and built tooling to surface them. The metric came first, and the practice followed.

CI carbon has no equivalent. The compute runs, the energy is consumed, and nothing records it. Not because it can't be measured, but because nobody built the instrument. Which means most engineering teams right now are carrying a carbon liability they can't quantify, inside a business that will soon need to report it.

CSRD is already in force for large EU companies, with Scope 3 disclosure requirements covering third-party compute. California's SB-253 brings mandatory GHG reporting to companies with over $1 billion in US revenue. In financial services, pharmaceuticals, and manufacturing, enterprise procurement teams are already asking suppliers for Scope 3 breakdowns before contracts get signed. For a lot of organisations, the disclosure requirement isn't coming. It's here.

Engineering is the only function in most businesses that still doesn't have a carbon number. Finance has one. Facilities has one. Logistics has one. And yet engineering runs some of the most energy-intensive continuous compute in the organisation, with nothing attached to it in sustainability reporting.

That's what EmitCI fixes. We instrument CI pipelines across GitHub Actions, GitLab CI, CircleCI, Azure Pipelines, Bitbucket, and Jenkins with no workflow changes and no instrumentation overhead. QA teams can see which test suites are driving the most emissions. Engineering leads get anomaly alerts before problems compound. Finance and sustainability teams get a complete, audit-ready GHG inventory — Scope 1 (direct), Scope 2 (electricity), and Scope 3 (cloud, CI/CD, hardware, SaaS) — that they can put directly into a CSRD or SB 253 disclosure without a spreadsheet or a consultant.

The organisations that get visibility now will have auditable data ready when a regulator or a customer asks for it. The ones that don't will be trying to reconstruct that history under pressure, probably during an audit.