Versus Incident
Versus Incident is a self-hosted AI SRE agent and incident manager that learns what normal looks like in your logs, metrics, traces, and Kubernetes clusters, then opens a triaged incident the moment something genuinely new appears. Detection earns trust gradually. Training mode only observes and catalogs patterns; shadow mode records what it would have alerted so you can judge its instincts; detect mode creates real incidents with an AI-written summary, a severity, and suggested next steps attached. Existing alerting does not have to move: Alertmanager, Grafana, Sentry, CloudWatch, Fluent Bit, and custom scripts post to the same webhook endpoint, and every incident, however it arrived, is rendered with your Go templates. Delivery fans out to Slack, Microsoft Teams, Telegram, Viber, email, and Lark. Silence has a deadline, because unacknowledged incidents escalate to on-call through PagerDuty, AWS Incident Manager, Opsgenie, incident.io, or ServiceNow. The Kubernetes dashboard gathers cluster health and capacity, workloads, resource relationships, recent changes, Helm releases, and GitOps status, and a DevOps chat agent in the web UI answers questions against the connected systems while responders work. The admin dashboard reviews learned patterns, shadow events, and raised incidents, so the agent's judgment stays inspectable. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
OpsiMate
OpsiMate gives on-call teams one queue for alerts that would otherwise arrive in five different dashboards, each demanding attention in its own tab. Connect Grafana, Datadog, Zabbix, Uptime Kuma, Google Cloud, or any custom webhook source and watch incoming alerts land in one table with their source, service, severity, tags, and status attached. Filter the noise down to the team or service you own, group related alerts so one incident does not look like forty separate emergencies, and use mute policies when a known problem should stop paging people. Acknowledge work with one click, assign ownership so nobody wonders who is responding, resolve alerts from the same screen, and follow deep links back into Grafana or Zabbix when you need the original chart or trigger. Let supported integrations auto-resolve alerts when the underlying monitor recovers, and use root-cause notes and insights to keep the next responder from starting at zero. Discover services running in Docker, Kubernetes, and Linux virtual machines so the alert queue stays connected to the infrastructure behind it. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
OneUptime
With 7,400+ GitHub stars and a feature set that replaces seven separate SaaS subscriptions — Pingdom for monitoring, StatusPage.io for status pages, PagerDuty for on-call, Incident.io for incident management, Datadog for APM, Loggly for logs, and Sentry for error tracking — OneUptime delivers every tool your reliability team needs in a single open-source platform that is genuinely 100% open source under Apache 2.0 (not open-core). Uptime monitoring runs synthetic checks against websites, APIs, ports, SSL certificates, and DNS records from distributed global probes with configurable intervals and thresholds. Branded status pages publish automatically when monitors detect issues, notifying subscribers via email, SMS, webhook, or RSS without manual intervention during an outage. On-call scheduling routes alerts through escalation policies to the right engineer via phone call, SMS, push notification, Slack, or Microsoft Teams. The incident management workflow handles declaration, triage, communication, resolution, and post-mortem generation in a unified timeline. APM collects traces and metrics via native OpenTelemetry integration — no proprietary agents required — while log management provides full-text search and alerting. An AI agent continuously monitors telemetry data, identifies root causes, and opens GitHub pull requests with proposed fixes for review. Deploy via Docker Compose or Kubernetes Helm charts with a Terraform provider for infrastructure-as-code configuration. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
Grafana OnCall
With 3,900 GitHub stars, 140 contributors, and 380 releases since its 2022 launch, Grafana OnCall delivers developer-friendly incident response that routes alerts from any monitoring system to the right engineer at the right time through the right channel. The platform accepts alerts via unique API URLs from Alertmanager, Grafana Alerting, Zabbix, Datadog, Pagerduty-compatible sources, Jira, inbound email, and generic HTTP webhooks, then applies routing templates to direct each alert to the appropriate escalation chain. Escalation chains define notification sequences — notify the primary on-call via Slack, wait 5 minutes, escalate to SMS and phone, wait 10 minutes, page the secondary on-call and notify the engineering manager — continuing until acknowledgment or resolution. On-call schedules support multi-layer rotations with overrides, shift swaps, and timezone-aware handoffs rendered directly inside Grafana dashboards. ChatOps integration publishes alert groups to Slack channels and Telegram groups with interactive buttons for acknowledge, resolve, and silence actions. Template engines based on Jinja2 control alert grouping, appearance rendering, and behavioral automation. The REST API enables programmatic management of integrations, schedules, and escalation policies. Deploy via Docker Compose with PostgreSQL, Redis, and Celery workers alongside your existing Grafana instance. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GNU AGPL v3 licensed.
uptimepage
Uptime checks, a customer-facing status page, and on-call paging arrive in one self-hosted package, so a failing check can open an incident, page the right person, and update the public page without a second tool. Monitors cover HTTP, TCP, ICMP ping, DNS, TLS certificate expiry, domain expiry, cron heartbeats, and scripted browser login flows with per-step timings. Probe agents run in any region you choose, and the dashboard shows latency by region. Incidents open on failure and close on recovery, with acknowledgement to silence paging and reminders per monitor. Escalation policies page channels and schedules level by level, and layered on-call rotations support daily, weekly, or custom shifts, calendar overrides, and an iCalendar feed. Alerts reach Slack, Discord, Teams, Telegram, PagerDuty, SMS, WhatsApp, ntfy, Gotify, email, and webhooks. The public status page shows 90 days of uptime per component, maintenance windows, incident updates, and RSS, JSON, and email subscriptions. Everything can be driven by REST API, scoped tokens, a Terraform provider, or an MCP server for AI assistants. Self-hosted installs have no monitor limits and no plan to buy. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
Jarvis
Alertmanager forgets an alert the moment it resolves; Jarvis remembers everything. This web frontend watches all your Alertmanager clusters at once and streams firing alerts into one live view over WebSocket, no refresh as problems appear or clear. Every alert's lifecycle is stored, so the resolved view answers how often something fired and how long it burned, and a grace period keeps a missed poll from being recorded as a phantom resolution. When an alert lands, claim it so the team sees who is on it, and leave comments bound to that alert fingerprint; notes survive restarts and re-fires, so the next person inherits the context. Silencing gets a rehearsal: preview exactly which alerts a silence will hit before creating it, fire a one-click Fast-Silence from the list, and save templates for recurring maintenance. Filters use the Alertmanager matchers you already know, save as named sets, ride in shareable URLs, and one can be your default view. Point Jarvis at every member of an HA gossip cluster and duplicates collapse by fingerprint, while protected upstreams authenticate with OAuth2, bearer tokens or basic auth per cluster. Sign-in is optional through built-in accounts or any OIDC provider, and it runs as one hardened container on port 8080, with PostgreSQL available when you want replicas. Keep it behind your VPN or an authenticating proxy, as its own docs insist. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
OpenSRE
The pager fires at 3am, and OpenSRE starts the investigation before a human has found the dashboard password. It queries the connected observability and infrastructure tools, works toward a root cause, and records what the evidence supports. Past incidents stay useful because episodic memory stores root causes, alert types, affected services, and fixes, then surfaces the matching playbook during a similar failure. A Neo4j knowledge graph maps service dependencies and ownership, so the agent can traverse dependencies, estimate blast radius, and check recent changes with structural context. Fifty-one production skills cover Elasticsearch, Datadog, Grafana, PagerDuty, Kubernetes, AWS, Jenkins, Argo CD, and more, so teams keep the stack they already operate. Start investigations from the web console, Slack, or Microsoft Teams, and follow progress from the same places. The console holds the investigation list, a memory hub for browsing episodes, and a config editor for the deployment. Direct Anthropic access is the default path, and the optional LiteLLM proxy adds OpenAI, Gemini, and other providers. Microsoft Entra single sign-on signs users into the console, with token login kept as break-glass access. Fault-injection tests against a demo application exercise cart, product, recommendation, and advertising failures end to end. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
OpsKnight
When production breaks at 3 a.m., somebody has to know it is their turn, and OpsKnight keeps that answer on your own server instead of a per-seat subscription. Alerts from Prometheus, Grafana, Datadog, Sentry, CloudWatch, and generic webhooks arrive at authenticated endpoints, get deduplicated, and are routed to the right service. On-call schedules support rotation layers, daylight saving safe handoffs, and temporary overrides, and escalation policies page users, schedules, or whole teams in timed steps. Responders get push, email, SMS, WhatsApp, and Twilio voice calls where the keypad acknowledges the page. Each incident has an ownership panel, a timeline, notes, subscribers, action items, and SLA timers, and Slack or Teams war rooms keep chat in step. The Command Center shows active, muted, and unassigned incidents at a glance, analytics report MTTA, MTTR, and SLA compliance, and a System Health Center runs live diagnostics. A public status page with uptime history, maintenance notices, and subscribers keeps customers informed, and postmortems capture what the team learned. Sign-in supports OIDC and SCIM provisioning, and an installable mobile web app brings pages to your phone. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
IMPulse
Incident response moves into the chat tool your team already lives in, with every alert landing as a Slack, Mattermost, or Telegram thread that carries a Take It button and a running escalation clock. IMPulse gives each incident a lifecycle that prevents duplicates and reduces noise. Responders take an incident, assign it, or freeze it until tomorrow, next Monday, or later, from the thread or from the web table. Escalation chains, nested as deeply as needed, wait and then notify the next person, and schedules can be edited in the UI or read from Google Calendar. Inhibition rules suppress child incidents when a parent is active, and maintenance windows mute matching alerts during planned work. The web table offers multi-column sorting, Alertmanager-style filters with regex, custom colors, an archive of closed incidents, and a light or dark theme. Sign-in goes through your chat platform, so nobody needs a separate account. Jinja2 templates reshape incident messages, thread replies, and Jira tasks, and webhooks reach Twilio, Zvonok, Instatus, and other outside services. Several instances can run together for high availability, and a REST API with Swagger documentation exposes incidents to scripts. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.
Regen
When a production alert fires at 3 a.m., Regen is the self-hosted on-call and incident management platform that makes sure a human answers it, keeping alerts, incidents, schedules, and escalations on one shared timeline instead of split across three tools. Alerts stream in from Prometheus Alertmanager, Grafana, AWS CloudWatch, or any webhook, and deduplication collapses repeat firings before Regen opens an incident automatically; responders can also declare one by hand and let AI draft the title and summary. Layered on-call rotations absorb overrides, holidays, and leave, while multi-step escalation policies with timeouts keep paging the next person until somebody acknowledges, so a critical page never dies in one inbox. The incident timeline syncs to Slack and Microsoft Teams, where bot commands acknowledge, escalate, and post updates without leaving chat, and Telegram notifications cover teams that live there instead. One-click summaries and handoff digests brief the incoming shift, editable postmortem drafts are assembled from the timeline using your own templates, and similar past incidents resurface with what worked last time. AI is bring-your-own-key through OpenAI, Anthropic, or a local Ollama model, and the platform loses nothing core if you never enable it. Schedules and escalation policies import in one click from PagerDuty, Grafana OnCall, or Opsgenie, SAML single sign-on through Okta, Azure AD, or Google Workspace is free, and nothing caps your incidents, schedules, or postmortems. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.