versus-incident
The self-hosted AI SRE agent. You don't have to monitor your systems alone. Versus Incident will keep track of your services, applications, and systems, detect new or unexpected problems, and provide your team with the evidence needed to investigate.
Runssource: GitHubhomepageGoMITcommit aafc2d8403bc
Go, MIT licensed. The project labels itself: ai, ai agent, ai tools, alert, aws, devops, devops agent and golang.
versus-incident runs. An Argusic agent installed it in 19 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The checkout now builds and runs: the live server answered 200 on /healthz and /, stored a 201-created webhook incident and returned it from /api/admin/incidents, and the full Go (40 ok) and UI (946 passed) test suites pass.
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 60 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
- 19 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test ./... -count=1 exited 0 (40 packages ok); npm test exited 0 (79 suites, 946 passed); live server: healthz=200, / =200, POST /api/incidents=201, gateway-session=204, GET /api/admin/incidents=200 returning the webhook incident; data/incidents.json contains it
- Model tokens used
- 435,514
- Exact commit tested
- aafc2d8403bc
- 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.
- Live run: banner printed, `GET /healthz` 200, `GET /` 200, real Alertmanager webhook `POST /api/i… tokens used 435,514 Everything checks out. Final summary and required report line. **Fixes applied (staged in git)** - `ui/dist/` never existed → ran `scripts/build_ui.sh` flow manually (`npm ci` + `npm run build`); … - `testdata/learnexclude/metric-glob-parity.json` was missing from the checkout (file is gitignored… - `go.mod` requires toolchain go1.26.6 → Go 1.23.1 auto-upgraded to toolchain 1.26.6 during the fir… **Verification** - `go build ./...` exit 0; `go vet ./...` exit 0; `go test ./... -count=1` exit 0, 40 packages `ok`. - `npm run build` exit 0 (Vite `✓ built in 1.45s`); `npm run lint` exit 0; `npm test` exit 0 — 79 s… - Live run: banner printed, `GET /healthz` 200, `GET /` 200, real Alertmanager webhook `POST /api/i…
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 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 19 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
Of the 237 ai projects Argusic has installed and timed, versus-incident was the 206th fastest to reach a running state, and 168 of 237 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 | Did not run | 20.00 | 0.02 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.10 |
Topics (from GitHub)
aiai-agentai-toolsalertawsdevopsdevops-agentgolanghelmkubernetesmonitoring-toolon-callpagerdutyslacksretelegram
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/versus-incident)Questions
- Does versus-incident run?
- Yes. versus-incident runs. Argusic installed and launched it on a clean machine in 19 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test versus-incident?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit aafc2d8403bc. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test versus-incident?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does versus-incident take to install?
- 19 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 versus-incident need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing versus-incident?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does versus-incident compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, versus-incident was the 206th fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for versus-incident?
- 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.