Operational Scenarios · 1.4.0

Built for teams that already operate a stack.

These are real-world operational situations OpsKnight is built for. No hosted cloud dependencies, no per-seat billing surprises, and no mandatory external SaaS lock-in.

VPC & Air-Gapped Data Sovereignty

When production breaks, your incident logs, database stack traces, customer identifiers, and postmortem root-cause notes frequently contain sensitive infrastructure details. Many regulated industries (fintech, healthcare, defense) are legally prohibited from streaming their internal outage timelines to a third-party SaaS cloud.

How OpsKnight handles this:

  • All rotations, incident records, and timelines live strictly in your internal PostgreSQL database.
  • Zero outbound telemetry, zero marketing trackers, and zero phone-home pings.
  • Deployable in fully air-gapped VPCs with private container registries.

On-Call at Scale Without Per-Seat Taxes

Commercial on-call vendors charge $25 to $49 per user per month. As your engineering team grows from 20 to 200 developers, the monthly cost inflates rapidly simply to give engineers access to emergency rotation schedules.

How OpsKnight handles this:

  • Apache-2.0 open source license: invite 5 or 5,000 engineers at $0 subscription cost.
  • Resource-efficient runtime: operates comfortably on 0.5 vCPU and 512MB RAM ($5/mo cloud compute).
  • No tier locks: full access to escalation policies, webhooks, and ChatOps for every team member.

Slack ChatOps & Incident War Rooms

Engineers already collaborate in Slack during active incidents. Context switching between separate web dashboards, alert feeds, and chat apps slows down Mean Time to Resolution (MTTR).

How OpsKnight handles this:

  • Automatically provisions dedicated Slack incident channels (e.g. #inc-2026-payment-timeout).
  • Interactive message buttons allow 1-click Acknowledge, Assign, and Resolve directly inside Slack.
  • Auto-injects conference bridge links (Zoom, Google Meet, or Jitsi) into the war room.

Multi-Tier Escalations & SRE Rotations

Complex microservice architectures require distinct ownership boundaries. The payment team needs different on-call handoffs than the infrastructure or security team.

How OpsKnight handles this:

  • Configurable multi-tier escalation policies with customizable step delays (e.g. 5m, 15m, 30m).
  • Multi-channel delivery: Twilio SMS, AWS SNS, Mobile Push, Slack, WhatsApp, and Webhooks.
  • Flexible rotation schedules supporting daily, weekly, and custom shift handoffs with timezone awareness.

Compliance & Enterprise Audit Readiness

SOC 2, ISO 27001, and HIPAA audits mandate rigorous tracking of who was paged, when they acknowledged, what actions were performed, and full post-incident timeline logs.

How OpsKnight handles this:

  • Immutable audit trails documenting every state transition, ack timestamp, and escalation step.
  • OIDC and SAML 2.0 Single Sign-On integration with Okta, Azure AD, and Keycloak.
  • AES-256-GCM envelope encryption protecting stored integration secrets and notification tokens.