kodebeat / themes / greenops

What does this software cost the grid?

Energy and carbon measured on real infrastructure, with the method published and the number made enforceable in CI.

The stack, layer by layer

Each layer answers a different question, and each tool is listed by what it does. Anything not publicly released is marked, because "I built it" and "you can go and read it" are different claims.

Measurement

Get a number before changing anything. Power at the node, emissions per workload, and the same figure attached to a pull request so it stops being an annual report and starts being a review comment.

carbon per build carbon-badge fails a PR over its carbon budget carbon-budget-action static linter for energy-wasteful code greenlint SCI to ISO/IEC 21031 sci-disclose grid intensity on a Pico W and e-ink co2-grid-meter

Placement and scheduling

The same job emits different amounts depending on where it runs, and the spread between regions is wider than most teams assume. These rank them on live grid intensity, from an auditable dataset.

ranks regions by live grid intensity carbon-region-picker the intensity data behind it carbon-intensity-api auditable region dataset cloud-carbon-scorecard

Distribution

Measurement that takes a week to install does not get installed. Terraform and Helm modules put the stack on a cluster in an afternoon, and an umbrella module wires them together.

the umbrella terraform-kubernetes-greenops power profiling terraform-helm-kepler container-level power terraform-helm-scaphandre emissions DaemonSet terraform-kubernetes-codecarbon cost alongside carbon terraform-helm-opencost event-driven autoscaling terraform-helm-keda hibernation and cleanup terraform-helm-kubegreen cloud carbon footprint terraform-helm-cloud-carbon-footprint intensity exporter terraform-helm-carbon-intensity-exporter the metrics stack under it terraform-helm-prometheus-stack

Writing and data

A method nobody can check is a marketing number. The book is free to read, the papers show the working, and the curated list points at everyone else doing this properly.

the field, curated awesome-greenops the course greenops-course in development

It is the deepest theme here: a full stack rather than a blog post, and the one specialism with a third party's name on it, Green Software Foundation Champion since 2025.

The papers

Every paper carries the methodology behind any number it emits, and what the tool deliberately does not do. Pick them up from the catalogue.

Making CI carbon visible, then enforceablecarbon-badge and carbon-budget-action
Acting on grid carbon intensity: the data and the placecarbon-intensity-api and carbon-region-picker
Linting for the energy a codebase wastesa static analyser for energy-wasteful patterns
Measuring Software Carbon Intensity to ISO/IEC 21031an SCI measurement CLI that prints every term of the formula
Shifting household load into cleaner hours, locallya local-first grid intensity meter with an e-paper display

GreenOps & GreenCoding

The long-form version: a practical roadmap to measuring energy and carbon on real infrastructure. Free to read online, no email needed.

Read the book

Why this matters commercially, if that is what you are here for: CSRD reporting needs emissions figures an auditor can question, and an estimate with a hidden method does not survive that. Everything above is open source and installs on your cluster, so the figures are yours to defend.

Working on this?

Tell me what you are looking at and I will tell you honestly whether any of this helps. No pitch attached, and the papers are free either way.

Send a request