tellery
Tellery lets you build metrics using SQL and bring them to your team. As easy as using a document. As powerful as a data modeling tool.
Runssource: GitHubTypeScriptApache-2.0commit 0f0e1d2587b4
TypeScript, Apache-2.0 licensed. The project labels itself: analytics, bigquery, business intelligence, collaboration, dashboard, data analytics, data modeling and data science.
tellery runs. An Argusic agent installed it in 25 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Tellery API builds and runs with a temporary PostgreSQL 16.15 instance; all 159 backend tests pass; frontend web build succeeds with Vite
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.
- Chinese text search fails with simple participle - reversed CJK word matching fails15 minutes
- No PostgreSQL binary available in container3 minutes
- zhparser extension not available for PostgreSQL2 minutes
- npm peer dependency conflict: typeorm requires ioredis@^4 but project uses ioredis@^51 minute
- Install time
- 25 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm test exited 0, 159 passed; node dist/src/index.js started and connected to database; npx vite build in web package succeeded
- Model tokens used
- 488,326
- Exact commit tested
- 0f0e1d2587b4
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Errors encountered**: 1. **npm peer dependency conflict**: `[email protected]` requires `ioredis@^4.28.3` but project specif… 2. **PostgreSQL not available**: No postgres binary in container. Fixed by downloading embedded Pos… 3. **zhparser extension not available**: The migration tries to install `zhparser` (Chinese text se… 4. **Chinese text search fails with `simple` participle**: The `searchBlocks` test failed because `… **Verified by**: All 159 tests pass, server starts successfully, frontend builds. exec /bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2… succeeded in 0ms: {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 25, "errors": [{"msg": "np… tokens used 488,326
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 4 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 25 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 13 analytics projects Argusic has installed and timed, tellery was the 10th 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
Topics (from GitHub)
analyticsbigquerybusiness-intelligencecollaborationdashboarddata-analyticsdata-modelingdata-sciencedata-visualizationdatabasedbtnotebookself-hostedsql
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tellery)Questions
- Does tellery run?
- Yes. tellery runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test tellery?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0f0e1d2587b4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tellery?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tellery take to install?
- 25 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 tellery need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tellery?
- 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 tellery compare with the alternatives?
- Of the 13 analytics projects Argusic has installed and timed, tellery was the 10th fastest to reach a running state, and 10 of 13 reached one at all.
- Where is the evidence for tellery?
- 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.