CodeBurn
Tracks AI coding tool token usage and costs by reading local session files, attributing spend to commits and pull requests.
≈ 98visits/mo
Established · estimate, read 2026-09-18
- For
- Developers tracking AI coding costs across Claude, Cursor, and other agents
- Price
- Freepricing page, read 2026-09-19
- Activity
- Activity not read yet
- Company
- founding year not on record
- Runs as
- CLIDesktop app
- Track token usage and costs across multiple AI coding agents
- Identify wasteful spending patterns and duplicate context reads
- Monitor real-time AI usage limits in menu bar
- #5
PostHog
Ingests product data and runs AI agents to investigate issues and recommend product improvements.
24.7knot readFree plan2020 - #23
GrowthBook
Runs A/B tests, manages feature flags, and analyzes product data from your data warehouse.
34.8kActiveFrom $40/user/mo2020 - #27
Weights & Biases
Tracks machine learning experiments, manages models and datasets, and monitors AI applications in production.
21.2kMaintainedFrom $60/mo - #28
ReadMe
Publishes and maintains API documentation with AI-assisted writing, version control, and developer analytics.
40.4kActiveFrom $250/mo - #35
Inspectlet
Records visitor sessions and heatmaps to show how users interact with websites.
3.5kMaintainedFrom $39/mo - #65
Actian
Provides data cataloging, quality monitoring, and conversational analytics for enterprise AI systems.
89.4knot readFrom $499/mo
What is CodeBurn?
Tracks AI coding tool token usage and costs by reading local session files, attributing spend to commits and pull requests.
Who is CodeBurn for?
Developers tracking AI coding costs across Claude, Cursor, and other agents
How much does CodeBurn cost?
CodeBurn is free, per its pricing page on 2026-09-19.
Do people use CodeBurn?
Established: ≈ 98 visits a month · estimate, 2026-09 · 41.4k npm installs a month.
What are alternatives to CodeBurn?
In Developer tools, by use: PostHog, GrowthBook, Weights & Biases, ReadMe, Inspectlet, Actian.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.