
ProjectDiscovery Cloud - Agent
What it does • Quick Start • Install • Configuration • Scaling
pd-agent lets you scan your own internal networks from the ProjectDiscovery Cloud Platform.
Install the agent on a machine inside the network you want to scan — a VM, a server, a workstation, a Kubernetes pod — and connect it to your PDCP team. From the cloud UI you can then launch scans against private IPs, internal hostnames, VPC ranges, or Kubernetes clusters, and the agent will run them locally and stream results back. Nothing in your network needs to be exposed publicly.
Nuclei, httpx, naabu, dnsx, and tlsx are all built into the agent — there's nothing else to install on the host.
Get credentials. Sign in at https://cloud.projectdiscovery.io, copy your API key and team ID.
Run the agent on the machine that has access to the network you want to scan:
docker run -d --name pd-agent \
--network host --cap-add NET_RAW --cap-add NET_ADMIN \
-e PDCP_API_KEY=your-api-key \
-e PDCP_TEAM_ID=your-team-id \
ghcr.io/projectdiscovery/pd-agent:latest \
-agent-network prod-vpc
Verify. Open the cloud UI's Agents tab — the agent appears within a few seconds with its discovered subnets.
Scan. Launch a scan from the UI and route it to your agent's network (prod-vpc above). The agent runs it locally and streams results back.
Other install paths (Kubernetes, native binary, systemd, launchd, Windows service) → docs/install.md.
10.0.0.0/8, 192.168.0.0/16, internal DNS, VPN-only services.-agent-network) — e.g. one or more agents per data centre, region, or VPC.| Topic | When to read |
|---|---|
| docs/install.md | First-time install on Linux, macOS, Windows, Docker, or Kubernetes. |
| docs/configuration.md |
Distributed under the MIT License. Built with ❤️ by ProjectDiscovery.
| Every env var and CLI flag the agent accepts, and what they control. |
| docs/scaling.md | When to add more agents and which metric to drive autoscaling from. |