head to head · open source

Claude-Code-Usage-Monitor vs GEOInflow

Claude-Code-Usage-Monitor has 8,780 GitHub stars, 463 forks, 37 open issues and last shipped 4 months ago. GEOInflow has 688 stars, 223 forks, 3 open issues and last shipped yesterday. Claude-Code-Usage-Monitor leads on adoption by 1,176% (8,780 vs 688 stars). Claude-Code-Usage-Monitor is written in Python under MIT; GEOInflow is written in TypeScript under MIT. Claude-Code-Usage-Monitor has attracted 5% as many forks as stars, GEOInflow 32%. GEOInflow was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

Claude-Code-Usage-Monitor ★ 8.8K GEOInflow ★ 688 category Data & Analytics

← all 20902 open source comparisons

Side by side

Claude-Code-Usage-Monitor GEOInflow
GitHub stars ★ 8.8K ★ 688
License MIT MIT
Written in Python TypeScript
Last push 2026-07-05 2026-10-28
Forks ⑂ 463 ⑂ 223
Self-hosting Yes Yes
Data ownership Your server Your server

pick Claude-Code-Usage-Monitor if

  • You weight community size — 8.8K stars and counting
  • You want the MIT license terms
  • Your stack matches Python
  • You value the larger contributor base for long-term maintenance

full Claude-Code-Usage-Monitor profile →

pick GEOInflow if

  • You want the GEOInflow feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches TypeScript
  • You evaluated both and GEOInflow fits your workflow better

full GEOInflow profile →

About Claude-Code-Usage-Monitor

🎯 Claude Code Usage Monitor A privacy first Claude Usage Ops companion for Claude Code. It combines a Rich live terminal monitor with official statusline rate limits , machine readable state/export output, provenance labels, forecasting, and an opt in local usage warehouse. 📑 Table of Contents ✨ Key Features 🚀 Installation ⚡ Modern Installation with uv (Recommended) 📦 Installation with pip 🛠️ Other Package Managers 📖 Usage Get Help Basic Usage Configuration Options Available Plans 🙏 Please Help Test This Release! ✨ Features & How It Works Current Features Understanding Claude Sessions Token Limits by Plan…

read the full Claude-Code-Usage-Monitor overview →

About GEOInflow

GEOInflow English 简体中文 Self hosted web and AI crawler analytics for Generative Engine Optimization (GEO). Jointly published by 猎看科技 · 北京日报社智源GEO Quick start · Deployment · AI crawler analytics · Architecture · Documentation · Contributing GEOInflow brings website visitors, AI search referrals, server crawl logs, and content inventories into a shared website context. It helps teams understand which AI crawlers visit their sites, which pages they request, which important pages have no observed crawl activity, where requests fail, and how AI search contributes visitors and conversions. The system includes browser…

read the full GEOInflow overview →

More in Data & Analytics

Related comparisons

More Web & Product Analytics projects

Compare either of these against the rest of the Web & Product Analytics field.

Frequently asked questions

Is Claude-Code-Usage-Monitor or GEOInflow more popular?

Claude-Code-Usage-Monitor has 8,780 GitHub stars and GEOInflow has 688. Claude-Code-Usage-Monitor has the larger community by that measure.

Are Claude-Code-Usage-Monitor and GEOInflow free?

Both are open source. Claude-Code-Usage-Monitor is licensed under MIT and GEOInflow under MIT. Neither carries a licence fee.

What is the difference between Claude-Code-Usage-Monitor and GEOInflow?

Claude-Code-Usage-Monitor is written in Python and GEOInflow in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, Claude-Code-Usage-Monitor or GEOInflow?

Choose Claude-Code-Usage-Monitor if you want the larger community (8,780 stars) or its MIT licence terms. Choose GEOInflow if its feature set, stack or MIT licence fits better. Both are self-hostable.