Dashboard

Production stopped fitting in anyone's head. Polylane holds all of it: clouds, code, and telemetry in one live graph.

Join the waitlist
Topology
Search your cloud resources...
Galaxy
checkout-edge Worker
Critical Critical to your architecture.

Issue hotspot: 4 issues in the last 7 days

Change hotspot: 12 changes in the last 7 days

Cloudflare · coreplane · earth · Compute
hd-prod Hyperdrive
Critical Critical to your architecture.

Change hotspot: 7 changes in the last 7 days

Cloudflare · coreplane · earth · Databases
ingest-events Lambda function
Standard Important to your architecture.

Issue hotspot: 2 issues in the last 7 days

AWS · coreplane-prod · us-east-1 · Compute
payments-db Database
Critical Critical to your architecture.

Issue hotspot: 1 issue in the last 7 days

Change hotspot: 3 changes in the last 7 days

PlanetScale · coreplane · us-east · Databases

Agents are as good as their context. Here's how Polylane learns yours.

  • Your whole cloud, read-only

    AWS through a read-only role, most providers with an API token. Every resource joins the graph, and it stays fresh on its own.

  • Linked across providers

    Hostnames, DNS records, and IPs connect the clouds: a Cloudflare CNAME pointing at a Render service. The real request path, not the diagram from two years ago.

  • The important stuff, watched harder

    Every resource gets a tier, from critical to minimal, worked out daily from traffic and what depends on it. Override any of it.

  • It writes things down

    Each resource keeps a wiki that rewrites itself as your system drifts, and agents leave notes: July's investigation learns from June's.

CLI or MCP, your choice. Your coding agent connects whichever way you want.

The CLI wires it.

One install connects your stack and registers Polylane in every coding agent on your machine.

Model Context Protocol

MCP serves it.

Your clouds, telemetry, deploys, and code behind one MCP server. Reads by default; writes sit behind a default-deny policy.

In the tool you already use. Every agent reads the same graph.

Claude Code
Cursor
GitHub Copilot
Codex
Gemini CLI
VS Code
Zed
OpenCode

Code mode. One round trip, just the answer.

Instead of calling tools one by one, your agent writes TypeScript against the MCP's tools namespace and the server runs it. Intermediate results never touch the context window; only the answer comes back.

polylane · runCode
// Which deploy slowed checkout-edge?
const deploys = await tools.deployHistory({ service: "checkout-edge", hours: 24 });
const { points } = await tools.queryMetrics({
  service: "checkout-edge",
  metric: "latency.p99",
  hours: 24,
});

const median = (xs) => xs.sort((a, b) => a - b)[xs.length >> 1] ?? 0;
const p99 = (t, side) =>
  median(points.filter((p) => (side < 0 ? p.t < t : p.t > t)).map((p) => p.v));

// Score every deploy by the p99 shift across its timestamp.
const [worst] = deploys
  .map((d) => ({ ...d, shift: p99(d.at, 1) / p99(d.at, -1) }))
  .sort((a, b) => b.shift - a.shift);

// Pull the error logs right after the suspect deploy.
const errors = await tools.queryLogs({
  service: "checkout-edge",
  level: "error",
  after: worst.at,
  limit: 5,
});

// Only this returns; the series and logs stay in the sandbox.
return {
  deploy: worst.sha, // 9f3c2a1
  p99Shift: worst.shift, // 4.8
  topError: errors[0]?.message, // "Hyperdrive pool exhausted"
};

one answer back; twenty round trips saved

Connect your cloud. Polylane learns every corner of it before anything breaks.