AI cost visibility for engineering leaders

You don't know where your AI spend goes.
Costpilot does.

Costpilot pulls cost from your AI tools and pins each dollar to the issue that caused it. So you always know what a feature really costs. Set budgets and get warned before they run over.

See the demoGet startedTalk to us

Cost by project

$24,860 in scope · last 30 days

  • Platform Core$6,94028%
  • Growth$5,71023%
  • Mobile App$3,88016%
  • Payments$3,12013%
  • Data Platform$2,63011%
  • Internal Tools$1,4205.7%
  • Security & Compliance$1,1604.7%

Issues synced from Jira

Live demo - Try Costpilot right here. Real data, no signup.

This is the actual Costpilot dashboard running on sample data. Click through epics, issues, developers and models, switch the date range and see how AI spend rolls up per feature.

demo.getcostpilot.io
Open full screen

Sample data from a fictional team. Your own deployment shows your telemetry, self-hosted in one click.

Why the invoice isn't enough

AI costs are climbing. The invoice won't tell you why.

Today, visibility ends at the provider's total. Costpilot ties every token to the issue that burned it and rolls it up to the story and epic it belongs to. Stop asking what a model costs. Start answering what a feature costs.

  • Consolidate. Every provider, every model, one dashboard. No more stitching invoices together just to see your total AI spend.
  • Attribute. Every dollar lands on its issue, with name, type and status from your tracker, and rolls up to the epic. Filter by bugs or open work, no manual tagging.
  • Control. Set budgets for the whole org, a project, a feature, a developer or a model. Costpilot warns you when spend nears the limit, spikes, or is on track to run over.

Know what a feature costs. And know before it costs too much.

Budget alerts

evaluated just now

  • Platform Core quarterlyproject Platform Core · calendar quarter · day 39 of 92$9,020 / $18,000 · 50%projected $21,280 · 118% at the current rate
  • Search & discovery v2 budgetissue Search & discovery v2 (GROW-640) · lifetime$2,855 / $3,000 · 95%
  • Product LLM trafficsource app · rolling 30 days$449.0 / $550.0 · 82%
  • 6 on track
  • AI assistant in product budgetissue AI assistant in product (GROW-801) · lifetime$3,450 / $4,500 · 77%
  • Monthly AI budgettotal spend · calendar month · day 8 of 30$6,630 / $28,000 · 24%
  • Claude Opusmodel claude-opus · rolling 30 days$7,900 / $12,000 · 66%
  • Anthropic quarterlyprovider anthropic · calendar quarter · day 39 of 92$19,400 / $50,000 · 39%
  • Mobile Appproject Mobile App · calendar month · day 8 of 30$1,035 / $4,000 · 26%
  • Nightly CI agentactor ci-nightly · rolling 7 days$84.00 / $250.0 · 34%

9 budgets · evaluated every 15 minutes

Coding agents - Works with the coding agents your team already runs.

One install per developer machine wires them up. Tokens, model and cost arrive via OpenTelemetry, and a prompt hook ties every session to the issue on the git branch.

  • Claude Code

    Anthropic

    Cost and usage

    Tokens, model, cost and tool calls for every prompt, mapped to the issue on the branch.

    ~/.claude/settings.json

  • Gemini CLI

    Google

    Cost and usage

    Tokens, model, cost and tool calls for every prompt, mapped to the issue on the branch.

    ~/.gemini/settings.json

  • Codex CLI

    OpenAI

    Cost and usage

    Tokens, model, cost and tool calls for every prompt, mapped to the issue on the branch.

    ~/.codex/config.toml

Integrations - Plugs into the tracker you already use.

Cost lands on the issue key in the developer's git branch, so attribution works with any tracker. Where Costpilot syncs the tracker, issues also get their names, types, status and epics.

  • Jira

    Synced

    Issues are synced with name, type, status and epic. Filter spend by bugs, open work or a whole epic, no manual tagging.

    feature/PROJ-142-sso-login → PROJ-142 · Add SSO login

  • Azure DevOps

    Attributed · sync in progress

    Work item ids on the branch attribute cost per work item and project today. Syncing titles, types and the backlog hierarchy is in progress.

    feature/US-02.003-checkout → US-02.003

  • GitHub

    Attributed

    Issue numbers on the branch attribute cost per issue and repository today. Syncing titles, labels and milestones is on the roadmap.

    fix/142-sso-login → #142

  • GitLab

    Attributed

    Issue numbers on the branch attribute cost per issue and project today. Syncing titles, labels and epics is on the roadmap.

    142-sso-login → #142

Get started - Self-hosted in minutes. One service, your data.

Costpilot runs as a single service with SQLite on a volume. Deploy it on Railway, Docker or Fly.io, install the agent on each developer machine, and every AI coding session is attributed to its issue automatically.

1

Run the Costpilot server

Clone the core repo and start it locally with a seeded demo dataset, or deploy it with one click on Railway. The API serves the dashboard itself.

git clone https://github.com/getcostpilot/core
cd core && npm install
npm run seed && npm run dev
getcostpilot/core on GitHub
2

Install the agent

One command on each developer machine turns on telemetry export for Claude Code, Gemini CLI and Codex CLI, and installs the hook that maps every session to the issue on your git branch.

npm install -g git+https://github.com/getcostpilot/agent.git
costpilot-agent init --endpoint https://costpilot.example.com
getcostpilot/agent on GitHub
3

Work on a branch

Check out a branch that carries an issue id, such as feature/PROJ-123-login, and use your coding agent as usual. Cost for every prompt shows up under PROJ-123, per epic, developer and model.

Full documentation

Roadmap - What works today, what we are building, where you can jump in.

Costpilot is built in the open on GitHub. The roadmap lives in the issues; this is the short version.

Live

Cost per feature, Jira and budgets

AI spend per epic, issue, developer and model, with names, types and status synced from Jira. Budget alerts to Slack or a webhook. Claude Code, Gemini CLI and Codex CLI feed in through one hook. Self-hosted, one service, SQLite.

See the core repo
In progress

Spot savings per feature

A large share of tokens goes to models where a smaller one delivers the same result. Costpilot will show, per feature, where a switch saves money without costing quality.

Follow on GitHub
Open for contributions

Cost estimates before you build

Effort gets estimated before a feature is built, AI cost does not. Usage data from similar issues can give a range up front. Want to build this with us? The issue is open.

Pick up the issue
Suggest a featureAll open issues

Maintainers - Built by people who had to answer for the cost.

We were responsible for the cost of product development. Developer time we could plan and report. When AI spend showed up, we couldn't say which feature it went to. Costpilot is the answer we needed. We maintain the repos, review pull requests and keep the demo running. Contributions are welcome.

Patrick Roos

Patrick Roos

@bitsmuggler

Tech lead and software architect. Builds the server, the dashboard and the agent, and makes sure cost per feature stays a number leadership can act on.

workingsoftware.dev ↗fellow.gmbh ↗

Florian Bosshart

Florian Bosshart

Enterprise architect and product owner. Brings the business-case view: what a feature is worth, what it costs, and how that becomes a team's priorities.

Get involved

Costpilot grows with the people who use it.

Contact - Talk to us

Want a demo with your own numbers, or just have a question? Tell us a bit about your setup and we'll get back to you.