Private infrastructure

Private probe agent

Monitor internal APIs and TCP services without exposing them to the public internet.

Back to services

Agent health

Connected installations

Loading

How it stays safe

Outbound only

The agent opens no inbound port.

Minimal data

Only successful heartbeat timestamps leave your network.

Local configuration

Private targets and credentials remain on your infrastructure.

Setup

  1. Choose a non-secret agent ID for this installation.
  2. Add one Heartbeat check for each private target.
  3. Click Connect private probe, name the installation, then paste both copied credential fields into that target in config.json.
  4. Download or clone the private-agent folder from the Calmping repository.
  5. Build the Docker image and mount config.json read-only.
  6. Keep the agent interval shorter than the Calmping heartbeat interval.

Supported in the MVP

HTTP/HTTPS health endpoints and TCP connectivity for PostgreSQL, MySQL, Redis, MongoDB, SMTP, and other internal services.

Structured heartbeats include agent identity, version and one-time event IDs. Duplicate and stale events are rejected. Separate signing credentials use one-time, expiring enrollment and can be rotated independently from other checks. Protocol-level database queries and Docker socket access remain outside this release.