Read
Always current. Your connections keep the map up to date as things change. Handbook pages you keep elsewhere stay in sync on their own.
- Refreshed on its own
- Live updates from most providers
- Synced handbook pages
- Read failures reported
Context Kept current
Context Halon starts from what your team knows
Your infrastructure, your owners, your rules and every past incident, in one place Halon reads before it answers. Connections keep it current. Your team keeps it right.
14 days free, then $99 a month per workspace. Nobody on the team needs a seat.
What Halon knows
Six sources, one picture
Every chat and investigation starts from them, and Halon queries them as it works. Each one links to its docs.
- Read from connections Resource map What runs where, and what depends on what. Read live from your clouds, hosts, databases and code hosts. Read the docs
- Kept by your team Catalog Services, teams, environments and product features, with owner teams and Slack channels. Each service links to the resources it runs on. Read the docs
- Approved by your team Handbook How your team releases, what counts as production, freeze windows and who directs Halon. Pages your team writes or accepts. Read the docs
- Confirmed by your team Memory Lessons from past incidents, postmortems and chats. Your team confirms, corrects or rejects each one. Read the docs
- Recorded by FireFight Incident history Past incidents, their timelines, findings and postmortems, with whether the team marked each answer right. Read the docs
- Read live Connected tools Logs, metrics, traces, deploys, CI and code. Every read a connected tool offers, through FireFight. Read the docs
Halon
Starts every chat and investigation from this context, and queries it at every step.
- Chat
- Investigations
- Fixes
How it stays current
Read live, confirmed by people
Connections refresh what can be read. People confirm what was learned. Anything a fresh reading contradicts is flagged before Halon relies on it.
Confirm
Your team decides what Halon remembers. Confirm or correct each lesson Halon learns. A handbook edit or a link Halon suggests waits until a person accepts it.
- Confirm or correct in Slack
- Handbook edits accepted first
- Suggested links confirmed
- Who decided, on the record
Correct
Live data beats old notes. A fresh reading outranks any memory or handbook page. A memory that no longer matches is set aside or flagged for your team to check.
- Live readings win
- Contradictions raised at once
- Outdated memories flagged
- Reminders for what waits
In an investigation
Context that changes the first ten minutes
-
Starts where the service runs
An investigation opens on the resources behind the incident's services and what changed around them just before it began.
-
Learns from the last time
Past incidents that fired the same alert arrive with the answer each one got. A confirmed answer is a worked example, a wrong one is a mistake to avoid.
-
Finds incidents by meaning
Halon searches past incidents, findings and postmortems that read like the current one, whatever words they used.
-
Cites the handbook page
Every chat and investigation starts from the handbook. An answer that follows a page links to it, down to the section.
-
Knows who owns it
The catalog names each service's owner team and Slack channel. Alert routing invites that team, and Halon reads ownership from the same record.
-
Memory checked against live results
A memory is a starting point, never proof. Live results outrank it, and an answer flags every unconfirmed memory it relies on.
Documentation
Read how it works
- /docs/catalog/map The map What goes on it, how it is read, links and live updates.
- /docs/catalog/overview The catalog Teams, services and owners, and how they meet the map.
- /docs/ai/handbook The handbook Pages, freeze windows, synced docs and the edits Halon proposes.
- /docs/ai/memory Halon's memory Where memories come from, and how your team decides on them.
- /docs/ai/investigations Investigations What a run starts from, including past incidents with the same alert.
- /docs/postmortems/overview Postmortems The record a completed incident leaves, and what Halon learns from it.
- /docs/api/integrations Connect an integration The tools Halon reads from, and what each is allowed to do.
- /docs/ai/reading-your-platforms Reading your platforms Every read a connected platform's API offers, with no approval needed.
Give Halon the full picture
Connect your cloud and your code, add your services, and Halon starts from all of it.
Sign in with Slack14 days free, cancel whenever you like. Or run it on your own servers.