GEOInflow
Self-hosted web and AI crawler analytics for Generative Engine Optimization (GEO). Track visitors, AI search referrals, crawl logs, content coverage, and conversions. Jointly published by 猎看科技 · 北京日报社智源GEO. MIT licensed.
Runssource: GitHubTypeScriptMITcommit 3d1504c480d6
TypeScript, MIT licensed. The project labels itself: ai analytics, geo, mit, postgresql, self hosted and web analytics.
GEOInflow runs. An Argusic agent installed it in 38 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PostgreSQL 16.15, Redis 7.0.15, and Node 22.23.4 are running; pnpm dependencies installed; Prisma and Liekan SQL migrations applied; tracker, recorder, OpenAPI spec, MCP and API-client packages built; dev server serves the GEOInflow application at port 3302 with all 284 unit tests passing (154 Vitest API tests in 30 files, 52 package tests, 77 Liekan deployment/integration tests)
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- PostgreSQL not available in container5 minutes
- Redis not available in container3 minutes
- Node v18.19.1 installed, project requires >=22 <232 minutes
- Production next build timed out after 180s in resource-constrained container2 minutes
- initdb created lock dir /var/run/postgresql which doesn't exist1 minute
- build:prisma:client required before liekan:migrate1 minute
- Install time
- 38 minutes
- Cold machine to finish
- 40 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- curl -s http://127.0.0.1:3302/api/heartbeat returned HTTP 200 with body '{"ok":true}'; curl -s http://127.0.0.1:3302/ returned HTTP 200 with HTML containing 'GEOInflow' title (33282 bytes)
- Model tokens used
- 143,356
- Exact commit tested
- 3d1504c480d6
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
3. Redis not available -> Downloaded redis-server deb, extracted with lib dependencies, started 4. build:prisma:client needed before liekan:migrate -> Ran it first 5. OpenAPI generation failed without .env -> Used pnpm dotenv 6. Dev server watcher EMFILE -> Used NEXT_DISABLE_FILEWATCHER=1 7. Production next build timed out (resource constrained) -> Dev mode used instead (verified workin… Now I'll compile the final structured report. exec /bin/sh -lc "cat << 'EOF' EOF" in /work/repo succeeded in 0ms: tokens used 143,356
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 38 minutes.
- Recovered from all 8 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/geoinflow)Questions
- Does GEOInflow run?
- Yes. GEOInflow runs. Argusic installed and launched it on a clean machine in 38 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test GEOInflow?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3d1504c480d6. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test GEOInflow?
- The run that produced this verdict cost $0.50: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does GEOInflow take to install?
- 38 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does GEOInflow need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing GEOInflow?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for GEOInflow?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.