Docs

Status Harbor Docs

Status Harbor watches services behind a firewall. The Lighthouse agent runs inside your network, opens only outbound HTTPS, and probes internal APIs, private databases and Kubernetes services from where they actually live. No VPN, no inbound ports.

The same product also monitors public endpoints from regional probes — HTTP, TCP, UDP, SSL or DNS — with one shared dashboard and incident pipeline. Alerts go to Slack, Telegram or email. Webhook and WhatsApp are on the roadmap.

Start here

• Quickstart — your first monitor in under a minute.
• Monitors — HTTP, TCP, UDP, SSL and DNS checks.
• Cron checks — heartbeat monitoring for scheduled jobs.
• Notifications — Slack, Telegram and email.
• Lighthouse — monitor private-network services.
• Terraform provider — manage Lighthouses as code.

How it works

The dashboard at console.statusharbor.io runs the control plane: monitors, schedules, incident state, alerts.

Public monitors run from Status Harbor's regional probes (US, EU, APAC and more — see Regions). Lighthouse-bound monitors run from your agent. Both feed the same incident pipeline: a single failure opens an incident, a single success resolves it.