versus-incident

Versus Incident is the self-hosted AI SRE agent. It learns what your system normally look like and escalates only what is new or unexpected issues; routing to your chat channels and on-call platform.

Not yet testedsource: GitHubhomepageGoMITcommit aafc2d8403bc

Go, MIT licensed. The project labels itself: ai, ai agent, ai tools, alert, aws, devops, devops tools and golang.

versus-incident has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
808
forks
154
open issues
25
watchers
8
size
36 MB
created
last push

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.

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

No recorded runs.

Topics (from GitHub)

aiai-agentai-toolsalertawsdevopsdevops-toolsgolanghelmlarkmonitoring-toolon-callpagerdutyslacksretelegram

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/versus-incident.svg)](https://argusic.com/subject/versus-incident)

Questions

Does versus-incident run?
versus-incident has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test versus-incident?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for versus-incident?
All 0 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.

Discussion