Latest / The Cloud Business Podcast with Fexingo: AWS, Azure, GCP, and Enterprise Infrastructure / Why Cloud Contracts Now Include Carbon Credit Guarantees
Transcript
- Lucas: If these conversations are useful for what you're building or running, stick with me through the episode. We're going to talk about something that is quietly reshaping how enterprise cloud contracts are priced — carbon credit guarantees. Luna: Carbon credits in cloud contracts — we've touched on carbon penalties and carbon-aware scheduling in earlier episodes, but this is different, right? Lucas: It is. In the last six months, I've seen a new clause pop up in at least a dozen large enterprise agreements across AWS, Azure, and GCP. It's a guarantee from the cloud provider that they will purchase and retire a specific volume of verified carbon credits on behalf of the customer, tied directly to the compute or storage the customer commits to. Luna: So not just offsetting the provider's own operations, but actually buying credits linked to the customer's workload? Lucas: Exactly. The typical structure looks like this: a customer signs a three-year reserved-instance or savings-plan commitment for, say, ten million dollars in annual spend. The cloud provider includes a rider that says, 'For every dollar of compute, we will retire X kilograms of carbon credits from a registry like Verra or Gold Standard.' The customer gets a report each quarter showing the serial numbers of the retired credits. Luna: That's a pretty specific commitment. How are providers deciding the rate? Is it per dollar, per core-hour, per gigabyte? Lucas: It varies. Azure has been using a per core hour model for its 'Carbon Aware Compute' tier — they guarantee 0.2 kilograms of carbon credit retired per virtual CPU hour for certain instance families. AWS is more often pricing it as a percentage of the total contract value, like 1 to 3 percent of the monthly spend goes to credit purchases. GCP has a more flexible approach where the customer can select the registry and the project type — reforestation, direct air capture, methane capture — and the credit cost is folded into the unit price. Luna: That must create a lot of negotiation surface area for procurement teams. I imagine the biggest question is: are these credits actually additional, or are providers just buying cheap offsets and calling it a day? Lucas: That's the billion-dollar question. The contracts I've reviewed all require the credits to be certified by Verra or Gold Standard, and they specify that the credits must be 'vintage' within the same year as the compute consumption. So no buying old forestry credits from 2015. But additionality — the question of whether the credit would have existed anyway — is harder to guarantee in a contract clause. Some sophisticated buyers are now requiring that the credits come from projects that are less than three years old and that the provider disclose the project ID and the validation body. Luna: So the contract becomes a tool for ensuring quality, even if the carbon market itself is still maturing. What about pricing? Are providers eating the cost, or are they passing it through? Lucas: Mostly pass-through, but with a twist. The cloud provider acts as an aggregator — they buy credits in bulk from project developers, so they get a lower price than a customer could individually. Then they add a small markup, typically 5 to 10 percent, and bundle it into the reserved-instance price. The customer sees a line item like 'Carbon Credit Fee' on their invoice. But I've seen cases where, for very large commitments — say over fifty million dollars — the provider actually discounts the compute by the cost of the credits, effectively making it neutral. Luna: Interesting. So carbon credits can become a negotiation chip. 'If you give me the credits at cost, I'll commit to more compute.' Lucas: Exactly. I worked with a financial services firm that was negotiating a fifteen million dollar annual Azure commitment. They asked for a 15 percent discount on the carbon credit rider. Microsoft agreed, but only if the firm extended the commitment from three years to five. So the credits effectively became a way to lock in longer terms. The firm got a lower carbon cost, Microsoft got a longer revenue lock. Luna: That's a classic cloud contract negotiation — just with a sustainability wrapper. But I can see CFOs and sustainability officers having different priorities. The CFO wants the discount, the sustainability officer wants real impact. Lucas: And that tension is playing out in contract reviews. One procurement leader at a retail company told me their sustainability team rejected a carbon credit clause because the credits came from a wind farm in a country where the project would have happened anyway — they wanted direct air capture credits, which are more expensive. The clause ended up being renegotiated with a specific project list and a maximum price per tonne. Luna: So the contract becomes a tool for directing capital to specific climate solutions. That feels different from the usual cloud contract, which is purely about compute and storage. Lucas: It's a shift. And it's being driven partly by Scope 3 reporting requirements. Under the SEC's climate disclosure rules and similar regulations in Europe and California, companies have to report the carbon footprint of their purchased goods and services — which includes cloud computing. If the cloud provider is retiring credits on your behalf, you can count that as an offset in your Scope 3 inventory. That's a direct compliance benefit. Luna: Right, so the carbon credit guarantee becomes a way to de-risk regulatory exposure. But is there a risk that these credits get overcounted — that two different customers claim the same credit? Lucas: That's the double-counting problem, and it's a real concern. The contracts I've seen try to address it by requiring that credits be retired in a registry and that the retirement serial number be tied to the customer's account. But if the registry isn't transparent, or if the provider retires credits in a bulk pool and then allocates them to customers, it's possible for the same credit to be claimed by multiple buyers. That's why some large enterprises are now insisting on a provision that gives them the right to audit the provider's credit retirement records. Luna: So the contract is evolving to include audit rights. That's a significant escalation from a standard service agreement. Lucas: Definitely. And there's another layer: some providers are now offering carbon credit futures as part of the contract. So instead of buying credits for current compute, you can pre-purchase credits for compute you plan to use in three years, at a fixed price. That helps the customer lock in costs if they expect carbon credit prices to rise. Luna: Carbon credit futures in a cloud contract — that's a financial instrument embedded in an infrastructure deal. It's like the contract is becoming a mini carbon market. Lucas: Exactly. And it's not just the big three. I've seen similar clauses from IBM Cloud and Oracle Cloud, though with less transparency on pricing. The trend is clear: carbon credits are becoming a standard line item in enterprise cloud agreements. Luna: Before we wrap up, I want to circle back to something you mentioned earlier about the quality of credits. You said some buyers are demanding specific project types. What's the premium for something like direct air capture versus forestry? Lucas: Direct air capture credits currently trade around two hundred to six hundred dollars per tonne, depending on the technology and the registry. Forestry credits are more like ten to thirty dollars per tonne. So if a customer insists on high-quality DAC credits, the carbon credit fee on their cloud contract could be ten to twenty times higher than if they accept forestry credits. That's a real cost consideration. Luna: That's a big range. So procurement teams need to understand both the carbon market and the cloud market to negotiate effectively. Lucas: Absolutely. And the providers know it. That's why they're offering tiered options — basic, premium, and what AWS calls 'Climate+', which uses a mix of reforestation and direct air capture. The customer can choose their level of ambition. Luna: We deliberately don't run ads on this show because we want these conversations to be as clear and unvarnished as possible. If you find that valuable and want to support that choice, the link is buy me a coffee dot com slash fexingo. Helps us keep digging into these contract details. Lucas: Yeah, it's a small way to keep the show independent and focused on what actually matters for operators and builders. And we really appreciate it. Luna: So let's look ahead — what's the next evolution? Do you see carbon credit guarantees becoming a standard clause in all cloud contracts, or will it remain a premium add-on? Lucas: I think within two years, most enterprise cloud contracts above a certain spend threshold — say five million dollars annually — will include some form of carbon credit guarantee. It's becoming table stakes for sustainability reporting. The differentiation will be in the quality, the auditability, and the pricing. And that's where the real negotiation will happen. Luna: So for anyone renewing a cloud contract in 2026, this is a clause to watch — and potentially to push for. Lucas: Exactly. Ask your provider: 'What's your carbon credit guarantee? What registry? What vintage? Can I audit?' Those questions are becoming as standard as asking about uptime SLAs.