VersusControl/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.
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
5 releases in the last 90 days, the latest 1 day ago, with 6 contributors on GitHub.
Use Cases & Benefits
- Provides a self-hosted AI SRE agent that monitors logs, metrics, and Kubernetes to auto-detect incidents and anomalies in systems and applications.
- Eliminates manual alert rule maintenance by using AI to learn normal patterns and only alert on new, unexpected issues.
- Use for automating incident detection and alerting in Kubernetes environments with integrated dashboards and Helm support.
- Use for consolidating alerts from multiple monitoring tools via webhook ingestion into a unified incident management workflow.
- Use for integrating on-call escalation with providers like PagerDuty and AWS Incident Manager to streamline incident response.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
MIT
Permissive: commercial use, modification and redistribution are allowed with attribution.
Community files
- README: present
- Contributing guide: present
- Code of conduct: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
Your AI SRE Teammate
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.
Auto-detecting incident in your system
Auto-detecting issues in Kubernetes
Incidents reach Versus two ways, and both are handled by the same notification, templating, and on-call logic:
Whichever source raises it, an incident is templated, fanned out to every channel you enable, and escalated to on-call if it isn't acknowledged in time.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
Forks
172+10
Open issues
25+0
Compared with peers in AI
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| thedotmack/claude-mem | 113.6K | +8.8K | 35 | today |
| D4Vinci/Scrapling | 98.1K | +6.9K | 65 | 1 day ago |
| Leonxlnx/taste-skill | 110.7K | +5.2K | 55 | 1 day ago |
| calesthio/OpenMontage | 77.2K | +4.2K | 40 | — |
| heygen-com/hyperframes | 79.6K | +4.1K | 45 | today |
| VersusControl/versus-incident | 919 | — | 46 | 1 day ago |
| Category median | 98.1K | +5.2K | 45 | — |
Discover Repositories
Search across tracked repositories by name or description