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 y

What is 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.

Overview of versus-incident

What it is

Versus Incident is a self-hosted AI SRE agent that learns what a system normally looks like and escalates only new or unexpected issues, routing them to chat channels and on-call platforms.

Key features

  • AI SRE Agent: Reads logs, metrics, and traces, learns normal patterns, and automatically opens an incident for new anomalies.
  • DevOps Agent Chat: A web-based chat interface in the Versus UI to enhance understanding of the connected system.
  • Kubernetes Harness Dashboard: Explore cluster health, capacity, workloads, resource relationships, recent changes, Helm releases, and GitOps status.
  • Multi-channel Notifications: Fan out incidents to Slack, Microsoft Teams, Telegram, Viber, Email, and Lark.
  • On-Call: Integrations with PagerDuty, Opsgenie, incident.io, and ServiceNow.
  • Webhook Alerts: Receive incidents from any tool that can POST a webhook (Alertmanager, Grafana, Sentry, CloudWatch SNS, FluentBit, etc.).
  • Custom Templates: Define alert messages using Go templates.

Use cases

  • Auto-detecting incidents in logs, metrics, and traces without maintaining alert rules.
  • Forwarding alerts from existing monitoring tools to a unified incident management system.
  • Monitoring Kubernetes environments with a dedicated dashboard.
  • Routing incidents to multiple communication channels and on-call platforms for team awareness and escalation.

Getting started

bash# AI SRE Agent (training mode)docker run -d --name versus-redis -p 6379:6379 redis:7docker run -p 3000:3000 -e GATEWAY_SECRET=change-me -e AGENT_ENABLE=true -e AGENT_MODE=training -e REDIS_HOST=host.docker.internal -e REDIS_PORT=6379 -v $(pwd)/config:/app/config -v $(pwd)/data:/app/data ghcr.io/versuscontrol/versus-incident# Webhook alertsdocker run -p 3000:3000 -e GATEWAY_SECRET=change-me -e SLACK_ENABLE=true -e SLACK_TOKEN=your_token -e SLACK_CHANNEL_ID=your_channel ghcr.io/versuscontrol/versus-incident

License and pricing

MIT license. Open source.

Based on the project's public README and repository metadata.

Add this badge to your README

Featured on YunoDB Badge styles & help

Maintain this project? Show that it is featured on YunoDB.

Markdown[![Featured on YunoDB](https://yunodb.com/badge/versuscontrolversus-incident.svg)](https://yunodb.com/tools/versuscontrolversus-incident?utm_source=github&utm_medium=badge)
HTML<a href="https://yunodb.com/tools/versuscontrolversus-incident?utm_source=github&utm_medium=badge"><img src="https://yunodb.com/badge/versuscontrolversus-incident.svg" alt="Featured on YunoDB" height="20"></a>