# Faultline > Monitor HTTP endpoints, Docker, ECS, cron jobs, and queues. Faultline opens the incident, pages on-call, runs your runbooks, and answers your AI agent over MCP. Faultline (fltln.io) monitors HTTP endpoints, Docker containers, ECS services, cron jobs, and queues, and manages the full incident loop: detection, escalation, on-call, runbook automation, and AI-assisted diagnosis and remediation through a built-in MCP server. ## Core pages - [Faultline: the monitoring tool your AI agent can operate](https://fltln.io/): Monitor HTTP endpoints, Docker, ECS, cron jobs, and queues. Faultline opens the incident, pages on-call, runs your runbooks, and answers your AI agent over MCP. - [Faultline roadmap: what's live and what's next](https://fltln.io/roadmap): What Faultline does today and what comes next: SLO tracking, multi-region probes, monitors-as-code, and self-hosting. - [Migrating from Opsgenie to Faultline: the complete guide](https://fltln.io/opsgenie-migration-guide): Opsgenie shuts down April 5, 2027. Move on-call, escalation, and heartbeats to Faultline, including heartbeats Atlassian's tool skips. - [Faultline docs: setup guides for monitoring and MCP](https://fltln.io/docs): Set up Faultline: first monitor, AWS IAM role for ECS, runbooks and approvals, the MCP server for Claude, heartbeats, and security. - [AWS IAM role setup for ECS monitoring - Faultline Docs](https://fltln.io/docs/aws-iam-role): The exact AWS access Faultline needs: trust policy, read-only ECS policy, optional remediation policy, ExternalId, and scoping it down. - [Quickstart: your first monitor in 5 minutes - Faultline Docs](https://fltln.io/docs/quickstart): Add an HTTP monitor, understand its thresholds, route alerts with an escalation policy, and trigger a real test incident end to end. - [Runbooks and approvals - Faultline Docs](https://fltln.io/docs/runbooks-and-approvals): How Faultline remediation stays safe: approval by default, auto-run per runbook, verification after every run, and a full audit trail. - [Connect Claude to Faultline: MCP server setup](https://fltln.io/docs/mcp): Connect Claude Code, Claude Desktop, or any MCP client to Faultline: API key, client config, read-only vs state-changing tools, and a sample session. - [CLI and heartbeat monitoring - Faultline Docs](https://fltln.io/docs/cli-and-heartbeats): Install the Faultline CLI and monitor cron jobs, queue workers, and Docker containers with heartbeats: push syntax and copy-paste examples. - [Security and data handling - Faultline Docs](https://fltln.io/docs/security): How Faultline isolates tenant data, handles sign-in and API keys, what incident data reaches the AI model, and how long data is kept. - [Faultline refund and cancellation policy](https://fltln.io/refunds): Every paid Faultline plan has a 30-day money-back guarantee. How to cancel from billing settings, when your plan ends, and how to ask for a refund. - [Faultline pricing - free monitoring, Pro from $49/mo](https://fltln.io/pricing): Free for 5 monitors with no card. Pro is $49/mo flat for 50 monitors and 10 team members. Growth and Enterprise add faster checks and more seats. - [About Faultline: why Chris Collareta built it](https://fltln.io/about): Faultline is built by Chris Collareta, an engineer who has carried the pager. Why it exists, what it does not do, and how to reach the founder. - [Faultline FAQ: monitoring, on-call, runbooks, and AI](https://fltln.io/faq): Answers on what Faultline monitors, when it pages, how runbooks and AI approvals work, AWS access, data retention, pricing, and refunds. - [Chris Collareta, founder of Faultline](https://fltln.io/author/chris-collareta): Chris Collareta builds Faultline, a monitoring and incident tool for small SRE teams. Articles, docs, and how to get in touch. ## Comparisons and alternatives - [Faultline vs Better Stack: an honest comparison](https://fltln.io/compare/better-stack): How Faultline and Better Stack compare on monitoring, incidents, runbooks, and AI, including the MCP server Better Stack doesn't have. - [Faultline vs PagerDuty: monitoring and paging in one tool](https://fltln.io/compare/pagerduty): PagerDuty pages you but monitors nothing. Faultline covers detection to remediation, with on-call, runbooks, and AI in every plan. - [Faultline vs Datadog: the incident loop without the APM bill](https://fltln.io/compare/datadog): Datadog is full observability billed per host. Faultline is detection plus a self-closing incident loop at a flat monthly price. - [Faultline vs AI-SRE agents (NeuBird, Resolve.ai, Traversal)](https://fltln.io/compare/ai-sre-agents): AI-SRE agents reason over Datadog and Splunk. Faultline owns the detection layer underneath and gates every fix behind your approval. - [UptimeRobot alternative: Faultline](https://fltln.io/uptimerobot-alternative): UptimeRobot is cheap uptime checks. Faultline adds escalation, on-call, runbooks, AI post-mortems, and Docker, ECS, and heartbeat checks. - [Healthchecks.io alternative: Faultline](https://fltln.io/healthchecks-alternative): Healthchecks.io does cron monitoring well. Faultline does heartbeats plus HTTP, Docker, and ECS monitoring with a full incident loop, on-call, runbooks, and AI. - [Opsgenie alternative: Faultline (EOL April 2027)](https://fltln.io/opsgenie-alternative): Opsgenie shuts down April 5, 2027. Faultline replaces its on-call schedules and escalation, and adds the detection Opsgenie never had. ## Blog - [Faultline blog: monitoring and incident response notes](https://fltln.io/blog): Notes on monitoring, on-call, and incident response from the person building Faultline, including how the MCP server and runbooks work. - [I gave my monitoring tool an MCP server so AI runs on-call](https://fltln.io/blog/ai-agent-incident-remediation-mcp): Why Faultline ships an MCP server: an AI agent diagnoses incidents and, behind an approval gate, runs the runbook that fixes them. - [The postmortem process: a practical guide for small teams](https://fltln.io/blog/postmortem-process-small-teams): A postmortem process for small teams: when to write one, how to rebuild the timeline from alerts and Slack, 5 Whys, and action items that ship. - [How to monitor cron jobs and catch silent failures](https://fltln.io/blog/how-to-monitor-cron-jobs): How to monitor cron jobs with heartbeats: detect missed runs, stuck and failed jobs, set grace periods, and catch silent production failures early.