AI Meter – Local token usage with energy and water estimates
Tracks token burn and water cost locally when no one else measures impact.

Translates abstract AI compute costs into kettles boiled and hours streamed.
AI developers, sustainability researchers, and environmentally conscious creators
CodeCarbon · Cloud Carbon Footprint · Machine Learning Impact Calculator
I built this calculator because I noticed it's easy to know how much a LLM costs per token, but it's extremely difficult to know it's carbon footprint or power consumption. I created this as a reference based on some published papers and public information, and it helps to have a guide of the impact of photo and video generation using AI.
I also added another factor about Token utilization, it's something that becomes important as the newer models start to use "thinking" modes to reach a conclusion. There is information up to earlier this year, so it's not possible to see the efficiency of newer models like OpenAI Sol or Kimi K3.
All the calculator does is to provide estimations and translate them in ordinary figures so people can understand it. There is no login required or any other type of paywall.
About the models, it's easier to make estimates for Open Source models (of course) so there's more confidence on that data. For the closed ones, there are estimations based on public available data.
Please let me know if you have suggestions in how I can improve this calculator.
Tracks token burn and water cost locally when no one else measures impact.
CodeCarbon and Green Software Foundation tools already do this with more depth.
Notebook calculates water usage per token, but lacks interactive tooling.
You enter monthly meter readings and MeterLogs turns them into grouped yearly dashboards (electricity, water, gas, solar production/feed‑in) — a deliberately pragmatic, no-hardware play. The site leans on trust signals (GDPR, Made in Germany) and a tidy starter flow, but it'd win more converts with CSV import, easier mobile entry, or optional utility integrations.
Poetic installation, but 49 seconds of steam disappearing—no reproducible tool or insight.
Driver-level energy profiling + grid carbon intensity—fills a genuine gap most devtools ignore.