---
title: "What is Firefight?"
description: "Firefight is incident management that runs where your team already works, Slack."
canonical: https://firefight.app/docs/
---

# What is Firefight?

Firefight helps your team declare, coordinate, and learn from incidents without leaving Slack. When something breaks, anyone types `/ff new`. Firefight spins up a dedicated incident channel, announces it to the team, and keeps a structured record of who's leading, what's been tried, and what's still open, so responders can focus on fixing the problem instead of managing the process.

You work with Firefight in three places.

- **Slack** is where incidents happen. Declare incidents, assign a lead, post updates, track action items, and resolve, all with `/ff` commands and message reactions in the incident channel.
- **The web dashboard** shows the bigger picture. Browse and filter incidents, read timelines, edit postmortems, manage your service catalog, and configure how Firefight behaves for your workspace.
- **The API and connected agents** let your tools plug in. Send alerts from your monitoring stack and let routing rules decide what becomes an incident, subscribe to webhooks, or connect AI agents that can read your incident data.

## Start here

  - [Your first incident](https://firefight.app/docs/getting-started/your-first-incident.md): Declare, coordinate, and resolve an incident in Slack, end to end.
  - [Statuses, severities & types](https://firefight.app/docs/incidents/concepts.md): The four concepts Firefight uses to describe every incident.
  - [Slack command reference](https://firefight.app/docs/incidents/slack-commands.md): Every /ff command and reaction shortcut in one place.
