Costpilot documentation
Costpilot shows Engineering Managers and VPs of Engineering what AI coding assistants cost per project, issue, developer and model, not just per API key. It ingests the OpenTelemetry export of Claude Code, Gemini CLI and Codex CLI, attributes every session to the issue being worked on, treats developers and CI agents as actors side by side, and turns that into a dashboard with overview, drilldown, an analysis tab and date-range filters. Self-hosted in one click, one service, SQLite on a volume.
I run the serverDeploy Costpilot in one click or start it locally, secure it, invite the team.I write codeInstall the agent once, point it at your server, work as usual.I read the numbersWhat the tiles, dimensions and charts mean, and what is deliberately missing.
The two parts
| Costpilot server | Costpilot Agent | |
|---|---|---|
| What | API, dashboard and SQLite in one container | costpilot-agent CLI on each developer machine |
| Does | Receives telemetry, prices tokens, joins sessions to issues and projects, manages accounts, serves the dashboard and the Admin Area | Turns on the coding tool's telemetry export and installs a hook that reports the issue from the git branch on every prompt and turn end |
| Repo | getcostpilot/core | getcostpilot/agent |
How the docs are organised
- Getting started: one path from zero to your first attributed session, about 15 minutes.
- Guides: task-oriented pages such as securing an instance, projects, agents in CI pipelines or budget alerts.
- Concepts: how it works, attribution and what the telemetry can and cannot tell you.
- Reference: the API, environment variables, the agent CLI and the wire contract.
Try the live demo to see the dashboard with ten weeks of realistic data before you set anything up.