Architecture at a Glance

How Stardust fits together

In Stardust's design, subscriber clients (chat plugins, browser extensions, cloud and database agents) send usage and telemetry through one ingestion API to the Stardust core. There, it is scored for right-sizing, turned into ROI and return-on-impact figures, and recorded in a net impact ledger for carbon, electricity, water, heat and materials. On the other side, provider drivers connect verified carbon removal and restoration services through one standard interface, and MCP servers give read-only reporting and insights. A subscriber's own eco-positive actions, such as on-site renewables, heat reuse and water recycling, can also earn credit: the EAC Marketplace Plugin turns verified impact into claims listed on environmental attribute certificate (EAC) markets, and the credits and revenue flow back to the subscriber.

Stardust technical architecture. Top: subscriber-side clients (chat plugin for Claude, ChatGPT and Gemini; browser extension; cloud and infrastructure agent; database agent; and an EAC Marketplace Plugin, an OS plugin for eco-positive action claims and credits) send events to the Stardust Ingestion API (REST, gRPC, OTLP). The API feeds the middleware, big data and telemetry core: event queue and telemetry store, right-size and efficiency scoring, ROI and return-on-impact calculator, net impact ledger for carbon, electricity, water, heat and materials, and the remediation broker with registry and market connectors. MCP servers on the side provide subscriber reporting, provider insights and operator lifecycle access. Bottom: provider systems connect through direct air capture, point-source, nature-based and ocean-based drivers to a provider driver interface that sends verified telemetry up to the core. A subscriber credit path runs from the core's Net Impact Ledger to an EAC claim builder, which packages verified eco-positive actions like for like and never double-counted, and lists them with EAC marketplaces and registries (RECs, GOs, I-RECs, granular certificates, water benefit certificates, carbon and plastic credits); credits and revenue return to the subscriber's EAC plugin.
Stardust technical architecture: ingestion, middleware, MCP, provider drivers and EAC credits. The EAC credit path is a design concept, not yet in the Stardust specification. Open full size ↗ · Stardust on GitHub ↗
The Urgent Problem

No standard way to measure what AI fully consumes, and negatively impacts, with closed-loop reporting

AI's electricity demand is growing exponentially, creating problems and challenges we see every day. Yet no standard, shared way exists to measure what real and evolving AI workloads consume. Today's benchmarks measure peak hardware speed, not the energy real requests use on a real grid at a real time. Every provider reports differently, so buyers, regulators and researchers cannot compare claims or verify efficiency gains. Even organizations that know their footprint have no simple, standard path from measuring it to reducing it and addressing AI's disruptive concerns.

The Solution

An open, end-to-end AI sustainability operating system

AIforE is building “Stardust”, the codename for an open, end-to-end AI sustainability operating system. It makes the energy, cooling, water and emissions of AI software observable everywhere AI runs, from web browsers to AI and software applications to infrastructure. It then connects that measurement to action. It has four parts:

1

Stardust telemetry standard

An open schema, published as RFC 0001, for per-request AI energy, cooling, carbon and water accounting, collected by browser extensions, application plugins and infrastructure agents. It is built on OpenTelemetry and aligned with ISO/IEC 21031. It covers time-of-use, lifecycle emissions (operational, facility, training, embodied) and confidence tiers.

2

Open benchmark harness and leaderboards

In development: tools and a continuous pipeline that will measure energy per token and useful output per kWh across models, serving frameworks and hardware. All methods and raw results will be published.

3

AIforE Efficiency Control Plane

Planned: focused on “right-sizing” AI solutions to use only what is needed, for maximum ROI and reduced negative impact. It will track and recommend state-of-the-art reference architectures, including an open-source reference efficiency router that uses the most advanced techniques to select the right-sized models and architectures that meet the quality and service levels needed. It will make savings and quality trade-offs fully measured and observable.

4

Sustainability ecosystem connections

Links each AI user organization's measured emissions, water and energy consumption to verified services that can increase long-term sustainability, offset negative impacts and earn credit for sustainable actions such as sequestering carbon, recycling water, using zero-carbon energy and more. These AI sustainability service providers include nature-based solutions (afforestation and reforestation, habitat restoration, ecosystem improvement) and technological carbon removal, offered through the AIforE carbon marketplace.

Available Today

Every AI query has a price tag most people never see: tokens spent, dollars charged, and the electricity, water, and emissions emitted — behind the scenes. That footprint is invisible to most people generating it by using AI services, which means it's invisible to their decisions that could reduce it.

We've built and are improving codename Stardust, a free, open-source operating system and SDK that puts those numbers back in front of you. Today it runs as a browser extension alongside the AI chat apps people already use, including Claude, ChatGPT, and Gemini, and as software kits that developers add to their own AI applications. For teams running AI at scale, it plugs into the monitoring tools they already use through OpenTelemetry. Wherever a decision gets made, the same figures appear: tokens, cost, energy, water, and carbon, per prompt or per workload.

One glance gives you a compact score; one click shows the full breakdown in plain language. Every figure is labeled as measured or estimated, and our methods are published openly, so anyone can check our work and help improve it.

This is AIforE's ROI in practice: return on investment and return on impact. Stardust helps people and companies capture AI's real upside (productivity, speed, quality of life) while giving them what they need to right-size how they use it.

Provider-Service Plugin (Driver) Model

Seeing the footprint is step one. Restoring it is step two.

The browser extension and SDK are the subscriber side. The other side is the provider: any service that removes carbon or restores ecology. Like a printer driver, a provider implements one standard interface once and becomes available to every subscriber, with no custom integration on either side.

Providers are not limited to carbon. Carbon removal (reforestation, blue carbon, direct air capture, biochar) joins renewable energy generators, water restoration and recycling projects, heat recovery operators, and materials recyclers, all through the same interface. Each is matched to subscribers like for like, by the kind of impact it offsets, and every service has to be carbon negative or otherwise positive for Earth's ecology, in harmony with AI.

A data-center operator can be both: a subscriber consuming electricity and water, and a provider exporting waste heat, generating on-site solar, or recycling water. One SDK covers both roles, and a benefit sold to others is never also counted against the operator's own footprint.

The Core System

Connecting clients, providers, and the exchanges that make it work

At the center is Stardust Core. It measures a client's footprint across carbon, electricity, water, heat, and materials, matches it with the providers that can address each one, and connects to the exchanges and registries where credits for each are issued, traded, and retired. The value flowing through those markets, including recycling, helps offset the cost of sustainable operations.

Stardust never mints its own credits. Recognized programs verify and issue them; Stardust supplies the measurement data and retires credits in the client's name.

Exchanges & Registries

Five kinds of impact, five kinds of exchange

Carbon · mature

Carbon credits

Removal and avoidance credits from registries such as Verra, Gold Standard, ACR, and CAR, with Puro.earth for engineered removals.

Electricity · mature annually, emerging hourly

Renewable energy

Energy attribute certificates: RECs, EU Guarantees of Origin, and I-RECs, plus hourly granular certificates (EnergyTag) as they come online.

Water · emerging

Recycled and restored water

Water restoration certificates (BEF, one certificate per 1,000 gallons) and volumetric water benefit accounting, matched within the same or a stressed watershed.

Heat · emerging, varies by jurisdiction

Heat recovery

Waste heat delivered for reuse in district heating, greenhouses, or industry, measured with ISO/IEC 30134-6 and credited where white-certificate or carbon programs apply.

Materials · emerging

Recycling

Plastic credits (Verra) and e-waste recovery attested by certified recyclers (R2, e-Stewards). There is no mature e-waste credit market yet.

How It Stays Honest

Ground rules for every credit

Like for like. A water credit never cancels carbon, and a renewable energy certificate is an electricity claim, not a carbon offset.

One benefit, one claim. Each credit is retired once, for one beneficiary and one claim period.

Match in time and place. Electricity is matched within a market boundary and, where possible, by the hour; water within the same or a stressed watershed; heat to a named local recipient.

Show the confidence. Every provider carries a confidence tier, so a verified registry credit is never presented the same way as an unverified attestation.

This is built in the open as Project Stardust, and the measurement standard behind it is AIforE's contribution to the field: one open schema for the negative and positive impact of computing, mapped to existing standards rather than competing with them. Many registries don't yet offer open write APIs, so early connectors will retire credits through an account holder and move to automation as registries support it.

Support This Project

What your gift funds

Finishing the core plug-in and shipping it free and open source, so any developer or company can build on it.

Portability work across Chrome, Edge, Safari, and Firefox, and integration at the cloud/infrastructure level.

Keeping it free forever for individual users — sustainability tools shouldn't sit behind a paywall.

Every dollar here moves a working, open-source tool closer to release — one that puts sustainability data directly in the hands of the people using AI every day.

Tax Information

AIforE is a 501(c)(3) tax-exempt nonprofit organization. EIN: 42-2272946. Donations are tax-deductible to the extent allowed by law.