RoninForge / Goei / vs ccusage
ccusage, across your whole team.
ccusage is the fast way to see Claude Code usage on one machine. Goei is the hosted layer on top: it dedupes spend across every machine and teammate, attributes it per project, per developer, and per git branch, and keeps 12-month history re-priced at the rates that were live then. Both read the same local logs. Neither needs an API key.
No API keys, no proxy, no prompt content.
ccusage is a great tool
If you work solo on a single machine and want a quick number, ccusage is an excellent choice and you may not need anything else. Run it with npx ccusage and it reads the logs Claude Code already writes to give you daily, monthly, and per-session cost breakdowns, with no account and no API key. It is open source, fast, and it stays useful standalone. Goei does not replace it; Goei answers the questions that begin the moment a second machine or a second developer enters the picture.
Side by side
| ccusage | Goei | |
|---|---|---|
| Reads local ~/.claude logs, zero API keys | Yes | Yes, via the budgetclaw CLI |
| Runs as | CLI on one machine | Hosted dashboard, fed by the CLI on each machine |
| Cross-machine rollup, deduped | One machine at a time | Yes, deduped across every machine |
| Team and per-developer view | Single user | Up to 10 developers, per-developer attribution |
| Per git branch and per project | Per project, per model, per day | Adds per git branch and per developer |
| History re-priced at the rates that were live then | Requested, then closed unbuilt (#764) | Yes, 30 days free, 12 months on Pro |
| Budgets and hard caps | Reporting | Budgets and alerts; SIGTERM caps via budgetclaw |
| Cost | Free, open source | Free tier, plus Pro at $19/mo flat |
LOCAL usage value at list API rates and BILLED provider charges are always labeled separately and never added together.
Track Claude Code costs across a team
To track Claude Code costs across a 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, a hosted dashboard that dedupes across machines and teammates: cost per project, per developer, per git branch. No API keys, no prompts, nothing in the request path.
On a Claude Team or Enterprise plan, Anthropic's own admin analytics may be enough. Goei is for API-billed teams and for Pro and Max developers, with per-branch attribution and no admin keys.
One commit for team-wide cost visibility
To give a whole team the same per-project, per-branch cost view inside Claude Code, commit the companion claude-code-cost plugin to a repo's .claude/settings.json:
{
"extraKnownMarketplaces": {
"roninforge": { "source": { "source": "github", "repo": "RoninForge/claude-code-cost" } }
},
"enabledPlugins": {
"claude-code-cost@roninforge": true
}
}On the next session in that repo, each teammate is prompted once to install it (Claude Code v2.1.195 or newer); nothing installs silently. This registers the Claude Code plugin, not the CLI, so developers still install budgetclaw once to feed the dashboard.
Two-command setup
If you already run ccusage, you already have everything Goei reads. Install the open-source CLI and push your history. Works on Claude Pro and Max, where billing APIs do not exist.
- 1 Install the open-source CLI.
- 2 Sign in, mint a device token, and push your last 30 days. Open goei.roninforge.org, sign in with the magic link, create a token under Settings → Device Tokens, then run it once with --save so later syncs need no token:
Prefer to look before you sign up? Open the live demo, no account needed.
Frequently asked questions
What is the difference between ccusage and Goei? +
ccusage is a single-machine command-line tool: run it with npx and it reads the logs Claude Code already writes to give you daily, monthly, and per-session cost breakdowns on that machine, with no account and no API key. Goei is a hosted dashboard that adds the layer a single-machine CLI cannot: it dedupes usage across every machine and teammate into one team rollup, attributes it per project, per developer, and per git branch, and keeps 12-month history re-priced at the rates that were live then. Goei is fed by the open-source budgetclaw CLI, so it reads the same local logs and still needs no API key.
Is Goei a ccusage alternative for teams? +
Yes. ccusage runs on one machine at a time, so a team has to collect and add up separate numbers by hand. Each developer runs the open-source budgetclaw CLI instead, and Goei dedupes every machine and teammate into one rollup: cost per project, per developer, per git branch, for up to 10 developers on a flat plan. No API keys change hands.
Does Goei need an API key when ccusage does not? +
No. Goei's local track reads the same local ~/.claude session logs ccusage reads, through the open-source budgetclaw CLI, and sends only daily dollar-and-token rollups with a device token you can revoke. Zero keys, no prompt content, nothing in your request path. An API key is only needed for the optional billed track that reads a provider billing API.
Can I keep using ccusage and Goei together? +
Yes. ccusage stays useful for a fast local check on one machine. Goei adds the hosted cross-machine, cross-person, long-history layer on top, fed by budgetclaw, without touching an API key. Many people use ccusage for the quick number and Goei for the team rollup and the re-priced history.
Why does re-priced history matter? +
API rates change over time. ccusage users asked for point-in-time re-pricing in issue #764, which was closed without the feature being built, so an old month is not valued at the rates that were actually live then. Goei values every past month at the rates that were in effect on the days the usage ran, using the open AI Price Index, so an old month reads true month by month. The free tier keeps 30 days; Pro unlocks the full 12 months.
Goei is part of RoninForge. See the full overview, get started at goei.roninforge.org, or read the CLI source at github.com/RoninForge/budgetclaw.