Skip to main content
53 integrations Any MCP server

Integrations Your whole stack, behind one set of rules

Connect your cloud, observability, databases, code and on-call tools. Halon and your agents use them to work through an incident, and you decide what they may change.

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

Connected once, governed every time

Connect a tool once. From then on, every call to it follows your rules.

Connect

Connect in seconds. Sign in to many tools with one click. Any tool with an MCP server connects too.

  • One click sign in
  • Any MCP server
  • Encrypted in transit and at rest

Choose

See everything a tool can do, and switch off anything you never want touched. You decide who can use each one.

  • Every capability listed
  • Switch off any one
  • Turn a connection off at once

Govern

You decide who can see and who can change each tool, down to production. Agents only get the access you give them, and every call is on the record.

  • Access per person and per environment
  • Approval where you want it
  • Every call recorded
The catalog

53 integrations across your whole stack

Not listed? Connect any MCP server and choose what it may do.

Cloud and hosting

15

Where your apps run, and what you can change there

  • AWS
  • Azure
  • Cloudflare
  • Convex
  • DigitalOcean
  • Fly.io
  • Google Cloud
  • Kubernetes
  • Modal
  • Netlify
  • Northflank
  • Railway
  • Render
  • Trigger.dev
  • Vercel

Observability

11

Logs, metrics, traces and errors for investigations

  • Axiom
  • Better Stack
  • Datadog
  • Grafana
  • Honeybadger
  • Honeycomb
  • Logfire
  • New Relic
  • OpenStatus
  • Sentry
  • SigNoz

Alerting and on-call

2

Who is on call, and the alerts and incidents paging them

  • Opsgenie
  • PagerDuty

Status pages

2

What your customers see about an incident or planned work

  • Instatus
  • Statuspage

Product analytics

2

Who an incident reaches, what they saw, and the feature flags behind it

  • Mixpanel
  • PostHog

Databases

8

Your data and how it is set up

  • ClickHouse
  • Neon
  • PlanetScale
  • PostgreSQL
  • Supabase
  • Tinybird
  • Turso
  • Upstash

Code

4

Correlate incidents with what shipped

  • Azure DevOps
  • Bitbucket
  • GitHub
  • GitLab

CI

1

Builds, tests and their logs, and rerunning them

  • CircleCI

Coding agents

3

Agents that write a fix's code change and open the pull request

  • Cursor
  • Devin
  • Factory

Issues

2

Tickets and follow-up work tied to incidents

  • Jira
  • Linear

Knowledge

2

Runbooks and documentation as context

  • Confluence
  • Notion

Custom

1

Anything with an MCP server

  • Custom MCP server
In the dashboard

Every tool, one switch away

Every connected tool in one place. Turn any connection off in one click.

The FireFight Integrations page showing connected tools by category: Northflank for cloud and hosting, Datadog and Sentry for observability and PagerDuty for on-call, each switched on.
Each connection

Built for real production setups

Separate environments, multiple accounts, and a clear view of what runs where.

  • Separate access per environment

    Give production and development their own credentials, so each gets only the access it needs.

  • Every account, side by side

    Connect two GitHub organizations or two cloud accounts, each under its own name.

  • Your infrastructure, mapped

    What your clouds, hosts, databases and code hosts run appears on the resource map, each item linked to its page at the provider.

  • Metrics as charts

    When Halon reads metrics, you see the charts under its answer, in the dashboard and in Slack.

  • Code Halon never touches

    Protect paths such as .github/workflows/ on each GitHub, GitLab, Bitbucket and Azure DevOps connection. Halon's code changes stay out of them.

  • Know when a connection breaks

    Each connection shows whether it is healthy, with the error when it is not.

Documentation

Read how it works

Connect the tools you already run

Sign in with Slack, then connect your first tool in a click.

Sign in with Slack

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