traks runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 18 minutes, hitting 4 errors on the way, and recorded the session.

How did Argusic test traks?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 762280a9a9b1. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test traks?

The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does traks take to install?

18 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 traks need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing traks?

4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for traks?

All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

traks

Self-hosted, privacy-friendly web analytics that deploys into your own Cloudflare account in two minutes. Free forever, MIT.

Runs with mockssource: GitHub homepageTypeScriptMITcommit 762280a9a9b1

TypeScript, MIT licensed. The project labels itself: analytics, cloudflare, cloudflare workers, iceberg, mcp, plausible alternative, privacy and self hosted.

traks runs, with stand-ins for the services it depends on. An Argusic agent installed it in 18 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Traks monorepo installs, builds, passes all CI checks, and both platform Workers (collect on :5010 and api on :5011) launch locally and respond successfully to HTTP requests.
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 86 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 86 / 100
cost of the verifying run: $0.05 (measured)
recorded runs: 2
last tested: 2026-10-26
stars: 295
forks: 29
open issues: 5
watchers: 1
size: 11 MB
created: 2026-02-18
last push: 2026-10-22

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-26. 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.

Time lost to each failure while testing traks, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Home API Worker (apps/home/api) cannot start locally — wrangler dev attempts remote connection to R2 bucket traks-releases which requires Cloudflare API credentials5 minutes
Node.js v18.19.1 installed but project requires >=20 (wrangler 4.107.1 requires >=22)1 minute
Doppler secrets not available (no doppler CLI, no API keys)1 minute
Better Auth warns 'BETTER_AUTH_SECRET appears low-entropy'

Install time: 18 minutes
Cold machine to finish: 9 minutes
Errors hit and fixed: 4 hit, 4 fixed with no human help
How the result was proved: yarn check:ci exited 0 (format passed, 7 build tasks succeeded, D1 drift check passed, tracker inlining check passed, changelog check passed); wrangler dev on collect worker responded HTTP 200 on GET /; wrangler dev on api worker responded HTTP 200 on GET /, /api/health, /api/claim-status ({"claimed":false,"needsCode":false}), /api/config ({"collectUrl":"http://localhost:5010"}); Vite dev servers for platform-web and home-web both responded HTTP 200 on GET /
Model tokens used: 309,894
Exact commit tested: 762280a9a9b1
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
Behaviour against real services: this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

exec
/bin/sh -lc 'echo "Time spent estimating..."
echo "Started: install + build = ~3 min"
echo "Started: worker verification = ~5 min"
echo "Total: ~8 min"' in /work/repo
 succeeded in 0ms:
Time spent estimating...
Started: install + build = ~3 min
Started: worker verification = ~5 min
Total: ~8 min
tokens used
309,894

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

Installed in 18 minutes.
Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed MIT, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

Of the 18 analytics projects Argusic has installed and timed, traks was the 9th fastest to reach a running state, and 14 of 18 reached one at all.

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

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs with mocks	92.00	0.05	2026-10-26 19:29 UTC
Argusic Runner	1/3	Unverified	80.00	0.02	2026-10-26 19:19 UTC

Topics (from GitHub)

analytics cloudflare cloudflare-workers iceberg mcp plausible-alternative privacy self-hosted web-analytics

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/traks.svg)](https://argusic.com/subject/traks)

Questions

Does traks run?: traks runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 18 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test traks?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 762280a9a9b1. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test traks?: The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does traks take to install?: 18 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 traks need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing traks?: 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does traks compare with the alternatives?: Of the 18 analytics projects Argusic has installed and timed, traks was the 9th fastest to reach a running state, and 14 of 18 reached one at all.
Where is the evidence for traks?: All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.