head to head · open source
Umami vs GEOInflow
Umami has 39,739 GitHub stars, 8,433 forks, 127 open issues and last shipped 2 days ago. GEOInflow has 634 stars, 193 forks, 3 open issues and last shipped yesterday. Umami leads on adoption by 6,168% (39,739 vs 634 stars). Umami is written in TypeScript under MIT; GEOInflow is written in TypeScript under MIT. Umami has attracted 21% as many forks as stars, GEOInflow 30%. GEOInflow was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (web-analytics), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| Umami | GEOInflow | |
|---|---|---|
| GitHub stars | ★ 40K | ★ 634 |
| License | MIT | MIT |
| Written in | TypeScript | TypeScript |
| Last push | 2026-10-27 | 2026-10-28 |
| Forks | ⑂ 8.4K | ⑂ 193 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Umami if
- You weight community size — 40K stars and counting
- You want the MIT license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
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
About Umami
Umami Umami is a privacy first analytics platform. Traffic, campaigns, behavior, conversions, and revenue in one place — no cookies, no surveillance, self hosted or in the cloud. 🚀 Getting Started A detailed getting started guide can be found at umami.is/docs. 🛠 Installing from Source Requirements A server with Node.js version 18.18+. A PostgreSQL database version v12.14+. Get the source code and install packages Configure Umami Create an .env file with the following: Optional: set API URL to change the base URL used by internal UI API calls. Relative paths are served under BASE PATH ; absolute URLs are…
read the full Umami 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 Umami or GEOInflow more popular?
Umami has 39,739 GitHub stars and GEOInflow has 634. Umami has the larger community by that measure.
Are Umami and GEOInflow free?
Both are open source. Umami is licensed under MIT and GEOInflow under MIT. Neither carries a licence fee.
What is the difference between Umami and GEOInflow?
Umami is written in TypeScript 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, Umami or GEOInflow?
Choose Umami if you want the larger community (39,739 stars) or its MIT licence terms. Choose GEOInflow if its feature set, stack or MIT licence fits better. Both are self-hostable.