Private Agents
Run pipelines in your network.
Install a Private Agent on your Linux host to reach the source and destination. It connects outbound to PipePilot while batch records and runtime credentials stay in your runtime during execution.
Core capabilities
Customer network
Place the Agent where approved routes can reach both endpoints.
Outbound control
Enrollment, health, jobs and aggregate progress use outbound control-plane communication.
Host evidence
CPU, memory, disk and runtime measurements help administrators review current capacity.
Workflow
01Enroll, verify and assign.
Install and enroll the Agent, verify its health, then select it on both compatible connections. A Private Agent does not bridge to managed Compute.
Linux installation packages
Workspace-scoped enrollment
Same Agent for both endpoints
Separate runtimes when Agents share a host
Configuration and runtime evidence stay attached to the workflow.
Workflow
02Connect a private database to a public warehouse.
The Agent reads the private source and writes to the public destination from your host. The public destination does not move execution to PipePilot infrastructure.
Credentials loaded only for the job
Aggregate status and checkpoints returned
Customer-managed host capacity
Updates drain affected work first
Configuration and runtime evidence stay attached to the workflow.
Next step
Plan your data workflow.
Share your source, destination and network needs. We will confirm the supported workflow and prerequisites.