The infrastructure work nobody was hired to do. Mapped, watched, and kept honest by agents.
Join the waitlistOne graph, every provider. Not a diagram you maintain: a graph that syncs itself.
checkout-edge Issue hotspot: 4 issues in the last 7 days
Change hotspot: 12 changes in the last 7 days
hd-prod Change hotspot: 7 changes in the last 7 days
ingest-events Issue hotspot: 2 issues in the last 7 days
payments-db Issue hotspot: 1 issue in the last 7 days
Change hotspot: 3 changes in the last 7 days
Every change goes on the record. Twelve minutes before the regression, someone touched the queue.
SQS visibility timeout lowered on checkout-events
VisibilityTimeout on checkout-events dropped from 120s to 15s. Consumers that hold a message longer than 15 seconds will see it delivered twice; the dead-letter queue threshold is unchanged.
SetQueueAttributes CloudTrail · deploy-bot · 12:41:02Z attached to this record's delta window The quiet parts, watched. The stalled cron, the growing backlog, the worker that stopped.
reconcile-orders stopped running
- runs/day 4 → 0: no successful run since Tue 02:00 UTC
- last attempt exited with code 137 after 91s (Tue 02:01)
- peak memory on the final run was 2.4× the previous seven-day average
Orders placed since Tuesday have no reconciliation record. The finance export and the daily revenue report both read from the table this job writes.
- 1. Read the logs from the last attempt on reconcile-orders
- 2. Check for memory limit or plan changes on the service in the change records
- 3. Confirm the schedule still exists in render.yaml on main
How Polylane works. It learns your system, watches it, investigates, and acts.
-
It learns your system first
The context graph maps every resource and dependency across your clouds, repos, and observability providers. Agents reason over real topology, not guesses.
-
Detection without thresholds
Built-in checks for every provider, plus checks generated from your own saved queries and dashboards. A statistical pass and an agent decide together, and an improvement never raises an issue.
-
Investigations that show receipts
Every claim links back to the query, log line, or change record behind it. A verdict without evidence falls back to inconclusive.
-
Writes are earned, never assumed
Accounts connect read-only. Rollbacks are off by default, rate-limited, and on the record. Code changes go through your normal review.
-
It gets sharper every week
Memories, daily notes, and monitoring queries re-confirmed against real data: July's investigation learns from June's.
It plugs into what you already run. Connect read-only and start.
AWS 
Cloudflare 
Vercel 
Render 
Fly.io 
Kubernetes PlanetScale 
Supabase 
Modal 
GitHub 
Slack 
Datadog 
Honeycomb 
Axiom 
Sentry 
Better Stack 
Devin 
Cursor 
Factory 
MCP Server Questions.
Which providers does Polylane support today?
AWS, Cloudflare, Vercel, Render, Fly.io, Kubernetes, PlanetScale, Supabase, and Modal, plus GitHub for code and Datadog, Honeycomb, Axiom, and Sentry for telemetry. The integrations page tracks the full catalogue, including what's coming next.
How does it link resources across clouds?
The way traffic actually flows: hostnames, DNS records, and IP addresses matched across providers, environment variables that reveal dependencies, traces where you have them, and infrastructure-as-code that declares what deploys where.
Do I need to tag resources or draw the topology?
No. Connect each account read-only and the graph builds and maintains itself. You can correct or annotate anything, and agents keep it fresh with every sync.
How much access does each cloud need?
The minimum, read-only by default: AWS through a scoped CloudFormation role, Cloudflare through pre-filled token permissions, and equivalents everywhere else. Write access is a separate, per-account decision.
Which background systems does it watch?
Whatever your providers run: SQS queues and scheduled jobs on AWS, Cloudflare Queues, Render background workers and cron jobs, Kubernetes CronJobs, Fly.io machines. If it's in a connected account, it's in the graph.