Skip to content
OpsKnight
Install
NAVIGATEOpsKnight
Live status ↗
Install OpsKnight GitHub

WHY OPSKNIGHT EXISTS

Operational control
should belong to you.

Incident response is critical production infrastructure. OpsKnight unites on-call scheduling, multi-channel paging, ChatOps, public status pages, telemetry analytics, and blameless postmortems into a single sovereign platform you own and operate entirely within your infrastructure.

Deploy OpsKnightExplore the source
v2.1.0 StableRelease-backed build
AGPL-3.0-onlyPermanent copyleft protection
100% Self-HostedZero external data custody
28 Inbound SourcesDocumented request contracts
Unlimited RespondersZero per-seat licensing tax

THE PROBLEM WE SOLVE

The black-box incident SaaS paradox.

Engineering organizations have spent a decade containerizing, automating, and securing their production infrastructure, yet their critical incident management plane remains rented from closed, multi-tenant clouds.

The Status Quo: Proprietary Incident SaaS

Why incident SaaS breaks down at scale

  • The per-seat responder tax: $34–$50+/user/month penalizes adding developers, product managers, and stakeholder teams to rotations, creating operational communication silos.
  • Third-party cloud downtime: When major cloud providers experience regional outages, external SaaS alerting portals often degrade, blinding teams precisely when coordination is vital.
  • Opaque deduplication & routing: Incident correlation and routing logic run inside black-box proprietary engines with no way to inspect or debug unexpected escalations.
  • Data custody and compliance exposure: Sensitive stack traces, internal network IPs, customer impact metrics, and employee notes are continuously transmitted to multi-tenant cloud servers.
The Sovereign Standard: OpsKnight

Built from first principles for infrastructure teams

  • Zero per-seat licensing friction: Add every engineer, support lead, and executive to incident notifications and response teams with no license procurement friction.
  • Runs inside your own boundary: Deployed in your VPC, private Kubernetes cluster, or on-premises servers. Internal communication and response control planes remain functional regardless of external outages.
  • Auditable & deterministic: Inspect every schema definition, database migration, worker queue lane, and cryptographic signature check directly in the open repository.
  • Complete data custody: Your dedicated PostgreSQL database stores all incident timelines, response metrics, and retro action items under your enterprise backup and retention policies.

QUALIFICATION & BOUNDARIES

Is OpsKnight the right fit for your team?

We believe in honest qualification. OpsKnight is purposefully designed for teams that prioritize engineering control, reliability, and security over zero-maintenance outsourcing.

WHO OPSKNIGHT IS BUILT FOR

Teams that value operational control and data sovereignty

OpsKnight is built for engineering teams who consider incident response to be core infrastructure, not a disposable third-party accessory.

  • SRE, DevOps & Platform Teams: Engineers who operate Kubernetes, Docker, or bare-metal stacks and demand control over upgrades, databases, and network ingress.
  • Regulated & Privacy-First Orgs: Financial services, healthcare, defense, and public-sector teams operating under strict compliance rules where incident data cannot leave the boundary.
  • Teams Migrating from Deprecated Tools: Organizations seeking modern self-hosted stability in light of Opsgenie’s end-of-life (April 2027) or Grafana OnCall OSS archive.
  • High-Growth Engineering Orgs: Companies wanting to empower every engineer with on-call capability without facing unpredictable, compounding per-seat SaaS invoices.
WHO OPSKNIGHT IS NOT FOR

Teams looking for zero-maintenance SaaS outsourcing

Self-hosting requires engineering stewardship. OpsKnight v2.1.0 is not a turnkey hosted SaaS product.

  • Zero-Operations Teams: Teams that do not have infrastructure engineers or do not want to manage container runtimes, PostgreSQL databases, and SSL certificates.
  • External Managed SLA Seekers: Organizations expecting a third-party vendor to guarantee 99.99% uptime for their application servers and manage hardware failover.
  • Air-Gapped Telephony Without Gateway: Environments that require voice and SMS paging but cannot establish outbound network access to providers such as Twilio or dedicated telecom gateways.
  • Non-Technical User Bases: Organizations that prefer proprietary point-and-click drag-and-drop SaaS configurators over version-controlled infrastructure definitions.

ENGINEERING FOUNDATION

Built on four core architectural pillars.

Every line of code and feature in OpsKnight is guided by clear architectural disciplines designed to keep production response resilient under stress.

01 / Data Sovereignty & Custody

All incident notes, timelines, responder rotations, and retro evidence live in your dedicated PostgreSQL database. Backup with native pg_dump tools, encrypt at rest, and keep audit custody intact.

02 / The Unified Command Loop

Eliminate four separate point solutions. Alert ingestion, escalation policies, Microsoft Teams & Slack war rooms, public status announcements, and 5-Whys postmortems operate in one coherent platform.

03 / Deterministic Contracts

28 inbound integrations feature documented request starters, integration-key authentication with conditional signature verification, and transparent payload tracing. Alerts are never silently discarded by black-box filters.

04 / Pragmatic Topology Scaling

Deploy in 3 minutes via single-node Compose for evaluation. Transition seamlessly to decoupled Web, Scheduler, and Critical Worker pods with PgBouncer connection pooling when production demands HA.

GOVERNANCE & STEWARDSHIP

Open source from day one. Protected forever.

How the project is maintained, why copyleft licensing protects the community, and how to participate in development.

THE AGPL-3.0 COMMITMENT

Why we chose the GNU Affero General Public License

In recent years, numerous open-source infrastructure and observability projects launched under permissive licenses only to execute a “bait-and-switch” once they gained adoption—relicensing to restrictive proprietary licenses (SSPL, BSL) or abandoning their self-hosted editions.

OpsKnight v2.1.0 is intentionally licensed under AGPL-3.0-only. This copyleft license permanently protects our community: it ensures that anyone who modifies or hosts the platform must share their improvements under the same open-source terms. OpsKnight cannot be enclosed into a proprietary walled garden by cloud providers.

Inspect the AGPL-3.0 License

OPERATING PRINCIPLES

Guiding disciplines for resilient response.

Engineering standards that ensure OpsKnight remains dependable, inspectable, and sovereign when production is under stress.

PRINCIPLE 01

Deterministic Execution

Alert correlation, escalation steps, and responder paging execute with predictable certainty. We reject black-box heuristics and opaque algorithms in the critical paging path.

PRINCIPLE 02

Zero Telemetry Tracking

OpsKnight contains no phone-home analytics, tracking pixels, or outbound reporting. Your incident records, responder contact details, and postmortems stay strictly inside your network boundary.

PRINCIPLE 03

Permanent Open Source

Protected by AGPL-3.0 copyleft, OpsKnight’s core platform cannot be enclosed into a closed-source monopoly. Every database migration, background worker queue, and API contract remains permanently open, auditable, and sovereign.

PRINCIPLE 04

Predictable Operations

Deploy what you need: from single-node Docker Compose for simple setups to clustered Swarm or Kubernetes for high availability, with zero per-seat licensing penalties as your engineering team grows.

COMMERCIAL PEACE OF MIND

Self-hosting does not mean being on your own.

Organizations adopting OpsKnight can engage commercial support agreements, high-availability architecture reviews, migration assistance from PagerDuty/Opsgenie, and security onboarding directly with the maintainers.

Explore Support & ServicesContact the Maintainer

Your incidents should belong to you.

Run OpsKnight on infrastructure you control.

v2.1.0 · AGPL-3.0-only · Self-hosted · 28 inbound integrations

Install OpsKnightStar on GitHub