Written by 
Reviewed by This guide is for FinOps practitioners and sustainability leads who want to add carbon emissions data to existing FinOps practices and tie cloud spend to corporate sustainability goals. It covers how FinOps relates to GreenOps, what the FinOps Foundation's sustainability capability asks for, what good looks like at each maturity stage, and how to get carbon data into the tools you already use.
Key takeaways
- Sustainability is a FinOps capability, inside the Optimize Usage and Cost domain.
- Most usage optimisation cuts cost and carbon together. Commitment discounts and region choice are where they can pull apart.
- Carbon emissions belong in the same allocation, showback and forecasting views as cost, not in a separate report.
- Start with directionally correct data and document your method. Waiting for perfect data stalls the practice.
What is FinOps sustainability?
FinOps brings finance, engineering and business teams together to get the most value from cloud spend, guided by a shared set of FinOps principles. FinOps sustainability extends that to environmental impact. In the FinOps Foundation's words, it means "incorporating sustainability criteria and metrics into FinOps activities to ensure environmental efficiency is balanced with financial value".
In practice that means three things. First, measuring the carbon footprint of cloud computing, AI and other technology use, even where the sustainability data is incomplete. Second, putting that data into the same reports, allocation models and unit economics as cost, so engineers see both numbers at once. Third, using it to choose between optimisation options, including the cases where the cheapest choice is not the lowest-carbon one.
The capability also asks teams to consider water and other environmental impacts as data becomes available, not only greenhouse gas emissions.
FinOps vs GreenOps
FinOps and GreenOps work on the same cloud usage data. FinOps optimises it for cost and business value. GreenOps optimises it for environmental impact: energy, carbon and water. FinOps sustainability is where the two meet inside one practice.
| Compared on | FinOps | GreenOps |
|---|---|---|
| Main question | Are we getting value for our cloud spend? | What is the environmental impact of our cloud and AI use? |
| Core data | Billing and usage data (CUR, FOCUS) | The same usage data, enriched with energy, carbon and water |
| Typical owners | FinOps team, finance, engineering | Sustainability team, FinOps team, engineering |
| Outputs | Showback, chargeback, forecasts, savings | Emissions reporting, carbon showback, reduction targets |
Most enterprises do not need a separate GreenOps team. The FinOps team already owns the billing data, the allocation model and the relationships with engineering and cloud operations, so it is usually the quickest route to acting on carbon. The sustainability team brings the reporting rules and targets.
"Technology teams are being told to scale cloud and AI at the pace needed to stay competitive, but also to control costs, meet sustainability targets and build carefully. The question is how. Putting carbon next to cost, in the tools FinOps teams already use, is the most practical answer we've seen."
The FinOps Foundation sustainability capability
FinOps work is grouped into domains and capabilities. Sustainability is a capability in the Optimize Usage and Cost domain, and its data is meant to feed other capabilities too, such as allocation, forecasting and unit economics.
The capability sets out two areas of work:
- Understanding sustainability impact: Measure the carbon footprint of technology across cloud, data centres, SaaS, AI and end-user computing. Treat usage efficiency as the main lever for both cost and carbon. Surface the trade-offs where the two goals conflict.
- Governing and reporting sustainability: Put carbon data into cost allocation, forecasting and unit economics. Work with sustainability, procurement and finance teams. Document assumptions, methods and data limits.
It is direct about data quality: the primary goal is "to use whatever data is available, even when it is incomplete" to make recommendations, while documenting how the numbers were produced. It also calls out AI workloads, which run on energy-intensive GPU clusters, as needing specific attention.
Sustainability at each FinOps maturity stage
The FinOps maturity model has three stages: Crawl, Walk and Run. The sustainability capability describes each stage. The first column summarises it; the second is our view of what the data needs to do:
| Compared on | What it looks like | What the data needs to do |
|---|---|---|
| Crawl | Teams know cloud use creates greenhouse gas emissions. Impact is reported after deployment, often by hand. Optimisation is mostly turning off what is not used. | Give a credible baseline that sits next to cost, so leadership and engineers trust it. |
| Walk | Carbon data is shared with engineering and product teams. Work moves to re-architecting and refactoring workloads. Carbon starts to enter allocation and chargeback. | Be granular enough to allocate to products, teams and services, at the same level as the bill. |
| Run | Sustainability is part of every build, migration and optimisation decision. Carbon is fully in allocation, chargeback and unit economics, with targets and executive reporting. | Be consistent across cloud providers, auditable, and detailed enough (by region and hour) to plan where and when workloads run. |
The step from Crawl to Walk is where many teams stall. Provider carbon dashboards can give a baseline, but they are hard to allocate to products and hard to join to FinOps tooling, so carbon stays in a separate report instead of shaping decisions.
Carbon showback and chargeback
Carbon showback means reporting each team's or product's share of cloud emissions alongside its share of cost. Carbon chargeback goes a step further and makes teams accountable for it, for example by setting carbon budgets per product or including carbon in internal pricing.
Both depend on the same thing as cost allocation: emissions data at the grain of the bill, carrying the same tags, accounts and business labels. If carbon arrives only as a monthly total per cloud account, it cannot be split by product, and teams cannot see what their own decisions changed.
The FinOps Foundation notes that carbon allocation is "inherently more nuanced than cost allocation". Shared services, idle capacity and embodied emissions from making the hardware all need a rule for how they are shared out. Treat it like any other carbon accounting choice: pick a rule, write it down and keep it stable from year to year, so the trend means something.
Adding cloud sustainability data to your FinOps tool
Most enterprise FinOps teams already have a cost platform or a BI environment they trust. Adding cloud sustainability data there is usually quicker than adopting a separate sustainability tool, because the allocation rules, dashboards and review routines already exist.
There are three common routes:
- Provider dashboards: The big public cloud providers, AWS, Azure and Google Cloud, each offer a carbon view of their cloud services. They are free and a reasonable first look, but each uses its own method and level of detail, so multi-cloud totals do not compare well.
- Spend-based estimates: Multiply spend by an emission factor per euro or dollar. Quick, but the figure follows price: a discount lowers the estimate even when energy use is unchanged.
- Usage-based data joined to the bill: Energy, carbon and water estimated for each line of usage, then loaded into the FinOps tool next to cost.
Greenpixie takes the third route. GPX Cloud enriches AWS, Azure and Google Cloud billing data (CUR or FOCUS) line by line, and the data can be loaded into the FinOps platform you already use, such as Flexera, Apptio or CloudHealth, as well as many others and your own BI tools.
Where cost and carbon line up, and where they don't
Most usage optimisation cuts both. Rightsizing oversized resources, deleting unattached storage or switching off idle environments lowers the bill and the energy behind it. Cutting cloud waste is where cost savings and cloud efficiency come together. The FinOps Foundation's capability makes the same point: using only what is needed, only when it is needed, is the main lever for both. Our guide to cloud cost optimisation goes through each tactic and what it does to carbon.
The two pull apart in a few places:
- Commitment discounts: A reserved instance or savings plan lowers cost without lowering energy, and can discourage teams from scaling the committed resources down.
- Region choice: Price, grid carbon and water stress are set by different things. In Greenpixie's Region Scorecard, AWS eu-north-1 (Sweden) scores A+ for carbon, has low water stress and sits in the cheapest price band, so cost and carbon line up. eu-central-2 (Switzerland) also scores A+, but sits in the most expensive band. eu-south-2 (Spain) is mid-priced and scores A for carbon, but faces extreme water stress.
- Latency and resilience: Running close to users or keeping spare headroom in your infrastructure can be the right call for the business, even when it costs carbon.
| Compared on | Carbon score | Water stress | Price band |
|---|---|---|---|
| eu-north-1 (Sweden) | A+ | Low | $ (cheapest) |
| eu-central-2 (Switzerland) | A+ | Low | $$$$ (most expensive) |
| eu-south-2 (Spain) | A | Extreme | $$ |
The gaps are large: the same m5.12xlarge instance running all year produces about 620 kg CO2e in Hong Kong (ap-east-1) and 284 kg in Spain, 54% less (Greenpixie data, November 2026). You can compare regions in the Greenpixie app.
These are the decisions where having both numbers side by side changes the outcome. At Mastercard, Greenpixie data enabled $2M in cloud cost reductions, and Mastercard exceeded its cloud carbon reduction target.
"Many still talk about cost and carbon as if they were two separate properties of technology. FinOps asks what an architecture will cost, and GreenOps asks what it will emit, but the engineer only made one architecture decision."
How to start
- Agree a baseline: your cloud carbon footprint for the last 12 months, by provider, account and region, with the method written down and in line with how your company reports GHG emissions.
- Put carbon next to cost in the dashboards your FinOps team already reviews.
- Add carbon to your existing optimisation recommendations, so each one shows its cost and carbon impact.
- Allocate carbon emissions to products and teams with the same tags as cost, and start carbon showback.
- Once the data is trusted, set targets per team that add up to your sustainability goals, and bring carbon into forecasts.
The data behind this is verifiable. Greenpixie's methodology has been independently verified in accordance with ISO 14064-3, prepared with reference to ISO 14064-1, and designed to be in line with the GHG Protocol Corporate Standard. If you also need the figure for CSRD or CDP, our guide to Scope 3 cloud emissions covers what each framework asks for.
Frequently asked questions
What is FinOps sustainability?
It is managing the environmental impact of cloud and technology use inside a FinOps practice: measuring carbon, energy and water, putting it next to cost, and using both in optimisation decisions.
What is GreenOps in FinOps?
GreenOps is the practice of reducing the environmental impact of cloud and AI use. Inside FinOps it shows up as the sustainability capability: the same usage data and teams, with carbon added to cost.
Is sustainability part of the FinOps Framework?
Yes. Sustainability is a capability in its Optimize Usage and Cost domain, with its own Crawl, Walk and Run descriptions and measures of success.
Does cutting cloud cost always cut carbon?
Usually, but not always. Removing waste cuts both. Commitment discounts cut cost without cutting energy, and the cheapest region is not always the one with the cleanest grid.
What is carbon showback?
Reporting each team's or product's share of cloud emissions alongside its share of cost, using the same tags and allocation rules.
Can I use my FinOps tool for carbon reporting?
Yes, if you can load emissions data at the same level of detail as your billing data. Usage-based carbon data that matches the bill line by line can sit in the same dashboards and allocation views as cost.
Explore GreenOps
Put carbon next to cost
See the energy, carbon and water behind your cloud bill
GPX Cloud adds them to every line of your AWS, Azure and Google Cloud billing data, ready for your FinOps tool.
