GreenOps is an organisational problem wearing a technical costume. The data was never really the hard part, and it is less of one every year.
Cloud providers keep improving the environmental reporting they offer their customers. That is good to see, but it still does not give you data you can act on to reduce the environmental impact of your cloud computing. Fortunately, a handful of commercial platforms now turn cloud usage into carbon, energy and water figures with real sophistication, GreenPixie, Tailpipe and Sopht among them, and we work with each of them. The same is possible today for free, using an open source project like SPRUCE, which we build and maintain. The old complaint that organisations simply cannot get the numbers they need is fading, and that is worth celebrating rather than treating as a problem still waiting to be solved.
SPRUCE earns its place in that landscape for two reasons. Its methodology is open, so anyone can look at how a figure was produced, question it, and compare it against other approaches, rather than trusting a result they cannot inspect. And it already has data and models covering most of what a typical organisation spends on cloud infrastructure, built on recognised open source datasets and projects. That combination makes it a credible starting point, not a placeholder to be replaced once the real budget arrives.
It also works from the same cost and usage data your FinOps teams already rely on. Environmental impact and spend end up side by side in one dataset rather than in two separate reporting streams, which is the first practical step towards treating them as one problem.
The hard part starts after you have the data
Here is the part of the story that gets less attention than it deserves. Turning that data into action, into decisions that actually reduce an organisation’s impact, is where most efforts stall, and almost nothing standing in the way is technical.
Once fine-grained numbers are available, the harder questions begin. Will they live in a new dashboard built for the purpose, or get folded into tools people already use every day? Who takes responsibility for leading and coordinating the work across teams that do not normally report to the same person? Is anyone bringing in the FinOps and finance people already reading the same bill every month? Can the effort find genuine support among the engineers who will need to change how they build and run systems, or will it stay confined to a slide deck? How do you get management to champion the work rather than simply sign it off? And how do you keep them engaged past the initial announcement, so the programme survives the next reorganisation or budget review?
None of this has a single right answer. What works for a small, close-knit engineering team looks nothing like what works for a large organisation with several business units, established governance, and a culture that moves carefully. The pattern has to fit the organisation, not the other way round.
One thing does generalise. Most actions that reduce environmental impact also cut the cloud bill, which is why GreenOps and FinOps belong in the same conversation. A programme that reports money saved alongside impact reduced has a far easier time surviving a budget review than one that reports environmental figures alone.
The groundwork is what makes a platform pay off
A commercial platform can take an organisation a long way: broader provider coverage, and integrations you would otherwise build and maintain yourself. Support is available either way, since we support SPRUCE ourselves, so there is someone to call when the numbers look wrong. What decides the return is the state of the organisation it lands in. Buying data and tooling is not the same as having teams who know what to do when the numbers arrive. Plenty of programmes deliver a fraction of the impact they could, and the limit shows up after the contract is signed, not before. What is missing is the organisational groundwork: who leads, who is engaged, how the output feeds real decisions. Do that work early, alongside or even ahead of any procurement process, and the platform arrives somewhere ready to act on it. The tool gives you data. What makes that data actionable is the culture you build and the ecosystem you develop around it.
A simple test for getting the most out of the spend
Before you commit significant budget, ask one question. Has the organisation already tried a free, open option such as SPRUCE, and started the organisational work described above? A yes puts the case for further investment on solid ground, and means whatever is bought lands somewhere that can already use it. A no is not a reason to hold off buying: it means the value of what you buy will be capped by something no licence can supply. The stakes are highest where the money being spent is public, but the test holds everywhere.
Where to start
The data side of GreenOps is not the obstacle it once was, and the organisational side is where most of the real work now lies. It will not sort itself out by waiting for a better tool or a bigger budget. Our technical grounding is what allowed us to build SPRUCE in the first place, and we work alongside commercial providers too, helping their customers get the most impact out of the data they already have. That work is as much about sustainability and finance as it is about engineering. If you are trying to work out where to begin, or how to get an initiative moving inside your own organisation, we would be glad to talk it through.