One monitor for everything that can break.
Eight monitor types, one dashboard, alerts wherever you work. Here's what each one watches.
HTTP(S) monitoring
Sends a real request to your URL and checks the response: reachable, expected status code, response time, and — optionally — that a keyword appears in the page body.
Use it for: Websites, landing pages, APIs, and health-check endpoints. Add a keyword like “All systems operational” to catch pages that load but render broken.
Keyword monitoring
Watches page content, not just status codes. Fail the check when a keyword goes missing — or alert the moment an unwanted word (like “error” or “maintenance”) appears.
Use it for: Defaced pages, expired trial banners leaking into production, payment-error strings, or confirming a deploy actually shipped the new copy.
Ping monitoring
Sends ICMP echo requests to your host and measures replies. No reply, no route — you know the machine itself is unreachable, below the application layer.
Use it for: VPS and bare-metal servers, routers, VPN endpoints, and anything where you need to separate “network down” from “app down”.
Port monitoring
Opens a TCP connection to any port on your host, with presets for the usual suspects — HTTP, HTTPS, FTP, SSH, SMTP, DNS, POP3, IMAP — or any custom port.
Use it for: Mail servers on port 25, databases, SSH access, game servers, and internal services that don't speak HTTP.
Heartbeat monitoring
Works in reverse: we give you a unique URL, and your cron job, backup script, or background worker pings it on every run. Silence past your interval (plus a 5-minute grace) means something stopped running.
Use it for: Nightly backups, billing runs, queue workers, scheduled reports — the jobs that fail silently and cost you the most.
SSL certificate monitoring
Inspects your certificate on every check and warns you a configurable number of days before it expires — default 14. An expired cert is a full outage for every visitor.
Use it for: Any HTTPS site. Especially the ones with manual renewals, or certs managed by someone who left the company.
Domain expiry monitoring
Looks up your domain's registration expiry via RDAP and warns you ahead of time — default 30 days. Losing a domain to expiry is the most embarrassing outage there is.
Use it for: Every domain you own, including the defensive registrations and client domains nobody thinks about until they're gone.
DNS monitoring
Resolves A, AAAA, CNAME, MX, TXT, or NS records and compares them against your expected values. Changed, missing, or hijacked records trigger an alert.
Use it for: Catching bad DNS edits, expired DNSSEC issues, MX records drifting after a mail migration, and CDN misconfigurations.
The platform around them
Monitor types are only half the story. This is what turns checks into confidence.
Alerting, your way
Email, webhook, Slack, and Discord contacts — every DOWN, RECOVERED, and expiry-warning alert goes to all of your active contacts. One alert per incident, never a flood.
Incident timeline
Every outage is recorded with start time, end time, and duration. Export your history for post-mortems, client reports, and SLA claims.
Uptime stats & response times
Per-monitor uptime percentages for the last 24 hours, 7 days, and 30 days, plus average response time and a visual check history.
Maintenance windows
Schedule planned work per monitor — or across all monitors — and checks pause while the window is active. Deploy on Friday without the 3 AM pages.
REST API & MCP
Every monitor, check, and incident is available over a documented REST API — or handed to your AI assistant over MCP. Generate keys from your dashboard and automate what the UI can do — create monitors, trigger checks, pull uptime stats.