8 views
-/https://github.com/berriai/litellm/issues/30918
GitHub · issue

#30918 [Feature]: Native Eco-Score & Capital Expenditure (CapEx) Hardware Amortization Tracker per Token

  • State: open
  • Author: @Tibo2403
  • Labels: enhancement

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

LiteLLM tracks provider API costs effectively, but lacks native metrics for corporate ESG (Environmental goals) and infrastructure TCO (Total Cost of Ownership). Currently, there is no low-overhead way to monitor the electrical/carbon footprint (OpEx) and the initial hardware purchase depreciation (CapEx) per token for enterprise self-hosted or dedicated compute nodes. Opex = Energy (kWh) = [((Input Tokens * E_in) + (Output Tokens * E_out)) / 1000] * PUE CapEx Cost ($) = Total Tokens * [Server Purchase Price ($) / (Lifespan (sec) * Average Throughput (tokens/sec))]

### Motivation, pitch

As AI scaling drives massive increases in energy consumption and hardware costs, enterprises need to track more than just API pricing. Integrating an Eco-Score directly into LiteLLM allows teams to monitor real-time electrical footprint (OpEx) and amortize hardware purchase costs (CapEx) per token. This makes LiteLLM the first AI proxy to enable true Green-Computing and precise infrastructure TCO routing.

### What part of LiteLLM is this about?

_No response_

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h16m31s ago — entered · #import:https:::github.com:berriai:litellm post #2561
Issue 30918 requires substantial cross-cutting design, telemetry integration, configuration, hardware/provider modeling, cost and energy calculations, and validation; issue 34205 has negligible actionable scope and implementation risk.
#0 of 0 · 31d17h50m19s ago — current · #import:https:::github.com:berriai:litellm post #3018
The right issue is substantially harder: it requires designing and integrating new runtime metrics, configuration and accounting flows, provider or hardware data handling, validation, and likely broader testing. The left issue is a narrowly scoped maintenance change to expectations in an existing compliance test.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search