Versus Incident
PulseGate's liveness check found it on 8 Oct 2026; it is registered on GitHub and has been in the index since 27 Aug 2026. How this is checked
Versus Incident is an AI SRE agent that learns normal behavior across logs, metrics, and traces, then detects and investigates unusual changes. It proposes SLOs and routes relevant incidents to chat and on-call platforms, with a free MIT-licensed self-hosted core and hosted enterprise capabilities.
Inferred · not functionally tested
Overview
6 featuresPurpose: Reducing alert fatigue by detecting novel system behavior and investigating incidents before routing only meaningful issues to on-call teams.
Inferred · not functionally tested
Audience: SRE and DevOps teams
Inferred · not functionally tested
Functions: monitoring, agents, analytics
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: unknown · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: commercial_oss · license: MIT · platforms: WEB · deployment: browser, self_hosted, cloud_managed
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: versusincident.com · github.com. These links do not verify the individual claims.
In the Agent monitoring & governance space, Versus Incident takes a focused approach. Inferred · not functionally tested: It focuses on reducing alert fatigue by detecting novel system behavior and investigating incidents before routing only meaningful issues to on-call teams. Inferred · not functionally tested: Versus Incident is a B2B product aimed at SRE and DevOps teams. Basis unknown · not verified: Versus Incident is commercial open source (MIT). Basis unknown · not verified: It ships for the web, and it can be self-hosted.
Behind Versus Incident is VersusControl, and it first shipped in 2025. The project is developed in the open on GitHub with 1.4k stars and 35 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are anomaly detection, read-only investigation, and runbook recall. Inferred · not functionally tested: Catalogued interfaces include a public API.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Anomaly detection
- Read-only investigation
- Runbook recall
- Logs analysis
- Metrics analysis
- Trace analysis
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed27 Aug · 05:19 UTCVersusControl/devops-ai-guidelines seen via GitHub Search (Smart)Source: GitHub Search (Smart) · Open
Frequently asked questions about Versus Incident
- What does Versus Incident do?
- Inferred · not functionally tested: Versus Incident focuses on reducing alert fatigue by detecting novel system behavior and investigating incidents before routing only meaningful issues to on-call teams. It is catalogued under Agent monitoring & governance on PulseGate.
- Who is Versus Incident for?
- Inferred · not functionally tested: Versus Incident is a B2B product built for SRE and DevOps teams.
- Does Versus Incident have a free plan?
- Basis unknown · not verified: The core is open source (MIT), with commercial offerings on top.
- What platforms does Versus Incident run on?
- Basis unknown · not verified: Versus Incident runs on the web. It can also be self-hosted.
- Is Versus Incident still active?
- PulseGate's liveness check found it on 8 Oct 2026. Its GitHub repository shows 35 commits in the last 90 days.
- Who develops Versus Incident?
- Versus Incident is developed by VersusControl.
- When did Versus Incident launch?
- Versus Incident first shipped in 2025.
- Is Versus Incident open source?
- Basis unknown · not verified: Yes — Versus Incident is open source under the MIT license, developed on GitHub.
Similar projects
Closest matches by what these projects do