upstat
🟢 a simple open-source, self-hosted status monitoring tool
Runssource: GitHubhomepageTypeScriptMITcommit 658b6d29e4c6
TypeScript, MIT licensed. The project labels itself: go, golang, monitoring, nextjs, open source, react, self hosted and typescript.
upstat runs. An Argusic agent installed it in 16 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Upstat Go API builds and runs on port 8000 with SQLite, accepting user signup/signin, creating and listing monitors with heartbeat pings, and serving Swagger docs over HTTP.
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.
- Go is not installed in the container3 minutes
- Generated TypeScript types declare MonitorItem.id as optional string (id?: string) but the component expects id: number3 minutes
- .env default (DB_TYPE=postgres) causes panic — no Postgres server available0.5 minutes
- Install time
- 16 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- curl tested all API endpoints end-to-end: GET /api/users/setup returned 200 with needSetup=true/false, POST /api/auth/signup returned 200 with access_token, POST /api/auth/signin returned 200 with access_token, POST /api/monitors returned 200 with message success, GET /api/monitors returned 200 with 1 monitor listing, GET /swagger/doc.json returned HTTP 200. npx next build for apps/web completed with compiled successfully and 13 static/dynamic routes.
- Model tokens used
- 184,758
- Exact commit tested
- 658b6d29e4c6
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
10:32:47 | 200 | 229.331µs | 127.0.0.1 | GET | /api/monitors
Monitors: 1, ids: [1], status: success
=== 6. GET /swagger/doc.json ===
10:32:47 | 200 | 63.5µs | 127.0.0.1 | GET | doc.json
Swagger HTTP 200
=== 7. GET /api/users/setup (after signup) ===
10:32:47 | 200 | 55.011µs | 127.0.0.1 | GET | /api/users/setup
{"needSetup":false}
Everything works end-to-end. Here's my final report:
tokens used
184,758
Everything works end-to-end. Here's 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.
- Installed in 16 minutes.
- Recovered from all 3 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 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)
gogolangmonitoringnextjsopen-sourcereactself-hostedtypescriptupstatuptime-monitor
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/upstat)Questions
- Does upstat run?
- Yes. upstat runs. Argusic installed and launched it on a clean machine in 16 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test upstat?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 658b6d29e4c6. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test upstat?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does upstat take to install?
- 16 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 upstat need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing upstat?
- 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.
- Where is the evidence for upstat?
- 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.