About FireFight

FireFight is incident management that lives inside Slack. One command opens the incident channel, sets a severity and a status, assigns the roles, and starts a timeline that writes itself. When the incident is over, the postmortem is already drafted from what actually happened rather than from what anyone remembers a week later. It is built by FireFight Labs and it is open source, all of it.

Why we built it

The outage is rarely the hard part. The chaos around the outage is. Someone tags you in a thread that is already sixty messages deep, three conversations are tangled together, nobody has written down what has been ruled out, and it is not clear who is leading. Then it goes quiet, which is worse, because nobody can tell whether it is fixed or whether everyone assumed somebody else had it. Days later the postmortem has to be reconstructed out of scrolled-past threads with half of it already forgotten.

Incident tooling that lives in another tab does not solve that, because during an outage nobody opens the other tab. So FireFight runs where the response already happens. There is nothing new to learn, because it is the tool your team is already living in.

Open source, on purpose

The whole platform is AGPL-3.0 and the source is on GitHub. It is not an open core with the useful parts held back, and there is no separate paid edition of the code. If you self-host, you are running the same software we run.

That matters even if you never run it yourself. Incident data is some of the most sensitive data a company holds, and your security team can read exactly what touches it instead of taking our word for it. If your requirements change, you can take the software and run it on your own infrastructure. The point is that you are choosing us rather than stuck with us.

Things you can check

• The licence. AGPL-3.0, the entire platform, at github.com/FireFightLabs/firefight.
• Where it runs. Hosted by us at app.firefight.app, or on your own infrastructure, from the same source.
• What it costs. Flat plans sized by responders, not per seat. Everyone else follows along in Slack for free. See the plans.
• How it connects. A versioned REST API described by a published OpenAPI spec, outbound webhooks, and an MCP server that AI agents connect to directly. Developer resources.
• What happens to your data. We do not train models on it, known credential formats are stripped before anything is stored, and everything stored is encrypted. Read the detail, or the privacy policy.

Who it is for

Engineering teams that already respond to incidents in Slack and want the structure without the context switch. That covers the team of five that has no incident process yet and wants one that costs them nothing to adopt, and the team of a hundred that has a process nobody follows because it lives somewhere else. FireFight ships with working defaults for statuses, severities, roles and the declaration form, so there is nothing to configure before the first incident, and every one of those is yours to change afterwards.

Talk to us

We answer our own email. Reach us at hello@firefight.app, open an issue on GitHub, or join the community Slack. The contact page lists which address goes where.