RoninForge / Goei
earlyThe Claude Code cost dashboard for your whole team.
Track Claude Code spend across your team: cost per project, per developer, per model, across every machine and teammate. It still answers the solo question too, where does my AI money go and is my Claude Max plan worth it.
The zero-key local track reads the logs Claude Code already writes on each developer's machine. An optional billed track pulls what a provider account was actually charged. The two are always labeled and never summed.
No API keys, no proxy, no prompt content.
Or jump straight to the local-track quickstart.
One rollup, across every machine and teammate
Every developer runs the local CLI on their own machines. Goei dedupes the lot into a single team view and attributes it the way a team lead actually needs: cost per project, per developer, per model, per git branch. No key ever changes hands.
Cross-machine, cross-person, deduped
Two laptops and three teammates on the same repo roll up into one number, deduped by machine so nothing is double counted and nothing is lost.
Per-developer attribution
See which projects and people carry the spend. Owners and admins see the team and each developer; members see their own and, if you allow it, the team aggregate.
Invite by email, zero keys
Invites reuse the same magic-link sign-in. A developer joins with their own device token and their machines associate with the team. Up to 10 developers on one flat plan.
Project aliases for shared screens
Rename or redact client repo names per team, so a real project name never leaks on a shared dashboard or a screenshot.
Quickstart, local track
Three steps to a spend dashboard with no API key. Works on Claude Pro and Max, where billing APIs do not exist. Each teammate runs the same three steps.
- 1 Install the open-source CLI.
- 2 Sign in and mint a device token. Open goei.roninforge.org, sign in with the magic link, then create a token under Settings → Device Tokens.
- 3 Push your last 30 days. Only daily dollar-and-token rollups are sent. No prompts, no code, no keys.
$ budgetclaw sync --days 30 reading ~/.claude/projects/*.jsonl 30 days, 18 projects, 41 branches pushing daily rollups to goei... -> 30 days uploaded done. open goei.roninforge.org
Cost per project, per developer, per model
Once the local track is syncing, the dashboard breaks your Claude Code spend down the way you actually think about it.
Spend by project
Every session is attributed to the project it ran in. See which repos are quietly eating the most, ranked by dollar value.
Per-git-branch drilldown
Open a project and split it by branch. The CLI uses the gitBranch Claude Code already records on each log line, so a runaway feature branch is easy to spot.
Spend by model
See how Opus, Sonnet, and Haiku usage splits across your work, valued at list API rates so the numbers are comparable.
Light and dark, your way
A daily chart, a near-real-time today-so-far figure, draggable widgets, and a light or dark theme. It reads like a tool you keep open.
Every card carries a source chip so you always know where a number came from: BILLED for what the provider charged, LOCAL EST for what your local usage works out to at list rates. The two are never added together.
What you see
Today so far
LOCAL EST$41.20
at list API rates
Team usage value, 30d
LOCAL EST$553.00
18 projects, 3 developers
Actually billed, 30d
BILLED$135.00
Max plan flat rate
MyClient-web
main, feature/auth, +3 branches
$214.60
usage value, 30d
side-project
main, refactor/db
$88.10
usage value, 30d
docs-site
main
$31.40
usage value, 30d
Illustrative layout. The billed and usage-value figures are the maintainer's own verified June data, see below.
Is your Claude Max plan worth it
Connect both tracks and Goei puts the two numbers side by side: what your usage would cost at list API rates, next to what you were actually charged. For a Pro or Max subscriber, the gap is exactly what the flat-rate plan absorbed. A billed-only tool cannot show this, because a subscriber has no per-token bill to read.
Maintainer's own data, first 10 days of June
Usage value at list rates
$553
Actually paid
$135
That is a real, verified gap from the maintainer's own account, not a projection. It is the kind of number you cannot see from a billing page alone, because the billing page only knows the flat rate.
12-month re-priced history
API rates move. Goei values every past month at the rates that were live then, using the open AI Price Index, so an old month reads at the rate that was in effect at the time, not today. The free tier keeps a 30-day window; Pro unlocks the full 12 months.
Pricing
The free tier is a complete single-developer dashboard, forever. Pro adds the team, the machines, and the history. Pro is early: sign in with a magic link, no credit card to start.
Free
$0
Forever, for one developer.
- One developer, one machine
- 30-day history
- Cost per project, per branch, per model
- Is your Claude Max plan worth it: personal subscription-value card
- Basic budget and alerts
- Optional billed track for one provider
Pro
early$19/mo
Flat, for a team of up to 10 developers.
- Everything in Free, for the whole team
- Cross-machine, cross-person rollup, deduped
- Per-developer attribution and team view
- 12-month re-priced history
- Budgets and alerts per project, branch, and team
- Project aliases and redaction
- All billed adapters
Already run ccusage?
Goei is ccusage, but across your whole team and every machine, with 12-month re-priced history, and it keeps itself up to date. ccusage stays useful standalone; Goei adds the hosted cross-machine, cross-person, long-history layer that a single-machine CLI cannot, without touching an API key.
Budgets and alerts
Set a budget per project, branch, or the whole team, and get told when you cross it. Arrange the dashboard the way you want.
Phone push via ntfy
Budget alerts pushed to your phone through self-hosted ntfy. Subscribe to a topic, no app store account needed.
Webhooks and RSS
Pipe alerts to a webhook URL for Slack, Discord, or your own automation, or subscribe to a personal RSS feed.
Customizable widgets
Dashboard widgets are draggable and dismissible. Keep the cards you care about, hide the rest.
Privacy and trust
Zero keys for the local track
The local track never asks for an API key. The CLI reads files you already own and authenticates to the dashboard with a device token you can revoke.
Rollups only, never prompts
Only daily dollar-and-token rollups leave your machine. Prompt text, responses, and code are never read, never sent, never stored, and nothing sits in your request path.
Open-source CLI
The local agent is the budgetclaw CLI, open source and auditable. Read exactly what it sends before you run it.
Billing keys encrypted at rest
If you opt into the billed track, provider keys are encrypted at rest with AES-256-GCM and can be removed whenever you want.
Frequently asked questions
How do I track my Claude Code costs across my team? +
Each developer runs the open-source budgetclaw CLI, which reads the session logs Claude Code already writes and pushes daily dollar-and-token rollups to Goei with a device token. Goei dedupes across every machine and teammate and shows one team rollup: cost per project, per developer, per model, per git branch. No API keys change hands. The team rollup and 12-month re-priced history are the Pro tier at $19 a month for up to 10 developers.
Am I getting my money's worth from Claude Max? +
Goei answers whether your Claude Max plan is worth it by valuing your actual local usage at list API rates and putting that next to the flat rate you pay. For a subscriber the gap is what the plan absorbed. In the maintainer's own verified data for the first 10 days of June, usage value was $553 against $135 billed. A billed-only tool cannot show this, because a Max subscriber has no per-token bill.
Does Goei need my API keys? +
No. Goei reads the local logs Claude Code already writes to your machine and sends only daily dollar-and-token rollups with a device token you can revoke. Zero keys, no prompt content, and nothing ever sits in your request path. An API key is only needed for the optional billed track that reads a provider billing API.
Does Goei work if I am on Claude Pro or Max instead of the API? +
Yes, and the local track is the only way to get a real spend dashboard on Pro or Max. Provider billing APIs require admin keys that subscription plans do not have, so the usual billing-API approach cannot work for subscribers. The budgetclaw local track reads your own session logs instead and shows what your usage would cost at list API rates, per project, branch, developer, and model.
What is the 12-month re-priced history? +
Goei values every past month at the API rates that were live on the days the usage ran, using the open AI Price Index. An old month reads at the rate that was in effect then, not today, so the dollar figure is true month by month. The free tier keeps a 30-day window; Pro unlocks the full 12 months. See how the re-pricing works.
How is Goei like ccusage? +
Goei is ccusage, but across your whole team and every machine, with 12-month re-priced history, and it keeps itself up to date. ccusage is a single-machine, point-in-time CLI; Goei adds the hosted cross-machine, cross-person, long-history layer that ccusage cannot, without touching an API key.
How much does Goei cost? +
The free tier is a complete single-developer, single-machine dashboard with 30-day history, forever. Pro is a flat $19 a month for up to 10 developers and unlocks the team rollup, unlimited machines, 12-month re-priced history, per-developer attribution, and per-project and per-branch budgets. Pro is early; sign in with a magic link, no credit card to start.
How is Goei different from BudgetClaw? +
BudgetClaw is the local CLI that reads your Claude Code logs, enforces hard caps, and can stop a run on breach. It runs entirely on your machine. Goei is the web dashboard that turns the same local rollups into charts and per-project, per-branch, per-developer, per-model views across your team, and optionally adds a billed track from provider APIs. The budgetclaw CLI is also what feeds Goei's local track, so the two work together.
What does Goei mean? +
Goei (護衛) is Japanese for bodyguard. It guards your team's wallet from runaway AI costs.
Goei is part of RoninForge. Get started at goei.roninforge.org, or read the CLI source at github.com/RoninForge/budgetclaw.