№ 00Local AI spend meter · open source

Stop runaway AI spend. Locally.

Burnban reads supported agent logs on your machine, meters supported API traffic live, and enforces budgets before forwarding. No signup. No telemetry. No Burnban cloud in the request path.

Install in one command Read the source

macOS · Linux · Windows · MIT licensed · local SQLite ledger

Local burn index · todaylive decision

$14.06

of $40.00 daily budget · localhost:4141 · SQLite

Illustrative instrument · real dashboard belowThe allow-or-refuse decision runs on this machine

№ 01What ships today

Meters watch. Burnban acts.

Burnban puts supported agent usage and enforceable API limits in one local dashboard. Logs provide visibility. Traffic routed through Burnban can be blocked.

01 · READ

Price local agent usage

Read supported agent histories in place. See usage by model, agent, and time window without a proxy, account, or upload.

02 · ENFORCE

Meter and cap API traffic

Route supported provider-bound traffic through the local meter. Keep a ledger and enforce daily, weekly, monthly, and per-agent limits.

03 · ACT

Act on the result

Inspect spend, pull the local kill switch, export records, or reprice recorded usage against another supported model.

localhost:4141 · burnban dashboardlive

Real local Burnban dashboard showing burned today, budget headroom, request count, burn chart, model and agent tables, and waste receipts

Local SQLite · no accountVisibility from logs · enforcement in the provider path

Price the usage already on your machine.

Burnban turns supported local histories into a shareable, clearly qualified API-equivalent estimate. The window, rates, and plan multiple ride along in the output.

$ burnban subsidy --share
window      last 30 days
equivalent  $4,173.49
plan        20.9× a $200/mo seat

Terminal recording of burnban subsidy share producing a qualified 30-day API-equivalent usage result — Real shipped output · screenshot-ready · qualification included

Install the free meter.

Inspect the script first if you prefer. The installer verifies published checksums and fails closed.

Available now

macOS or Linux curl -fsSL https://burnban.sh/install | sh Windows PowerShell irm https://burnban.sh/install.ps1 | iex

№ 02How it works

See usage locally. Block supported API traffic.

Burnban separates what can be seen locally from what can be enforced in the request path, and the dashboard tells you which is which.

supported agent logs

read locallyvisibility only

agent or app

local Burnban metermeter · allow · block

chosen provider

Your usage data stays on your machine.

No Burnban account, telemetry path, or hosted gateway is required.
The usage ledger is local SQLite on the machine you control.
Provider keys go to your chosen provider and are never persisted by the meter.
Prompts and responses are not sent to a Burnban control plane.

Read the guide and check the release.

Follow the setup guide quickstart ↗ Inspect every source line MIT repository ↗ Verify release artifacts checksums + SBOMs ↗ Read the dated benchmark method + source ↗

№ 03Pricing and questions

The complete local meter is $0 forever.

Install it, inspect it, change it, and keep your data local. The open-source product is the complete meter.

Open sourceMIT licensed

$0 forever

One machine. Full local control.

Everything required to see usage and enforce supported provider traffic locally.

Local usage meter and dashboard
Daily, weekly, monthly, and agent caps
Local kill switch, reports, and exports
Subsidy and model repricing tools
Public source, releases, and checksums

Install Burnban

No card · no account · no telemetry

What can Burnban see from local logs?

It reads supported agent histories already stored on your machine and prices their recorded usage. Support varies by agent and log format.

Which traffic can it stop?

Burnban can enforce configured budgets only for supported provider-bound API traffic routed through its local meter. Log-only usage stays visible for pricing and reporting.

Do prompts or provider keys go to Burnban?

No Burnban cloud sits in the free meter path. Requests and keys go to your chosen provider. The local meter does not persist provider keys.

What is free, and what is separate?

The local meter, dashboard, limits, kill switch, reports, exports, and source are free. Cross-machine coordination is a separate product and is not offered on this page. The waitlist hears about that launch first.

№ 04Next instrument

One budget across every machine is next.

The free meter governs the machine it runs on. The next Burnban instrument coordinates several: one budget across your laptop, desktop, and CI, then org-wide policy for teams. It ships as a separate product on its own launch day.

Hold a place for the launch notice.

One email when the coordination instrument goes live. The list reads it first and installs first.

Launching soon