You know the drill: someone torches the weekly limit by Tuesday lunch, the whole team stares at a lockout, and the bill can't say who. ccMeter runs Claude on your infrastructure — every token pinned to a person, budgets enforced, pay-as-you-go instead of pay-and-pray.
No 5-hour lockouts, no weekly walls. Pay-as-you-go on your own Anthropic key — capacity that never tells your team to come back at 7pm.
Every turn is metered — input, output, cache read, cache write — and pinned to the person who ran it.
Your cloud account, your Anthropic key, your data. Nothing routes through a third-party agent vendor.
Your org spent $4,000 on Claude last month. Who spent it? On which project? Was it worth it? A shared key identifies a company, not a person — so when spend spikes, the only lever you have is revoking access for everyone.
One teammate runs a heavy agent loop in the morning. By 2pm the shared window is gone and everyone else is locked out of their own workday. Subscription resets turn team capacity into a zero-sum fight — and the fastest spender wins it.
Desktop CLIs and IDE plugins mean one developer, one machine, no roles, no approvals, no audit trail. Ops, support and analysts — the people with the most questions — never get access at all.
Who has actually adopted the agent? Whose prompts land in one shot, and who burns an hour in correction loops? Which repos soak up the spend? That signal exists today — and it evaporates the moment a session closes.
Adoption per person — who's in it daily, who never opened it, who quietly stopped last month.
Timing patterns across the week. See the crunch, see the calm, see what reality looks like.
Styles and correction loops, per person. Spot the habits that win — and teach them to everyone.
Every token attributed to a person and a project. The mystery bill dies here.
Tokens, tasks, one-shot rate, streaks. You see your numbers before anyone else does — including your lead.
Best-practice guides distilled from real sessions: what worked, why it worked, and what to try on your next task.
Your team's best prompts and patterns, saved and searchable. Nobody solves the same problem twice.
Your drafts and dead ends stay yours. Leads see aggregates and totals — never your transcript.
Pay-as-you-go capacity per person. Nobody's monster refactor can lock you out of your own afternoon.
A full workspace in a browser tab. Terminal loyalist? Point local Claude Code at it with two env vars.
Personal stats land in the developer's workspace before any rollup lands anywhere else.
Insights describe the team's patterns. Ranking people is a different product — we didn't build it on purpose.
The data finds friction. Deciding what it means is a conversation, not an alert.
Ships now. Self-hosted, your Anthropic key.
In build, in this order. No vapour — the roadmap is public.
Your cloud, your Anthropic key, your rules. Conversations, credentials and code never leave the perimeter — and every token finally answers to a name.
BRING YOUR OWN ANTHROPIC KEY · POSTGRES · DOCKER