PRIVATE AGENTS — BETA

Monitor what the internet can't reach

Deploy a lightweight OKStatus agent inside your own network and monitor databases, intranets, VPN-only services and anything behind your firewall — with the same dashboard, alerts and status pages as your public monitors.

PRIVATE NETWORK — LIVE
🔒 pg-cluster.internal:5432 agent: dc-paris-rack2 UP2ms
🔒 vault.corp.local agent: dc-paris-rack2 UP4ms
🔒 10.0.4.12 (NAS backup) agent: office-nuc SLOW890ms
🔒 gitlab.intranet:443 agent: office-nuc UP11ms

Up and running in three steps

01

Deploy the agent

One Docker command, a Helm chart, or a single Linux binary with systemd — pick what fits your infrastructure.

02

Enroll with a token

The agent enrolls itself with a one-time token generated from your dashboard, then appears as a private region only your organization can use.

03

Monitor private targets

Create monitors on internal IPs and hostnames and pick the 🔒 private region — checks run from inside your network, results and alerts flow like any other monitor.

Built for private infrastructure

Private IPs, allowed

10.x, 192.168.x, .internal, .local — targets our public probes rightly refuse are exactly what your own agent is for.

Egress-only, org-scoped

The agent only makes outbound HTTPS connections to OKStatus — no inbound ports to open — and only ever receives your own organization's checks.

As many agents as you need

Run one per site, per datacenter or per rack. Each agent reports its identity, version and last-seen status on your dashboard, with rotation and suspension built in.

Three ways to install

The agent is a single lightweight Rust binary — pick the packaging that matches your stack.

★ Docker ★ Helm / Kubernetes ★ Linux binary + systemd