Request a briefing

New researchMeasuring AI work in Malaysian data centres

More answers per megawatt
from your H100s

Croutons measures the energy and GPU memory behind every AI answer, finds the workloads that waste capacity, and proves each fix by replaying real prompts before it ships.

Demo data, made up: the output of croutons scan --demo. Your logs stay on your machine.

A chip serves more when less of its work is wasted.

Croutons reads telemetry from deployments running open models on your own accelerators

  • Llama
  • DeepSeek
  • Qwen
  • Mistral
  • Gemma
The Croutons mascot, a chrome robot cat, between open models and the accelerators that run them
  • H100
  • H200
  • B200
  • GB200
  • MI300X

Reads telemetry from deployments running these models and accelerators. Nothing sits in the request path.

Croutons finds the waste and proves the fix

Every token a model reads costs compute and holds GPU memory. At 128K tokens, that memory alone can outgrow the GPU (OSDI 2026).

Energy, memory and cost per answer

From the logs and telemetry you already have. Spend by model and workflow, and what the GPUs drew while they served it.

croutons scan ./logs --gpu dcgm.csv

Spend by workflow, and what the GPUs drew while they served it.

WorkflowCallsCostShare
research-agent1,066$72.3156%
contract-review280$24.5019%
ticket-triage2,800$22.2917%
support-chat1,820$10.868.4%

2 × H100 · 80 kWh used · 238 W average per GPU

Demo data, made up: the output of croutons scan --demo.

Losses multiply. The cheapest one to cut is at the bottom.

A token saved at the request also saves its share of every loss above it. At a PUE of 1.4, each watt a GPU spends on a token the answer never needed costs 1.4 watts at the meter.

Power from the grid

Power reaching the serversLost to cooling and power conversion · facility teams

Useful GPU workLost to idle and underused GPUs · schedulers and clouds

Answers deliveredLost to wasted tokens · Croutons

Widths are illustrative, not measured. PUE 1.4 as an example. Croutons, November 2026.
  • Facility tools stop at the rack.
  • GPU tools stop at the chip.
  • AI logs stop at the API call.
  • Croutons starts at the request, the one layer nobody else checks.

Beside your stack, not in it

Croutons reads; it does not sit in the request path.

Reads what you already export

Request logs, engine metrics, GPU telemetry and facility data. Gateway logs, OpenTelemetry spans, vLLM and DCGM metrics all work as they are.

How the scan works

Runs on your own machine

Nothing is installed in production and no prompts leave the site.

How data is handled

Proved on your traffic

Start with a scan of your own logs. It shows where your compute goes. Every fix after that is measured against it, for cost and for answer accuracy.

npm install -g @croutons/cli

Then run croutons scan ./logs, or croutons scan --demo to try it on a made-up week.

One command, on logs you already keep

JSON, JSON Lines and CSV. Your logs are never uploaded.

Read the docs
Teams paying for AI by the token
A smaller bill for the same answers.
Teams running their own GPUs
More users on the cluster you already own.
GPU clouds
More tenant work on the capacity you’ve built.
Public-sector AI
More from finite national compute.

An open method, on public data

How to verify AI work and measure output per allocated megawatt, with every source dated.

See all

Questions

Do you need access to our systems?

Not to start. The scan runs on your machine, on log samples you choose.

How much will it save?

That depends on your traffic, so we don’t quote a number up front. The scan gives you your own baseline first.

Does sending less hurt accuracy?

It can if it’s done carelessly. Accuracy is measured on the same questions as cost, and a change that loses accuracy doesn’t ship.

Is our data safe?

Samples are used only for the agreed work and kept only as long as needed. Personal information is never sold.

Before you buy another GPU, see what yours are doing.