Skip to content
RootPilotRootPilotRootPilot Edge

RootPilot Edge

The open half of RootPilot. The executor that runs on your infrastructure, holds your credentials, and redacts PII before any data leaves. Apache-2.0, auditable line by line.
Get running in 5 minutesView on GitHub
The runner sits inside your infrastructure and opens a single outbound connection to the control-plane. Credentials stay put; only redacted results cross. Boundary Your infrastructure RootPilot Secret manager your credentials Your sources AWS · Datadog · GitHub… runner (the RootPilot Agent) read-only · redacts PII at the edge · ephemeral control-plane composites · judgment

The boundary has exactly one opening, and it points outward: the runner dials the control-plane, never the other way around. Credentials don’t cross. Results do, already redacted.

Where to start

Section titled “Where to start”
5 minutes

Quickstart

Bring up the whole catalog with a planted incident, without a single cloud credential.

 Concept

Overview

What runs on which side of the boundary, and why the split is drawn where it is.

 Production

Install for real

Enrollment, cloud-identity attestation, and the fleet against the production tunnel.

 Reference

Environment variables

All 40 RUNNER_* settings, with defaults and what each one breaks.

 Reference

Connector credentials

Which keys each of the 15 connectors asks for, and which are actually required.

 Posture

Security model

Read-only by construction, the 5 write exceptions, and the human gate covering them.

What this repository does not contain

Section titled “What this repository does not contain”

The diagnostic intelligence (multi-source correlation, learning aggregation, decision thresholds) lives in the control-plane, which is closed. The edge on its own is an auditable API executor, and that is the point: you don’t have to trust RootPilot to check exactly what touches your credentials.