Local Monitoring Agents

Why use local agents?

Traditional uptime monitors can only check publicly accessible endpoints. But most production systems include private databases, internal APIs, queue brokers, and cache servers that are invisible from the outside. A local agent bridges that gap, giving you full observability over your entire infrastructure without opening firewall ports or creating VPN tunnels.

Local agents are available on Pro and Scale plans. Scale plans support up to 100 agents for large or distributed environments.

The agent is intentionally simple: no database to manage, no message broker to configure, and no persistent inbound listener for an attacker to find. It authenticates once, runs your configured checks on a schedule, and pushes results out over HTTPS — the same pattern your other outbound-only services already use every day. Because it behaves like any other outbound client on your network, most teams don't need a special firewall exception or a security review beyond what they'd apply to any other software installed on that host.

A single agent typically covers an entire private network, since it can reach any host the network itself allows — there's no need to install one agent per server. Most teams start with one agent per VPC, data center, or Kubernetes cluster, then add more only when a network boundary genuinely separates two environments that need independent visibility. Upgrading an agent later is a matter of replacing the binary — there's no separate migration step for the checks it already runs.