For engineering leaders paying for AI tools
Kintri.ai puts the cost and token usage of Claude Code, Gemini CLI, Codex CLI and any OTLP tool next to commits, merged pull requests and reviews, per developer and per team. Prompt content is never collected. Set up in five minutes per machine.
Free for up to 5 developers · No credit card
Sign-in uses GitHub OAuth for identity only. It grants no access to repository contents.
Per UTC day
Per UTC day
Sample data. Last 30 days vs previous 30 days.
For teams running Claude Code, Gemini CLI, Codex CLI and other OTLP tools
Cost next to output
Every Claude Code session reports tokens in, tokens out, cache reads, cache writes and cost in USD; Gemini CLI, Codex CLI and other OTLP tools are received and stored under their own names. Every GitHub sync reports commits, additions and deletions, pull requests opened and merged, and reviews given. Kintri.ai rolls it up per developer per day, so the leaderboard can be sorted by cost, by merged PRs, or by anything in between.
Sort by any column. Figures cover the selected period.
| Developer | Cost | PRs merged |
|---|---|---|
| dev-4f1a | $412 | 38 |
| dev-9b0c | $388 | 31 |
| dev-2e77 | $301 | 22 |
| dev-c3d1 | $245 | 19 |
| dev-71aa | $109 | 7 |
| dev-e805 | $23 | 2 |
Sample data. Pseudonymization is on: managers see stable pseudonyms such as dev-4f1a instead of names.
Effectiveness, not just spend
Cost alone tells you who uses the tool the most. Acceptance rate tells you whether the tool's output survives contact with the developer. Kintri.ai records accepted versus rejected edits per session, lines added and removed by the assistant, and API errors, then charts them per day so a drop is visible the week it happens, not at the quarterly review.
Accepted and rejected edits per UTC day
Acceptance is computed from Claude Code's tool-decision events. Codex CLI sends a matching event that is stored today and not yet charted. It is a usage signal, not a code-quality verdict.
Per developer, per team, per day
A workspace holds your company. Inside it, teams group developers, and every developer has a page: sessions, active time, cost, tokens, acceptance, commits and merged PRs over any date range, compared with the previous range. Team pages roll the same figures up. Members see their own data, managers see their teams, owners and admins see the workspace.
Workspace totals with deltas against the previous period, four time-series charts and the sortable leaderboard.
The same tiles and charts for one team, so a manager can answer "is it working for us" without asking for a report.
Daily series for one person, including cache-read share, accepted versus rejected edits and GitHub activity. Pseudonymized if the workspace requires it.
GitHub, the other half
Connect a GitHub App (recommended: webhooks plus polling, scoped to the repositories you choose) or a personal access token encrypted at rest. Kintri.ai discovers repositories, lets you include or exclude them with glob patterns such as platform/* or !*-archive, and syncs commit, pull-request and review history into the same daily rollups the AI-tool telemetry lands in.
Repositories mirrored by the GitHub sync worker.
How it works
Sign in with GitHub, name the workspace for your team or company, invite owners, admins, managers and members.
Install the GitHub App on your organisation or paste a personal access token. Choose repositories with include and exclude globs. History starts syncing immediately.
Each developer creates one ingest token and switches on the OpenTelemetry export in their tool, once per machine. The Telemetry setup page in the app covers Claude Code, Gemini CLI, Codex CLI and any OTLP tool. From the next session onward, telemetry arrives; Claude Code fills the daily rollups today, other tools are stored under their own names until their rollups land.
export CLAUDE_CODE_ENABLE_TELEMETRY=1 export OTEL_METRICS_EXPORTER=otlp export OTEL_LOGS_EXPORTER=otlp export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf export OTEL_EXPORTER_OTLP_ENDPOINT=https://<ingest-host> export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer <token>"
Shown for Claude Code. Gemini CLI and Codex CLI use their own settings files. The exact values, with your endpoint and token filled in, are on the Telemetry setup page once you are signed in.
Privacy is the product, not the footnote
Kintri.ai ingests counts and timings from the OpenTelemetry export of Claude Code, Gemini CLI, Codex CLI or any OTLP tool: sessions, active seconds, tokens, cost, lines, accepted and rejected edits, API errors. Prompt text is never stored; only prompt length is recorded. Everything else is designed for a European engineering organisation with a works council, a DPO and an auditor.
Developer machine · never leaves
ingest boundary · Kintri.ai
Only metrics and counters leave the developer's machine, whichever tool sends them. The ingest path strips prompt-bearing attributes before anything is written; prompt text is never stored, only its length.
Raw telemetry is kept 90 days by default as platform policy. Daily rollups and the audit log may be kept up to 3 years. A workspace can shorten its rollup and audit windows below the platform values, never lengthen them.
When on, managers see stable pseudonyms instead of names and emails. Owners and admins always see identities, and everyone always sees themselves.
Owner, admin, manager and member roles. Members see their own data, managers the developers on their teams, admins and owners the workspace.
Every read of another person's data and every administrative change is recorded and cannot be edited. Export it for your auditor.
Run the whole stack on your infrastructure with Docker or Kustomize: web app, Rust ingest and sync workers, PostgreSQL. Your data never leaves your network.
Designed with GDPR, NIS2 and DORA obligations in mind. Kintri.ai is a measurement tool, not legal advice; your DPIA stays yours, and we would rather make it short. Data-processing agreement available on Enterprise.
Pricing
Privacy is not a tier. No prompt collection, pseudonymization, retention limits and the audit log are in every plan, including Free. You pay for developers and for how long you keep the history.
Small teams trying it on one repository set
Engineering organisations that need teams, longer history and multiple connections
Regulated organisations and teams that must keep developer data on their own infrastructure
Prices in USD, excluding VAT. A developer is anyone who sent AI-tool telemetry or had synced GitHub activity in the billing month. Owners and admins who only read dashboards are not billed. Annual billing is ten months for twelve.
Questions
Only what the tool's OpenTelemetry export emits. For Claude Code that is session counts, active seconds, input and output tokens, cache read and cache creation tokens, cost in USD, lines added and removed, accepted and rejected edits, API errors, and the length of each prompt. Gemini CLI and Codex CLI send their own equivalents. The text of prompts, responses and files is stripped by the ingest worker before anything is written and is never stored.
Claude Code, Gemini CLI and Codex CLI have built-in OpenTelemetry exporters; any other tool that speaks OTLP/HTTP works through the standard OTEL_* variables. Every metric Claude Code sends appears on the dashboards. Gemini CLI, Codex CLI and other OTLP tools are received and stored today under their own metric names; the dashboards chart Claude Code's names, the rest follows. Cursor, GitHub Copilot and IDE plugins have no client-side exporter and are not collected.
No. Sign-in uses GitHub OAuth for identity only. Repository activity is read through a separate GitHub App installation (recommended, webhooks plus polling) or a personal access token you provide, which is encrypted at rest. You choose which repositories are included with include and exclude globs; the sync worker reads commit, pull-request and review metadata.
Owners and admins see identities. When pseudonymization is on for the workspace, managers see stable pseudonyms instead of names and emails, scoped to the developers on their teams. Every developer always sees their own data. Changes to this setting are written to the append-only audit log.
Raw telemetry is kept 90 days by default; that window is platform policy. Daily rollups and the audit log may be kept up to 3 years, and a workspace can shorten those windows below the platform values but never lengthen them.
Anyone who sent telemetry from Claude Code, Gemini CLI, Codex CLI or another OTLP tool, or had synced GitHub activity in the workspace during the billing month. Someone on leave with no activity is not billed that month. Owners and admins who only read dashboards are not billed. Inactive developers still appear in history within your retention window.
Annual Team plans are charged at $120 per developer per year, the equivalent of ten monthly payments, so two months are free. You commit to a developer count for the year and can add developers at the pro-rated annual rate at any time. Monthly plans can be cancelled at any time and stop at the end of the current month.
Yes. The Enterprise / Self-hosted tier ships the full stack for Docker or Kustomize: the Next.js web app, the Rust ingest and sync workers and PostgreSQL. Developers point their tool's OTLP endpoint at your ingest host and nothing leaves your network. The web app makes no third-party script, font or image requests.
Kintri.ai is designed to be GDPR, NIS2 and DORA aware: data minimisation by schema, pseudonymization, enforced retention, role-based access and an exportable audit log. Compliance is a property of your processing, not of a tool, so your DPIA and records of processing remain yours; the Enterprise tier includes a DPA and help with your security questionnaire.
Create a workspace, connect GitHub and point your developers' AI tools at it: Claude Code, Gemini CLI, Codex CLI or any OTLP tool. Your first daily rollup lands tomorrow morning for Claude Code; other tools are stored from day one. Nothing about your prompts ever leaves the machine.
Free for up to 5 developers. No card required.