Skip to content
UsageAtlas logo

UsageAtlas

Free open-source desktop app that tracks token usage, cost estimates, and limits across 14 AI coding tools.

Actively maintained

At a glanceswept Oct 18, 2026

≈ 20visits/mo

Emerging · estimate, read Oct 18, 2026

For
Developers who use several AI coding tools and want to track usage, costs and limits on their desktop.
Activity
Actively maintainedsite updated 3 weeks ago
Runs as
Desktop app
Used for
  • track token usage across multiple AI coding tools
  • check remaining credits and reset times before starting work
  • compare usage and estimated cost across past periods
Worth knowingcomputed from what we read · each with its source
  • Publishes llms.txt, a file written for AI assistantsusageatlas.com ↗
  • Launched on Product Hunt on Aug 29, 2026Product Hunt ↗
Alternatives in Productivityby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare UsageAtlas with

Pick up to two.

All 10 alternatives to UsageAtlas →

All Productivity tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use UsageAtlas for?

Sign in to leave a note
Questions this page answers
  • What is UsageAtlas?

    Free open-source desktop app that tracks token usage, cost estimates, and limits across 14 AI coding tools. It is listed in the Atlas under Productivity.

  • Who is UsageAtlas for?

    Developers who use several AI coding tools and want to track usage, costs and limits on their desktop.

  • Do people use UsageAtlas?

    Emerging: ≈ 20 visits/mo · estimate, 2026-10.

  • Is UsageAtlas still maintained?

    Actively maintained: site updated 3 weeks ago.

  • What are alternatives to UsageAtlas?

    In Productivity, by use: Superhuman, Rize, MeisterTask, You Have Time, Byterover, Race Calendar & Results.

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 tool 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.

How we read every tool → · By INITE Atlas Desk