talivia
Open-source, self-hosted revenue-first analytics for founders: web analytics, Session Replay, revenue attribution, and customer revenue integrations. datafast alternative
Runssource: GitHubhomepageTypeScriptMITcommit 6e2f5531548e
TypeScript, MIT licensed. The project labels itself: analytics, bing, datafast, dodopayments, google search, lemonsqueezy, polar and product analytics.
talivia runs. An Argusic agent installed it in 28 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, Prisma client generated, tracker and recorder scripts built, and all 463 tests pass. The application's test suite runs successfully end-to-end with mocked database. Production build and dev server require more RAM than available (1GB).
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.
- Next.js production build OOM (killed at page data collection with 119 workers) - only ~1GB RAM available10 minutes
- PostgreSQL not available in container (no Docker, no apt install permission)8 minutes
- Next.js dev server (Turbopack) crashes with EMFILE/too many open files due to pnpm's deeply nested node_modules symlinks5 minutes
- Node.js v18 installed, project requires Node.js 22+3 minutes
- pnpm not installed for Node 221 minute
- APP_SECRET not set in .env1 minute
- Install time
- 28 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- Model tokens used
- 170,383
- Exact commit tested
- 6e2f5531548e
- 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.
- 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.
- **Tests**: ✓ All 116 test files / 463 tests pass
- **Next.js production build**: ✗ OOM (needs >1GB RAM)
- **Next.js dev server**: Starts but crashes (memory pressure)
Let me now clean up the background processes and provide the final report.
exec
/bin/sh -lc 'kill $(ps aux | grep "next dev" | grep -v grep | awk '"'{print "'$2}'"') 2>/dev/null; …
succeeded in 871ms:
Cleaned up
Now let me compile my final report.
tokens used
170,383
Now let me compile my final report.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.
- Recovered from all 6 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 28 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, talivia was the 11th 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.
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.12 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.12 |
Topics (from GitHub)
analyticsbingdatafastdodopaymentsgoogle-searchlemonsqueezypolarproduct-analyticsrevenue-analyticsrevenue-attributionsession-replaystripeweb-analytics
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/talivia)Questions
- Does talivia run?
- Yes. talivia runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test talivia?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6e2f5531548e. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test talivia?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does talivia take to install?
- 28 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 talivia need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing talivia?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does talivia compare with the alternatives?
- Of the 13 analytics projects Argusic has installed and timed, talivia was the 11th fastest to reach a running state, and 10 of 13 reached one at all.
- Where is the evidence for talivia?
- 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.