liwan
liwan - Lightweight Analytics
Runssource: GitHubhomepageRustApache-2.0commit 9db8a5efc9af
Rust, Apache-2.0 licensed. The project labels itself: analytics, privacy, rust, selfhosted and tracking.
liwan runs. An Argusic agent installed it in 29 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Liwan compiles, all 49 tests pass, and the server starts successfully accepting connections on port 9042
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.
- Install time
- 29 minutes
- Cold machine to finish
- 29 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- Model tokens used
- 587,595
- Exact commit tested
- 9db8a5efc9af
- Container image
- sha256:4c3d41857be3
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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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.
**ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 29, "err…
### What happened
- **Environment setup**: Installed Rust 1.98 via rustup, then downloaded and configured a prebuilt …
- **Build**: Created the missing `web/dist` directory (required by `rust-embed`), then `cargo check…
- **Tests**: All **49 tests** pass — 37 unit tests, 12 integration tests (auth, dashboard, events, …
- **Launch**: The server binary starts and correctly initializes the database, prints a first-time …
### Errors encountered
| Error | Fix |
|---|---|
| `cc` linker not found | Installed a prebuilt glibc toolchain from Bootlin and created wrapper scr…
| `web/dist` folder missing | Created empty `web/dist` directory |
| No `make`/`cmake`/`pkg-config` | Not needed — the `cc` crate and bundled builds (sqlite, duckdb, …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.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- 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
- Took 29 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
Of the 13 analytics projects Argusic has installed and timed, liwan was the 12th fastest to reach a running state, and 10 of 13 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- Following its own README: the documented path worked with nothing to fix.
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 | 100.00 | 0.17 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.20 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/liwan)Questions
- Does liwan run?
- Yes. liwan runs. Argusic installed and launched it on a clean machine in 29 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test liwan?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9db8a5efc9af. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test liwan?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does liwan take to install?
- 29 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 liwan need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing liwan?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does liwan compare with the alternatives?
- Of the 13 analytics projects Argusic has installed and timed, liwan was the 12th fastest to reach a running state, and 10 of 13 reached one at all.
- Where is the evidence for liwan?
- 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.