SessClone vs ccusage vs Anthropic's Claude Code analytics
Three ways to see what Claude Code costs, what each one covers, and when SessClone is the one you want.
There are three common ways to see Claude Code usage and cost. They answer different questions, and plenty of teams use more than one.
The short answer
- ccusage is a command-line tool that reads the usage files Claude Code writes on the machine it runs on, and prints daily, monthly and per-session reports. Free and MIT-licensed. It is the quickest answer to "what did I spend on this laptop?".
- Anthropic's analytics — the Claude Code analytics dashboards for Claude for Teams and Enterprise, and for Claude Console (API) accounts — cover the people inside that one Claude organization or Console account, with adoption, accepted lines and spend.
- SessClone collects every Turn from every machine each person works on — laptops, servers, Claude Code cloud sessions and CI — into one Org, whichever Claude account each of them signs in with, and prices it per Member, Project, Device and Session.
Side by side
| ccusage | Anthropic's analytics | SessClone | |
|---|---|---|---|
| Where it runs | Your machine | Anthropic's dashboards | Hosted at sessclone.com, or self-hosted |
| Machines covered | The files on the machine it runs on | Accounts in one Claude org | Every machine with the Collector |
| People on different Claude accounts | Local files only, from every config directory on that machine | Only inside that organization | One Org, whatever account each signs in with |
| Cost per Project, Device and Session | Per day, session and project, on that machine | Spend per user | Yes, per Member, Project, Device, Session |
| Transcripts archived for review | No | — | Opt-in, per Member |
| Roles and scoped views | No | Role-based access | Owner, Admin, Manager, Member |
| Source | MIT | Closed | AGPL-3.0, Collector MIT |
A dash means the published docs say nothing either way.
When SessClone is the right one
- Your team's usage is spread across accounts. Some people use a personal Pro or Max subscription, some an API key, some a cloud environment. No one vendor dashboard sees all of them; the Collector reports from each machine, so SessClone does.
- You need the total, not one laptop's. Cloud sessions and CI jobs leave no usage files on anyone's laptop. The same plugin runs in a cloud environment's setup script, and every container a Member burns through collapses into one Device.
- You want cost by Project. Each Turn carries the git remote it ran in, normalised into a Project key, so spend lands on the repository that caused it.
- You want to keep your data. Self-hosting is free at any size: your Postgres, your bucket, your network. See Self-hosting.
When it is not
- You only want your own spend on one machine.
npx ccusage@latestgives you that with nothing to set up. - You want accepted-line or pull-request metrics. Both of Anthropic's dashboards count accepted lines, and the Teams and Enterprise one connects to GitHub for pull requests shipped with Claude Code. SessClone counts tokens and cost, not lines.
- Everyone is in one Claude organization and you run an observability stack. Claude Code can export per-user token and cost metrics over OpenTelemetry.
What SessClone sends
Usage only: token counts, models, timings, and the Session, Project and Device they belong to. Never a prompt, never a file's contents. Transcripts, which do contain both, are a separate upload that stays off until each Member turns it on for themselves. How collection works has the detail.
Self-hosting
From a clone to the first collected Turn, on your own Postgres, bucket and Supabase project.
How to track Claude Code costs per developer and team
Where per-person Claude Code spend shows up for each kind of account, why mixed accounts and cloud sessions fall through the gaps, and how to see one total per Member, Project and Device.