The data centers going up across the region won't wait for the grid to get cleaner. A new data center needs reliable 24/7 power on day one, at the scale a hyperscale operation requires. Reliability comes before everything else. Clean energy matters, but it can't come at the cost of supply risk. That tension is the starting point for how SPARC fits into a data center power contract.
These facilities have a procurement problem that looks simple but isn't. They need very large volumes of reliable electricity. They need price certainty over a decade or more. And they need a credible story about clean power, both for internal targets and for the regulators and communities that increasingly scrutinize large new loads.
In most markets in the region, there are two practical options. The first is a standard grid connection: simple to execute, but passive. The data center consumes whatever the system delivers and has no meaningful influence over the generation mix behind its load. The second is a direct supply agreement with a generator or portfolio operator who can commit to reliability at scale.
A direct deal like this solves the reliability and commercial control problem. The data center gets a named counterparty, a defined supply obligation, and a pricing structure it can plan around. What a conventional PPA doesn't provide is a clear answer to the clean-power question. A large generator's portfolio is typically partly renewable and partly fossil-backed. That ratio isn't static, but a standard PPA doesn't create any formal structure for managing or evidencing how it changes.
This is where SPARC comes in.
A transition framework inside the contract
SPARC is a contractual and registry framework for turning a conventional power supply agreement into a transition contract. Rather than leaving the fossil-backed share of supply as an unmanaged background assumption, it gives that share a formal emissions position, registered in a dedicated system, with a defined pathway for reducing it over time as cleaner generation takes over.
The mechanism works through SPARC streams. A SPARC stream is a registered delivery band inside the supply agreement: a defined volume of power, delivered across a defined profile, carrying a specific embedded emission right expressed in tCO₂/MWh. When an eligible MWh is delivered under a registered stream and confirmed through metering, a SPARC is created. Where the delivery came from a renewable source, a REC or equivalent energy-attribute certificate evidences the renewable attribute linked to the SPARC record. Where the verified emissions of the delivered MWh fall below the embedded emission right, the difference is issued as an ARC: an Avoided Right to emit Carbon, designed to be registry-backed and potentially monetizable once recognized under the relevant host-country or market framework.
A registered basket of rights and obligations attached to a defined delivery band inside a supply agreement. It carries the right to supply power under the band, the right to receive the associated payment, and the embedded right to emit carbon, along with corresponding delivery and availability obligations. Individual SPARCs arise only from delivered and metered MWh. See the full mechanics.
The full mechanics are described in the mechanism section. The point here is the commercial structure.
How the deal might look
Take a 100 MW data center supply agreement between a hyperscaler and a large portfolio generator with a mix of gas and renewables in its fleet. At contract start, the generator can credibly commit to 15 percent renewable-backed delivery and 85 percent gas-backed. Rather than treating those as permanent background conditions, the parties define a SPARC transition schedule inside the agreement.
- Year one15 percent.
- Year three35 percent.
- Year five60 percent.
- Year eight80 percent.
Each target isn't a statement of intent. It's tied to registered SPARC streams, metered delivery data, and verified substitution.
As lower-emission generation fulfills what were previously gas-backed delivery bands, SPARC records the substitution, REC or equivalent evidence confirms the renewable attribute where applicable, and ARCs record the unused portion of the embedded emission right.
The power contract documents the reliability obligation. The SPARC records document that the renewable MWh fulfilled a registered delivery band that otherwise carried a gas-backed emission right. The REC or equivalent certificates document the renewable generation attribute. The ARCs document the unused emission rights. Each instrument says something distinct. None of them overstate what actually happened.
Where the clean capacity comes from
A generator holding this kind of contract has two paths for meeting the renewable targets inside the transition schedule, and SPARC accommodates both.
The first path is internal: the generator builds or contracts new solar, wind, or storage capacity and brings it into its portfolio to fulfill the registered streams itself. Many generators in the region already have renewable development pipelines. Under this path, SPARC gives the generator a mechanism for evidencing and crediting the transition as it happens, inside the supply agreement rather than through a separate reporting exercise.
The second path is to bring in an external renewable energy developer to fulfill specific SPARC streams. A solar-plus-storage developer could take on the delivery obligation for a defined band within the supply agreement, receiving the associated payment right while the generator retains its role as the primary counterparty to the data center. The external developer gets a bankable revenue stream tied to clean delivery. The data center gets renewable MWh evidenced under the same contractual framework as the rest of its supply.
In practice, a large long-term contract would likely involve some combination of both. The generator grows its own clean portfolio over time while also creating space for specialist developers to contribute to the more demanding parts of the trajectory.
Why not just negotiate this directly?
A sophisticated procurement team could write transition language into a bespoke bilateral contract without SPARC. The question is what they'd actually end up with.
Custom contract language is not an accredited instrument. Progress recorded through a private contractual note isn't independently verifiable, can't be compared across agreements, and doesn't produce a tradable asset. SPARC-issued ARCs are built on a consistent methodology that works whether the facility is grid-connected, on a private wire, or inside an industrial estate. The instruments, once the framework is recognized under the relevant host-country rules, can be used for domestic climate accounting, held as a transition record, or potentially monetized. A bespoke side letter cannot do any of that.
For generators, the same logic applies. SPARC doesn't just help them manage one data center contract. It gives them a product they can offer to any large industrial or commercial buyer who wants reliable power with a documented clean trajectory. The methodology travels.