Get startedin three steps.

Add a webhook in Settings → Integrations with its URL, the method (POST, PUT or GET), any custom header fields and, optionally, a signing secret. FastMonitor sends each alert as JSON (a GET sends no body) and retries a failed delivery with backoff, so use dedupeKey to ignore one you have already handled. eventType is triggered or resolved.

With a signing secret, every request carries X-Alert-Signature: sha256=<hex HMAC-SHA256 of the body>. A GET is signed over the empty string. Check it against the raw body, before parsing it, and compare in constant time; reject the request when the function returns false.

{
  "alertEventId": "<alert event id>",
  "monitorId": "<monitor id>",
  "issueId": "<issue id>",
  "ownerId": "<account id>",
  "severity": "critical",
  "title": "<short summary>",
  "body": "<what failed>",
  "dedupeKey": "<idempotency key>",
  "eventType": "triggered",
  "links": { "issueUrl": "<link to the issue in the dashboard>" }
}

const crypto = require('node:crypto');

function verifyAlertSignature(rawBody, signatureHeader, signingSecret) {
  const expected =
    'sha256=' +
    crypto.createHmac('sha256', signingSecret).update(rawBody).digest('hex');
  const received = Buffer.from(String(signatureHeader || ''));
  const wanted = Buffer.from(expected);
  return (
    received.length === wanted.length &&
    crypto.timingSafeEqual(received, wanted)
  );
}

An HTTP check requests your URL on a schedule. It passes when the status code is one you expect and every assertion passes. An assertion that cannot be evaluated, such as a JSON path on a body that is not JSON, fails instead of passing silently.

To avoid alerts for a single blip, set how many failed checks in a row, from 1 to 100, it takes before FastMonitor opens an issue. The issue resolves on its own when the check passes again.

• SSL certificate. Connects to your host (port 443 unless you change it) and fails when the certificate is not valid, does not cover the host name, has an untrusted chain, or expires within your warning window: 30 days by default, with an optional stricter critical threshold. On an HTTPS check you can instead assert on ssl_certificate.expires_in, the days left on the certificate.
• DNS record. Resolves an A, AAAA, CNAME, MX, TXT, NS or CAA record and compares the answer with the values you expect: an exact match, contains all of them, contains none of them, or any record at all.
• Domain expiry. Reads your domain's registration through RDAP and warns when it expires within your warning window (30 days by default).
• Broken links. Crawls your site from a start URL and its sitemap, 50 pages a run by default and up to 500, and reports broken pages and links and redirect loops. It reads the HTML and does not run JavaScript.

A notification list is a named group of email recipients and integrations. Each monitor alerts one list; a monitor without a list alerts your default list. Alert channels: email on every plan, Slack, webhooks, Microsoft Teams, Discord, Google Chat, Telegram, Lark / Feishu, Twilio SMS and voice, Pushover and n8n on Starter and Enterprise, and PagerDuty, Opsgenie and Splunk On-Call on Enterprise. Notification lists per account: 1 on Free, 10 on Starter and unlimited on Enterprise.

Environments, such as production and staging, group your monitors, and you switch between them in the dashboard. Environments per account: 2 on Free, 10 on Starter and unlimited on Enterprise. See every channel and its plans on Integrations.

A status page shows the uptime of the monitors you pick and any open incidents, with your logo and brand colour, at its own address from us. Status pages per account: up to 5 on Starter and unlimited on Enterprise.

To serve a page on your own domain, verify the domain in the dashboard with a TXT record, attach it to the page, and point a CNAME record at the target the dashboard shows. The page goes live on your domain once our team has confirmed the CNAME record.

Routing rules decide which notification lists receive an alert. A rule matches on any mix of monitor type, check type, environment, tags, monitor group, severity and schedule (days and hours in a time zone you choose), and sends to one or more lists. Rules run in priority order, lowest number first, and a rule set to stop processing keeps the rules after it from running.

"Where would this alert go?" in the dashboard shows which of your rules a sample alert matches and which lists it reaches. If no rule matches, the monitor's own notification list is alerted, or your default list when the monitor has none.

After an alert, an automation rule can call a webhook, start an n8n workflow, post an update to a status page or create a ticket. A run can wait for approval, retries with backoff when the target fails, and keeps an audit trail. Before a rule is enabled it can be dry-run: the dry run checks the rule and its target and shows what it would send, without sending anything.

There is no automation screen in the dashboard yet: our team sets up your automation rules and handles run approvals with you, on request.

Create an organization and invite people by email. Each member has one of 5 roles: owner, admin, billing, member and viewer. Owners and admins invite and manage members and teams, the billing role manages billing, and viewers have read-only access. There is no per-seat pricing. Monitors, notification lists and API keys belong to the person who created them.

Everyone can turn on two-factor sign-in with an authenticator app (TOTP) in Settings → Account, with single-use backup codes, and can sign in with Google or GitHub.

API keys authenticate the telemetry API. In Settings → API, create a key with the Telemetry purpose (the monitor:telemetry and monitor:write scopes), or choose Custom and pick from monitor:telemetry, monitor:read, monitor:write, issue:read and issue:write. You can limit a key to certain monitors and give it an expiry date. A key is shown once and stored only as a hash, and it can never report for another account's monitors.

Coding agents use separate MCP tokens, created in Settings → AI agents & MCP (see Agent plugins and MCP).