PlatformPilot
Infrastructure Intelligence

Your infrastructure,
fully understood.

The live data layer for your infrastructure — every service, resource, and dependency, with full history. Your engineers and AI agents finally reason from the same ground truth.

Try the live demo →Get early access →
●Self-hosted · read-only · zero data leaves your infra
The Problem

Your infrastructure exists in three places.
They disagree.

What you declared, what's actually running, and how it behaves are three different stories — and no tool you have today reads all three.

DECLARED
Terraform · Pulumi · CDK
aws_security_group.payments_db
ingress[5432] from sg-eks-nodes

What you intended. Reviewed, versioned, approved.

ACTUAL
AWS · GCP · Azure
sg-payments-db · live
ingress[5432] from 0.0.0.0/0

What's actually running — after every console click, hotfix, and "temporary" change.

BEHAVIORAL
Traces · metrics · logs
catalog → legacy-pricing · 255 rps
legacy-pricing: in neither plane, unowned

What traffic actually does — including services nobody declared anywhere.

Every incident, surprise bill, and 3am page lives in the gaps between them.

The knowledge to close those gaps lives in your senior engineers' heads — and now AI agents are making infrastructure decisions without it.

From signals to answers

One pipeline. No new agents
in your request path.

PlatformPilot reads what your infrastructure already emits. Nothing is instrumented, injected, or intercepted at runtime.

SOURCES01
Everything you already run
  • ·Terraform / OpenTofu state
  • ·AWS, GCP, Azure APIs
  • ·OpenTelemetry traces
  • ·VPC flow logs, CloudTrail
›
MODEL02
Reconciled into one model
  • ·Intent reconciled with reality
  • ·Services joined to what runs them
  • ·Every join confidence-scored
  • ·Versioned as it changes
›
SIGNALS03
What falls out of the join
  • ·Drift, ghosts, shadow services
  • ·Blast radius and failure modes
  • ·Cost, ownership, exposure
  • ·Environment divergence
›
ANSWERS04
Delivered where you work
  • ·Terminal and pull requests
  • ·The map and the timeline
  • ·Plain-language questions
  • ·Your AI agents, over MCP
The Model

One living model.
Every answer built on it.

PlatformPilot reconciles all three planes into one live model of your estate — your services joined to the infrastructure they run on — and keeps it current as everything changes. There are no features here in the usual sense: every capability is a question asked of the same model.

app.platformpilot.co/overview▸ walkthrough
Overview
Resources
34
Services
27
Active drift
2
Monthly spend
$9,244
SEV-2 · ACTIVEpayments-service breaching SLO
p99 812ms against a 250ms target. Security group drift at 14:02, health degraded at 14:04 — the model already links the two.
Latest events
14:06●SEV-2 routed to payments-team
14:04●payments-service p99 breached SLO
14:02●sg-payments-db drifted from declared state
13:40●PR #481 applied — catalog search index tuning
Ask Pilotgrounded in the model
Ask anything about your infrastructure…
anything you want to know about this estate
Ask Pilot

Talk to your infrastructure.

Health, blast radius, drift, and the reasoning behind why things are wired the way they are — each answer carrying its source, confidence, and freshness.

pilot ask — acme-prod● live
Ask anything about your infrastructure…
Not a chatbot over your docs — every claim resolves to a node, an edge, or a recorded event in the model.

Questions you can now answer.

Pick any one — it runs in the terminal above.

Before you change
While it runs
When you ask
AI Context Layer · MCP

Your agents are about to touch prod.
Give them ground truth.

Coding agents already write your Terraform. Soon they'll operate your infrastructure. PlatformPilot is the context layer that grounds them in what's actually running — over MCP, from your own deployment.

Scoped retrieval, never whole-model dumps

Agents get the minimal relevant slice of the model for their question — typed MCP tools like blast_radius, simulate_failure, and query_history.

Every fact carries its receipts

Source, confidence, and last-seen timestamp on everything returned. An inferred dependency is labeled inferred — agents can't mistake a guess for ground truth.

Same interface your team uses

The Ask feature and the MCP server are one interface. What your engineers see is exactly what your agents see.

◆your coding agentmcp: platformpilot ● connected
Can I safely delete the staging NAT gateway?
⚙ platformpilot.blast_radius(resource: "nat-gw-staging")
⚙ platformpilot.simulate_failure(node: "nat-gw-staging")
No. Three services route egress through it:
● staging-ci — hard-fails observed
● etl-worker — degrades inferred · 0.81
● web-staging — unaffected, alternate path redundant
source: the model · cloud synced 2 min ago · simulation ran on live snapshot, nothing touched
Security & safety

PlatformPilot only ever reads.
There is no write path to disable.

Most tools ask you to trust their judgement before they act on your behalf. This one has no mechanism to act at all — it reads what your infrastructure already emits, models it, and answers.

What it do
Read-only. Always.

No write permissions to your cloud, and none to your repositories. PlatformPilot observes, models, and answers — you apply.

Runs in your environment

Docker Compose, Helm, or a Terraform module, inside your own network. Air-gapped deployment supported.

Your model, your key

Anthropic, OpenAI, or any compatible endpoint. Requests go from your deployment to your provider — never through us.

What it reads — nothing new to install
Declared
TerraformOpenTofuPulumiCDK
Actual
AWSGCPAzureKubernetes
Behavioral
OpenTelemetryDatadogPrometheusCloudWatch
Delivery
GitHubSlackPagerDutyMCP

Read-only credentials against sources you already run. PlatformPilot replaces none of your tooling — it connects the planes your existing tools each see one of. No runtime agent, no sidecar, nothing in your request path.

Contact

Let's talk
infrastructure.

Pick whichever is easiest — a direct email, a call, or the form below. No sales funnel, no drip sequence.

Email
prabhakaran@platformpilot.co

Straight to the person building it. Replies within one business day.

Book 30 minutes
Walkthrough or review →

A live look at the model against a real estate, or a session with your security team on the deployment model.

Try it first
Launch the live demo →

A full e-commerce estate you can click through — follow a live incident down to the change that caused it. No signup.

Goes straight to a person. No autoresponder, no mailing list.
What happens next
01One of us reads it — not a queue, not a bot.
02A reply within one business day, from a real address.
03If it is a fit, a 30-minute walkthrough against your own questions.
04No drip sequence and no follow-up cadence. Ever.
Before you ask — yes, it is safe

PlatformPilot is self-hosted and read-only. It runs in your environment with your own credentials, holds no write permission to your cloud or your repos, and sends nothing outbound except to your own providers.