Test environments, forgotten VMs, orphaned volumes and pods from finished projects keep running because nobody owns them. They rarely show up in performance reviews, only on the bill.
The fix you can use today
List everything with sustained low CPU and network use (the Constitution uses under 10% CPU and under 5 MB/s network).
Tag every resource with an owner and an expiry date.
Delete, or schedule to stop out of hours, what nobody claims.
Tools that help
GreenCode Constitution skill (GreenCode researchers): open-source energy principles and a catalogue of 37 energy anti-patterns that an AI coding agent can follow to find and fix waste like this
Cloud Carbon Footprint: estimates the energy and emissions of AWS, Azure and Google Cloud usage from billing and usage data
Kepler: exports energy estimates per pod and container on Kubernetes, using eBPF and hardware counters
How GreenCode helps
GreenCode helps tackle this by mapping a running estate and the energy each service uses. It shows which services run hot and which barely run at all. More on this.
