The agent in your networkpreview

• preview

  Checks where your systems are

  HTTP (status, latency, certificate expiry), TCP, TLS and gRPC health, for monitors and for checks run on demand. Hosts outside your verified domains are refused before a job is sent.

• preview

  It only dials out

  One WebSocket to the platform's API host, kept open; nothing listens on your side, so there is no inbound firewall rule to ask for. When the connection drops, work stops.

• preview

  Declared in one file

  A checks.toml says what it watches; the platform turns each check into a monitor managed by that agent, with its category and tags. It reports its own machine so a devops team sees where and under which rules it runs.

• preview

  A binary a security team can check

  Built from public source in inorbithr/dataplane, every artifact signed keyless at its tag with SLSA provenance and a CycloneDX SBOM. Linux and macOS, amd64 and arm64, a container image and a Helm chart.

• in development

  Reading your system for Atlas

  Observers for Kubernetes, Envoy, cargo, network policy and the host are built and not in a release yet. Load and faults on your side come later and are refused until then.

[[check]]
name = "orders-api"
surface = "http"
target = "https://orders.internal.example/healthz"
every = "30s"
expect = { status = 200, max_ms = 500 }
fail_after = 2
category = "availability"

[[check]]
name = "orders-tls"
surface = "tls"
target = "orders.internal.example"
every = "1h"
expect = { valid_for_days = 14 }

Drawn from the console's own layout. The services, times and numbers are made up for the example.