Create a Private Location

A private location runs checks from infrastructure you control. Use it when targets are reachable only on an internal network or when you need a particular network vantage point.

Deploy the agent

1. Open Settings → Private locations in the dashboard.
2. Create a location and give it a recognizable name.
3. Copy its installation instructions and token. The dashboard supplies Docker, Kubernetes, and binary instructions with the supported image or source revision.
4. Deploy the agent on a host that can reach your targets and make outbound HTTPS connections to https://ingest.probed.dev.
5. Preserve the state and spool paths specified by the installation instructions across restarts.
6. Wait for the location to report healthy, then attach monitors to it.

Use the generated commands rather than an upstream container or a floating image tag. Installation environment variables retain names such as OPENSTATUS_KEY; those identifiers are part of the agent interface.

Verify operation

Check that the dashboard shows a recent connection and that an attached monitor produces results from the private location. A running container alone does not prove that checks are reaching Probed.

Treat the location token and local state as sensitive. Restrict access to the host and state directory, and rotate credentials if exposed. No inbound port needs to be opened for Probed to connect to the agent.

Starter supports two private locations; Hobby supports one. The limit is a count of private agents, separate from managed check regions.