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.
Cachet
Cachet Core is the open-source engine behind Cachet 3.x status pages, giving your team a self-hosted page where incidents, maintenance windows, component health, and live metrics keep customers informed during downtime. You publish an incident with a name, status, and visibility, then post updates on its timeline as work progresses, and the public page reflects every change immediately. Services become components you can group and mark operational, degraded, partially out, or fully down, so visitors see exactly which part of your platform is affected. Maintenance gets scheduled ahead with its own updates, and subscribers receive notifications when new incidents appear or change. Custom metrics accept data points through the API and render as charts on the page, turning response times or queue depths into public proof of recovery. A JSON API creates and updates incidents from your monitoring stack, and webhooks push incident events to the chat rooms and tools your team already watches. The dashboard handles components, incidents, metrics, subscribers, tags, and user accounts, with status page customization and localization in more than 10 languages. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT 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.