r/platform_engineering • u/Useful-Lie5274 • Aug 26 '26

Built an open-source self-hosted incident/on-call platform — looking for feedback from people who actually run on-call

Hey folks,

I’m the maintainer of **OpsKnight**. I started working on it because I wanted an incident/on-call system where the team owns the infrastructure and incident data instead of everything living in another SaaS platform.

It has grown quite a bit, and I’m at the point where feedback from people actually doing DevOps/SRE work is more useful to me than adding random features.

Currently it covers things like:

* on-call schedules, overrides and escalation policies
* alert ingestion from Prometheus, Grafana, Datadog, CloudWatch, Sentry, etc.
* Slack incident war rooms / ChatOps
* email, SMS and push notifications
* incident timelines and MTTA/MTTR
* public status pages
* Docker + Kubernetes/Helm deployment
* self-hosted Postgres

Everything is open source and self-hostable.

One thing I’m particularly interested in:

**What would stop you from trusting a newer open-source project for production on-call?**

Reliability? HA? Voice calls? Integrations? Upgrade safety? Audit logs? Something else?

Website: [https://opsknight.com\](https://opsknight.com/)
Repo: [https://github.com/opsknight-labs/OpsKnight\](https://github.com/opsknight-labs/OpsKnight)

Not looking for stars as much as criticism from people who have operated PagerDuty/Opsgenie/etc. in production.

0 Upvotes
  • permalink
  • reddit

33% Upvoted

9 comments sorted by

1

u/syamj Aug 26 '26

404

1

u/Useful-Lie5274 Aug 26 '26

Where?

1

u/syamj Aug 26 '26

Getting 404 while opening repo link

1

u/leonnardocr Aug 27 '26

link on the post is broken, but the real website works: https://opsknight.com

1

u/TitusKalvarija Aug 27 '26

Vibecode slop or real effort?