// the take
A self-hosted Django app for running incidents through Slack: declaring an incident spins up a dedicated comms channel, posts a headline update, and builds a timeline/report automatically. It's for teams who already run a Django stack internally and want a Slack-native incident workflow without buying a SaaS tool.
The core idea is solid - a slash command creates a real Slack channel per incident instead of relying on a shared war-room channel, and the headline post keeps a running summary visible org-wide without anyone having to write it by hand. It ships as an installable Django app with a REST API (via DRF) rather than a standalone service, so it drops into an existing internal tools codebase instead of adding another thing to deploy. There's an actual e2e test suite running against docker-compose in addition to unit/API tests, which is more than most internal tools get.
Last commit is March 2024 - this was Monzo's internal tool that got open-sourced and then left alone once the team moved on (several of its authors went and built incident.io instead, which tells you where the energy went). Slack is the only integration point; there's no Teams support and PagerDuty shows up as a screenshot in the docs rather than a real integration, so escalation/paging is on you to wire up. You're also on the hook for the operational side Monzo doesn't have to think about anymore: running Postgres, handling Django migrations, and exposing a public endpoint for Slack's webhooks (the docs literally suggest ngrok for setup), which is a lot of infrastructure to own just to get an incident channel bot.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →