tianji
Tianji: Insight into everything, Website Analytics + Uptime Monitor + Server Status. not only another GA alternatives
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit 1aba241d9a79
TypeScript, Apache-2.0 licensed. The project labels itself: analytics, docker, google analytics, monitor, self hosted, selfhosted, server status and statistics.
tianji runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, project builds successfully, shared and most server unit tests pass, client component tests mostly pass; server cannot launch without a PostgreSQL database
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 92 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.
- isolated-vm native build failed: missing -lz, -lbrotlidec, -lbrotlienc, -lcares, -lnghttp2, -licui18n, -licuuc, -licudata2 minutes
- Node.js v18.19.1 too old (requires >=22.14.0)2 minutes
- Server segfaults on start without PostgreSQL (DATABASE_URL not set)
- Install time
- 15 minutes
- Cold machine to finish
- 25 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pnpm check:type passed; pnpm build succeeded producing dist/src/server/main.js, public/index.html, tracker.js, and GeoLite2-City.mmdb; pnpm test in src/shared: 77 passed; src/server: 594 passed; src/client component: 86 passed; packages/client-sdk: 16 passed
- Model tokens used
- 193,334
- Exact commit tested
- 1aba241d9a79
- 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.
**Installation** completed after two fixes: - **Missing library symlinks**: `isolated-vm` native build needed `.so` symlinks for z, brotli, c-a… - **Node.js version**: The project requires `>=22.14.0` but the container had v18.19.1. Downloaded … **Build** (`pnpm build`): Succeeded. Produced the server executable (`dist/src/server/main.js`), cl… **Tests**: | Package | Result | |---|---| | `src/shared` | 77 passed, 1 skipped — **all passing** | | `src/server` | **594 passed**, 16 failed, 12 skipped — failures are 2 pre-existing snapshot misma… | `src/client` (component) | **86 passed**, 10 failed — failures due to `node:crypto` browser exter… | `packages/client-sdk` | 16 passed, 3 test files fail — pre-existing module resolution issues | **Server launch**: Cannot start without a PostgreSQL database (`DATABASE_URL`). The binary segfault…
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 15 minutes, faster than the median of the 12 comparable projects Argusic has measured.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, 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 13 analytics projects Argusic has installed and timed, tianji was the 7th fastest to reach a running state, and 10 of 13 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.09 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.18 |
Topics (from GitHub)
analyticsdockergoogle-analyticsmonitorself-hostedselfhostedserver-statusstatisticsumamiuptimeuptime-monitoruptimekumaweb-analytics
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tianji)Questions
- Does tianji run?
- tianji runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test tianji?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1aba241d9a79. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test tianji?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tianji take to install?
- 15 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 tianji need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tianji?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does tianji compare with the alternatives?
- Of the 13 analytics projects Argusic has installed and timed, tianji was the 7th fastest to reach a running state, and 10 of 13 reached one at all.
- Where is the evidence for tianji?
- 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.