Give Pilot a GitHub repo and a cloud provider — it writes the Dockerfile, Terraform, Helm chart, and CI/CD pipeline, then monitors and scales your service automatically.
Your strongest engineer is awake at 3:14, copy‑pasting kubectl describe into Slack for the fourth night this week.
Six environments. Four Terraform repos. One Notion doc that was last accurate in March. The config has drifted, and so has the team.
Three unused RDS instances. A NAT gateway from a 2022 spike. Idle GPUs in eu‑west‑3. Finance keeps asking. Nobody knows.
You thinkyou can roll back. You're not sure who has the latest good SHA. The runbook lives in a Notion doc that 404s on mobile.
Pilot owns infrastructure as a first‑class actor. It writes the IaC, picks the cloud, runs the deploy, watches the metrics, fixes what it can, and pages a human only when it really, genuinely, should.
Pilot maps every service, queue, db, and edge node it ships — and keeps the map alive as the topology changes.
Canary, blue/green, or progressive rollout — Pilot picks the strategy and bails out the moment the SLO budget twitches.
Plain English in. Diffs, deploys, and incident commentary out.
Pilot right‑sizes, schedules, and kills the orphaned NAT gateway you forgot.
Detect bad release, halt rollout, revert. No paging, no Slack thread.
No rip‑and‑replace. Pilot reads your existing Terraform, your Helm charts, your GitHub Actions, and your runbooks — and just gets to work.
+ 80 more · open MCP & REST APIs · BYO tools via shell wrapper
One pilot init. It reads your code, your existing IaC, your env. No magic — it tells you exactly what it plans to take over.
Pilot drafts the IaC, the pipeline, the dashboards, the alerts. You diff it, comment, merge. Then it ships, end to end.
Pilot deploys, watches, scales, patches, rotates secrets, and writes the postmortem. You sleep through the on‑call rotation you used to dread.
// ALL THREE STEPS, FIRST DEPLOY, UNDER 11 MINUTES MEDIAN
Read the technical brief16 Claude Code commands that run directly in your editor. Infra ops without leaving your terminal.
Pilot operates with least‑privilege roles, dry‑runs every change, and asks for a human signature on anything that touches money, identity, or data.
Least privilege, audit log on every action, dry‑runs on every change, human approval on every blast radius.
Approvals routed by policy. Pilot waits patiently. Everything else, it just ships.
Append‑only audit log, exportable to your SIEM. Ask Pilot anything about its own behaviour.
Pilot rotates, distributes and revokes — auto, on schedule, on compromise.
Your cloud, your account, your data. Pilot's control plane never touches it.
OPA‑native. Encode “Pilot may never…” once, enforce it everywhere.
Hover any question to peek the answer. Click to keep it pinned open.
Eleven minutes from pilot init to your first autonomous deploy. No card. No sales call. No yak shaving.