Thanks to visit codestin.com
Credit goes to opsknight.com

OpsKnight 1.5 · AGPL-3.0-only · you run it

The 2am page should live on your servers — not in a SaaS you rent per person.

When production breaks, OpsKnight messages whoever is on call, opens a Slack room, and gives customers a status page. Afterward you write what happened. One product. Your machines.

Built for teams that already run Postgres and would rather operate a pager than pay per seat. Not a hosted cloud, and not native voice calls.

InstallGitHubLive status
License
AGPL-3.0-only
Parsers
27
Deploy
Compose / Helm
Hosting
Your VPC
Command center · OpsKnight 1.5
OpsKnight command center on a real install — open incidents, on-call, and MTTA/MTTR

The night, in order

Alert, page, talk, write it down.

The same sequence most teams already run. OpsKnight is the place that sequence lives — on your network.

  1. 01

    Something fires

    Monitoring tools send a webhook. OpsKnight understands 27 of those out of the box, plus generic JSON.

  2. 02

    Noise is grouped

    Related alerts become one incident, so one person is not messaged for every downstream symptom.

  3. 03

    Someone is paged

    The active rotation gets SMS, email, Slack, WhatsApp, or a push notification. If they miss it, the policy moves on.

  4. 04

    The team gathers

    A Slack channel is opened for that incident. Optional video link. Work stays on one timeline.

  5. 05

    You close it out

    Resolve, update the status page, and write what happened — with follow-up tasks if you need them.

The product

Screens from a real install.

Same sequence as the night: list, schedule, Slack, policy, service. Status is one page. Ack from a phone is the site on the home screen — no extra app-store product.

One list for what is open.

One list for what is open.

Incoming webhooks become incidents. You acknowledge, assign, and resolve. Related alerts can share a fingerprint so one person is not paged for every downstream symptom.

  • Open, acknowledged, and resolved in one place
  • Filter by service, urgency, and who is assigned
  • Write the postmortem from the timeline — OpsKnight does not invent a report
  • Ack from a phone by installing the site; same login as desktop

What you get

The night, in one install.

AGPL-3.0-only Community software. You host it and control the data plane. Separately licensed Enterprise or hosted offerings can add commercial capabilities without changing rights to published Community releases.

  • 01

    Incident command

    Open, ack, assign, resolve. Related alerts can share a fingerprint so one person is not paged for every downstream symptom.

  • 02

    On-call schedules

    Rotations, timezones, and last-minute swaps. The active layer is who gets the first message.

  • 03

    Escalation and paging

    Email, SMS (Twilio or SNS), Slack, WhatsApp, push, or a webhook. If they miss it, the policy moves on. No native voice calls.

  • 04

    Customer status page

    Public, restricted, or private. Optional custom domain and email subscribe. One page per install.

    See how it ships →
  • 05

    Analytics and SLA

    MTTA, MTTR, and compliance on your Postgres. You read the numbers; OpsKnight does not invent a postmortem.

  • 06

    Ack from a phone

    Install the site on the home screen. Same login as desktop. Not a separate app-store product.

Install

Run it where your systems already live.

Compose, Docker, Helm, or Kustomize. Postgres, NEXTAUTH_SECRET, and ENCRYPTION_KEY are required. There is no hosted cloud.

curl -sL https://raw.githubusercontent.com/opsknight-labs/OpsKnight/main/docker-compose.yml > docker-compose.yml
docker compose up -d

OpsKnight requires PostgreSQL, NEXTAUTH_SECRET, and ENCRYPTION_KEY. The bundled Docker Compose configuration starts both PostgreSQL and OpsKnight automatically.

First-Boot SecretsRequired
NEXTAUTH_SECRET

Generating...

ENCRYPTION_KEY

Generating...

PostgreSQL 14+ is required (bundled in Compose).

Need the longer walkthrough? Install page · Docs · Helm charts

Integrations

Your monitors already know how to send a webhook.

27 inbound parsers. Point the destination at OpsKnight. Events API v2 /v2/enqueue is an ingest adapter — not the product name.

Datadog
Datadog
Prometheus
Prometheus
Grafana
Grafana
Sentry
Sentry
AWS CloudWatch
CloudWatch
New Relic
New Relic
Slack
Slack
PagerDuty
PagerDuty Events API v2
Jira Cloud
Jira Cloud
GitHub
GitHub
All 27 parsers and sample payloads

Versus the usual stack

Incident response on infrastructure you operate.

You operate Community

The Community data plane is self-hosted in your environment. Enterprise modules or hosted offerings can be packaged separately.

Paging is text, chat, and push

Email, SMS (Twilio or SNS), Slack, WhatsApp, webhooks. No native voice calls in the current Community capability set.

One Community status page per install

Public or private, optional custom domain. Additional status-page capabilities can be packaged separately in future offerings.

Events API v2 ingest

Keep routing keys; change the destination URL. That is an adapter, not a PagerDuty clone of the whole product.

Full capability matrix

Community

Self-hosted Community. Clear commercial boundaries.

The v1.5 Community line is AGPL-3.0-only. Separately licensed Enterprise modules, support, or hosted services may be offered independently without changing the rights attached to published Community releases.

Community · self-hosted

Open source

Community edition · AGPL-3.0-only · your infrastructure

Install CommunityCompare deployment and capabilities
  • Self-hosted Community incident response and on-call
  • Schedules, paging, Slack rooms, status page, and write-ups
  • 27 inbound monitoring parsers
  • Install on a phone from the browser
  • Jira Cloud sync
  • AGPL-3.0-only Community source — you host it