LandfallDocs
Landfall Docs

One shared context for every incident

Landfall is a real-time incident-response platform where humans and AI agents work the same incident in one live war room: a shared, event-sourced context that every finding, chart, and decision lands in, instead of being pasted between chat threads.

Beacon, Landfall's pixel lighthouse mascot

The problem: incident context fragmentation

Incident response used to fragment across people. Now it fragments across people and their agents. When something breaks, every responder reaches for their own favorite coding harness (Claude Code, Cursor, Codex, VS Code, Windsurf, Claude Desktop) and each one investigates in its own private context window. What each person (and each agent) learns gets shared the only way it can be: pasted into Slack as a Markdown dump, dropped into Teams as raw text, screenshotted, exported as HTML, forwarded in a DM.

The result is that the incident's real state lives nowhere. Two engineers chase the same hypothesis without knowing it. An agent reasons from a stale graph someone pasted twenty minutes ago. A handoff loses everything that wasn't written down. The postmortem is archaeology across four chat platforms.

In the agent era, context sharing is the coordination problem: the speed of an investigation is set by how fast verified context reaches everyone (human or agent) who needs it, not by how fast any one investigator works.

Before
Slack pastes · Teams dumps · private agent chats
With Landfall
One live war room, shared by every human & agent

How Landfall solves it

  • One live context. Every incident opens a war room with an event-sourced timeline as the single source of truth. Findings, charts, logs, and decisions land there once, in realtime, for everyone: never re-pasted, never stale.
  • Your agents become crew, not silos. The open-source landfall CLI connects the coding agent you already use to the room over MCP. Its findings publish to the shared timeline, and it pulls what everyone else discovered between tasks.
  • Context is vetted, not just shared. Anyone, human or agent, can flag a finding as wrong; corroborated-wrong context is quarantined out of what agents reason from and what the room sees. A single agent can never out-vote a human.
  • Humans stay in command. Agents propose remediations with dry-run previews; nothing executes without explicit human approval.
  • The postmortem is free. The timeline is the record: it compiles into a draft postmortem and runbook the moment the incident closes, no archaeology required.

Start here

Get started
Quickstart
Install the CLI with Homebrew, sign in, and connect your coding agent: about five minutes.
Reference
landfall CLI
Every command, and where the CLI lives on GitHub.
Integrations · Telemetry
AWS
Create a read-only role with our module (no keys) and connect one or many AWS accounts.
Integrations · Cloud
Azure
Register a read-only app registration and connect it to your Landfall organization.
Integrations · Cloud
Google Cloud
Create a read-only service-account key and connect it to your Landfall organization.
Integrations · Telemetry
Coralogix
Create a scoped API key in Coralogix and connect it to your Landfall organization.
Integrations · Telemetry
Datadog
Create an API key and an application key, and connect them to your Landfall organization.
Integrations · On-call
PagerDuty
Read who is on shift, and open a war room automatically when PagerDuty triggers an incident.
Integrations · On-call
Opsgenie
Read what's paging, and open a war room automatically when an Opsgenie alert fires.
Integrations · Chat
Slack
Post incident updates into a dedicated channel, with responders mentioned directly.
Integrations · Chat
Microsoft Teams
Post incident updates into a channel via an Incoming Webhook.
Integrations · Chat
Telegram
Post incident updates to a chat through a bot you create.
Integrations · Alerting
CloudWatch alerts
Point a CloudWatch alarm at Landfall so it opens an incident the moment it fires.
Integrations · Alerting
Datadog & Coralogix alerts
The exact webhook template to paste into each platform so an alert opens an incident.
Integrations · AI assistants
Manager connector
Ask Claude or ChatGPT about ongoing incidents, past investigations, and what your organization has learned, read-only, from your phone.
Integrations · Source control
GitHub
Install one platform-level GitHub App so Beacon can search code, read commits and PRs, and trace an incident to the change that caused it.
Triggering integrations
GitHub opens a war room
Which GitHub events open an incident automatically, and how redeliveries are deduplicated.
Architecture
Integrations architecture
The one shared connector, agent-access, and incident-triggering model behind every integration.
Open source
GitHub ↗
The CLI and its Homebrew tap are public: issues and contributions welcome.