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.

Aurora is an open-source AI SRE agent that investigates production incidents on its own, turning each incoming alert into a structured root cause analysis with evidence and a suggested fix. Alerts arrive from PagerDuty, Datadog, Grafana, New Relic, OpsGenie, incident.io, or CloudWatch, and every one triggers a background investigation without waiting for a human to pick it up. The agents choose from more than thirty tools, run cloud and cluster commands inside sandboxed pods, query logs, compare deployments, and search a knowledge base of past incidents for similar failures. An infrastructure dependency graph shows the blast radius across services and providers. When the root cause is found in code, Aurora can draft the remediation as a pull request instead of stopping at a diagnosis. Finished investigations become postmortems with a timeline, impact assessment, and remediation steps, exportable to Confluence, Notion, or SharePoint, and automated actions can open the fix, notify Slack, or update living documents as new evidence lands. Command policies and guardrails bound what the agents may run, and any major language model provider can power the reasoning, cloud-hosted or local. 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.

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.

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.

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

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.

Five monitoring systems should not mean five places to look when something breaks at 3 a.m. Alerta is an open-source alert management server that consolidates alerts from many sources into a single stream, de-duplicates repeats, correlates severity changes, and shows only the current state of each problem in a web console built for fast scanning. Prometheus, Zabbix, Nagios, InfluxDB Kapacitor, cloud watch alarms, and your own scripts all post into the same HTTP API, which accepts a flexible alert format carrying environment, resource, event, severity, and custom attributes, so no tool has to contort itself into someone else's schema first. Repeats of a known fault raise a duplicate count instead of generating another page, and a severity change updates the existing alert rather than birthing a twin. Operators acknowledge problems, assign them, silence expected fire during blackout periods set for maintenance windows, and partition visibility by customer for teams that monitor other people's infrastructure. A command-line client, query language, webhooks, and plugin hooks carry alerts onward into tickets, chat, and paging workflows, and everything persists in MongoDB or PostgreSQL with API keys and OAuth protecting access. 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.

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.

Keep is an open-source AIOps and alert management platform built with Python FastAPI and Next.js. It provides a single pane of glass for monitoring alerts from 110+ integrations, alert deduplication, correlation, enrichment, and filtering, YAML-based workflow automation similar to GitHub Actions, AI-powered correlation and summarization, and customizable dashboards for incident management. With 12,100+ GitHub stars, Y Combinator backing, and an Elastic partnership, Keep is the open-source AIOps platform that centralizes alert management across your entire monitoring stack into a single customizable dashboard. Alert deduplication identifies duplicate notifications across providers, correlation groups related alerts into incidents based on rules or AI-powered semantic analysis using pluggable LLM backends supporting OpenAI, Anthropic, and local models via Ollama, and enrichment adds context from external sources like CMDBs and databases. Workflow automation follows a GitHub Actions paradigm with declarative YAML files defining triggers, conditions, and actions that can query MySQL, update Jira tickets, send Slack messages, execute Python scripts, or call REST APIs. Authentication supports no-auth, database, Auth0, Keycloak, OAuth2 Proxy, Okta, and OneLogin. The Common Expression Language enables advanced alert querying, slicing, and rule-based grouping to reduce noise. On RepoCloud, deploy Keep on a dedicated VPS with Docker Compose, root SSH access, and complete control over your alert infrastructure, all under the MIT license.

When an alert fires, OnGrid investigates it for you: an AI operations agent that correlates metrics, logs, traces, and topology, then names the root cause in plain language. A coordinator agent hands each question to specialist SRE, network, or database sub-agents, and the incident investigator walks the service graph for blast radius, queries Prometheus, Loki, and Tempo, and pins the cause to a line of source code before posting its report back to chat. Lightweight edge agents on every host dial out over a single tunnel, so no inbound ports are opened, and operators can reach any machine through an audited browser shell. The agent works through more than 26 read-only inspection tools in a sandbox, while anything that changes production waits behind an approval gate. Ask questions or receive reports in Slack, Telegram, Larksuite, DingTalk, or WeCom, and run it on Anthropic, OpenAI, GLM, DeepSeek, Gemini, Kimi, or any OpenAI-compatible endpoint. A workflow builder turns triggers, agents, tools, and notifications into repeatable automations, and a knowledge vault indexes runbooks, incident history, and repositories for search. Enroll Kubernetes clusters to inspect workloads and manage upgrades, or discover network neighbors, verify them over SNMP, and map them into the topology. Role-based access separates admins, users, and viewers. 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.

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.

Better Status Page watches your services around the clock and turns outages into calm, branded status updates for your users instead of a flood of support tickets. Its monitors probe HTTPS endpoints with authentication flows and TLS expiry warnings, ping and TCP ports, DNS records, Docker containers, mail servers over SMTP, IMAP, and POP3, and databases from PostgreSQL and MySQL to Redis, MongoDB, SQL Server, and Oracle. A slower-than-usual alert fires when a monitor's p95 response time climbs against its own last seven days, and passive webhook heartbeats catch jobs that simply stop checking in. Alerts reach the team through email, Slack, Discord, Microsoft Teams, Telegram, ntfy, Pushover, webhooks, and Twilio SMS or voice calls, with failure thresholds, quiet hours, rate caps, and grouping keeping the noise down. Incidents carry severity levels, public updates, linked monitors, and recurring maintenance windows, and subscribers follow along by email, webhook, RSS or Atom feed, or a JSON status API. A drag-and-drop builder restyles the public page with your branding, dark mode, and translations, a static fallback keeps the page readable if the server itself falls over, and uptime reports export to CSV for SLA reviews. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Keep users ahead of outages by consolidating infrastructure monitoring into Peekaping, a unified uptime monitoring and incident communication platform that alerts engineering teams to network and application failures before customers experience disruptions. Users can configure automated synthetic checks across HTTP endpoints, database engines, message queues, and container runtimes to verify response latency, payload integrity, and SSL certificate expiration. When performance thresholds degrade or connections drop, the platform broadcasts structured incident notices across twenty-two notification channels including Slack, Discord, Telegram, PagerDuty, and custom webhooks. Visual dashboards display live heartbeat timelines, historical latency percentiles, and rolling availability scores for each monitored endpoint. System administrators can assemble custom public status pages with custom domains, branded color schemes, and component grouping to inform external stakeholders during planned maintenance or unforeseen service degradations. Teams can schedule recurring maintenance windows to pause alert notifications during routine deployments and generate API tokens to automate monitor creation directly from CI/CD deployment pipelines. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Trusted by Cal.com, WhiteBIT, and Documenso and backed by 8,800+ GitHub stars, OpenStatus delivers the open-source status page and uptime monitoring platform that replaces Atlassian Statuspage, Better Stack, and Instatus with a single self-hosted deployment. The monitoring engine runs Go-based probes across 28 global regions on three cloud providers checking HTTP, TCP, and DNS endpoints in parallel with configurable intervals and multi-region consensus to eliminate false-positive alerts. Status pages ship with custom domain support, password and email-domain access controls, maintenance windows, grouped monitor components, and subscriber notifications via email and RSS. Incident management provides structured status reports with investigating, identified, monitoring, and resolved timeline phases that publish automatically to affected status pages. The monitoring-as-code workflow supports YAML configuration synced through the CLI, a GitHub Actions integration for CI/CD pipelines, and a Terraform provider for infrastructure-as-code deployments. The typed ConnectRPC JSON-over-HTTP API exposes a published OpenAPI specification with a Node SDK for programmatic access, while an MCP server connects AI assistants like Claude, ChatGPT, and Cursor directly to workspace data. The tech stack combines Next.js with shadcn/ui for the dashboard, Hono for the API server, Drizzle ORM over Turso for application data, and Tinybird for analytics. Private monitoring locations deploy as a single 8.5MB Docker image behind firewalls to check internal services. 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.

A polished public status page without Statuspage prices or a heavyweight observability suite: Kener is a status and uptime monitoring system built with SvelteKit and Node.js. It runs 11 monitor types - API, Ping, TCP, DNS, SSL certificate, SQL query, Heartbeat, gRPC, and GameDig game-server checks among them - each with configurable intervals and thresholds. Incident management covers the full lifecycle: structured timelines from investigation through resolution, acknowledgements, and subscriber-visible updates, plus maintenance windows with RRULE-based recurring schedules and automatic status transitions. Notifications reach email, Slack, Discord, and custom webhooks through trigger-based workflows with template-driven messaging. One instance can serve multiple branded status pages - per product, team, or region - with custom logos, colors, and CSS, localization into 21 languages, timezone-aware displays, and server-rendered pages that stay fast and SEO-friendly. Operations tooling includes role-based access for teams, API key management, a secrets vault, analytics integrations (Google Analytics, Plausible, Umami, and others), and a REST API with 17+ endpoints for automating incidents and monitors from CI/CD. MIT-licensed; Docker deployment with Redis, SQLite by default, PostgreSQL or MySQL for production.

When a service you run goes down at 3 a.m., Upstat is the watcher that notices first and writes it down. Add any HTTP or HTTPS endpoint and it checks in every sixty seconds, building a living record of uptime, response latency, and ping times that you can read at a glance from status and latency charts. Certificate details sit alongside each monitor, so an expiring TLS certificate stops being a surprise outage waiting for a date. Each monitor can appear on public status pages, and you can run several of them, mapping different pages to different domains so customers, clients, or separate products each get their own honest view of what is up. When a check fails, a Discord notification heads to your channel with the news, and the dashboard keeps the incident in its history instead of letting it vanish into a chat scrollback. Install it as a progressive web app, keep its data in SQLite for a one-file setup or PostgreSQL when the deployment grows, and the whole thing stays on infrastructure you control. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Monitoring everything from network switches to Kubernetes clusters since 2001 with over 6,200 GitHub stars and deployments exceeding 100,000 devices per installation, Zabbix has established itself as one of the most mature and feature-rich open-source monitoring platforms available, trusted by organizations including Dell, Salesforce, ICANN, and T-Mobile. The platform collects metrics from virtually any source using Zabbix Agent written in C, Zabbix Agent 2 written in Go with native plugin support, SNMP v1/v2c/v3 polling and trapping, IPMI for hardware health, JMX for Java applications, SSH and Telnet checks, HTTP/HTTPS polling, and ODBC database queries. Version 7.0 LTS introduced synthetic browser monitoring that executes user-defined JavaScript via WebDriver to simulate multi-step user interactions on websites, proxy load balancing with automatic host redistribution across proxy groups for high availability, in-memory proxy data buffering delivering up to 100x performance improvement, native multi-factor authentication with TOTP and Duo support, and just-in-time user provisioning from SAML and LDAP. Low-level discovery automatically detects file systems, network interfaces, SNMP OIDs, VMware resources, and Kubernetes pods, creating monitoring items and triggers dynamically. The alerting engine correlates events with configurable escalation chains, sending notifications through Slack, Microsoft Teams, PagerDuty, Jira, email, and SMS with customizable message templates. Over 1,000 official templates provide instant monitoring for Linux, Windows, VMware, AWS, Azure, Docker, PostgreSQL, MySQL, Apache, Nginx, and hundreds more. 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.