Skip to main content
Resource map Live updates

Resource map See everything you run, and what breaks with it

Firefight maps your clouds, services, databases and code automatically, and keeps it current. When something fails, you see at a glance what depends on it, who owns it, and its recent incidents.

Sign in with Slack Read the docs

14 days free, then $99 a month per workspace. Nobody on the team needs a seat.

How it works

Builds itself, and stays current

Connect your cloud, hosts, databases and code. Firefight maps what runs where and how it connects, and updates as things change.

Read

Builds itself. Connect a tool, and its services, databases and functions appear on the map. Deploys and scaling show up as they happen.

  • Over 25 providers
  • Live updates
  • Always current

Link

Knows what depends on what. Firefight links services to the databases and queues they use, and shows how each link was found. You confirm the rest in a click.

  • Found automatically
  • Suggestions you confirm
  • Add your own

Respond

Shows the blast radius. When an incident hits, the services it touches light up, with everything that depends on them and what changed right before.

  • Blast radius
  • Recent changes
  • Linked to owners
In the dashboard

One resource, everything around it

Focus shows a resource with what it needs and what needs it, the catalog service it runs, any open incident and the key checks worth running first.

The FireFight resource map focused on checkout-api, outlined in red with INC-042 open. Its panel shows the catalog service it runs and its key checks, and the map shows the payments-gateway and orders-db it uses and the GitHub repository it is built from.
On the map

Every resource, with its context

  • What it needs, what needs it

    Focus on any resource to see what it depends on and what would stop if it failed.

  • Normal vs now

    Each resource has the checks worth running first, compared with its usual week.

  • Spot the unusual log line

    Firefight learns what a resource normally logs, so a new line stands out during an incident.

  • Every deploy and scale recorded

    Deploys, status changes and scaling are kept as changes, and any of them can start a workflow.

  • One search across everything

    Find any resource, service or team in one search.

  • Halon starts from here

    Halon begins every investigation from what the incident's services run on.

Documentation

Read how it works

Know what breaks when something breaks

Connect your cloud and your code, and the map draws itself.

Sign in with Slack

14 days free, cancel whenever you like. Or run it on your own servers.