Nobody should be on-call in 2026.

Agents that read your code, watch your infra, and fix production before you wake up.

Join the waitlist

· Early access currently rolling out.

Context. Every cloud, every repo, every dependency: one live graph.

Topology

Search your cloud resources...

1,320 resources

Galaxy Graph Table

cloudflare

checkout-edge

Critical Critical to your architecture.

Issue hotspot: 4 issues in the last 7 days

Change hotspot: 12 changes in the last 7 days

coreplane · earth · Worker · Compute

cloudflare

hd-prod

Critical Critical to your architecture.

Change hotspot: 7 changes in the last 7 days

coreplane · earth · Hyperdrive · Databases

AWS

ingest-events

Standard Important to your architecture.

Issue hotspot: 2 issues in the last 7 days

coreplane-prod · us-east-1 · Lambda function · Compute

planetscale

payments-db

Critical Critical to your architecture.

Issue hotspot: 1 issue in the last 7 days

Change hotspot: 3 changes in the last 7 days

coreplane · us-east · Database · Databases

Prevention. Agents catch the incident while it's still a pull request.

github.com/coreplane/orders-api/pull/482

Add trigram index for order search #482

Open rvidal wants to merge 1 commit into main from order-search-trgm

Conversation 1 Commits 1 Checks 2 Files changed 1

polylane bot commented 2 minutes ago ···

Caution

Merging this pull request may degrade production (high impact).

Merging this blocks every write to orders while the index builds. migrations/0114_order_search_trgm.sql:3 adds CREATE INDEX … USING gin (search_text gin_trgm_ops) without CONCURRENTLY, and a plain CREATE INDEX takes a full write lock on orders for the whole build. Checkout sustains ~38 writes/s on that table; each one queues behind the lock until the build finishes.

To make this safe: build the index with CREATE INDEX CONCURRENTLY outside the transactional migration.

orders-db · writes per second · last 48h projected lock window

02040

-48h -24h now

every one of these writes blocks while the index builds

Polylane analysed de91b47 for production impact.

Some checks were not successful 1 failing and 1 successful check

ci / test Successful in 2m 4s Details

Polylane production impact Non-concurrent index build locks writes on orders Details

Merging is blocked

Detection. Agents find issues in production before your users do.

Issues Critical latency degradation in checkout-edge worker Overview

Critical latency degradation in checkout-edge worker

Critical Active ·Detected 3 hours ago

OverviewMetricsLogsTracesTimelineProperties

checkout-edge

Cloudflare Worker

Open

View triggering check View incident

Critical latency degradation detected in checkout-edge worker: 18x+ P99 latency spikes sustained for 12 minutes

Request Duration

414 ms ▲ 43.1σ

Wall Time

416 ms ▲ 43.0σ

Request Duration

131 ms ▲ 2.6σ

Blast radius

Search your cloud resources...

5 resources

Graph Table

edge-gateway Cloudflare Worker ···

checkout-edge Cloudflare Worker ···

hd-prod Hyperdrive ···

payments-db PlanetScale ···

cart-svc Cloudflare Worker ···

Investigation. Agents find the root cause and prove it.

Threads Critical latency degradation in checkout-edge worker Share

What I did

I queued an autofix that restores the Hyperdrive pool hd-prod in the coreplane/checkout-edge repo with:

max_connections restored from 5 to 50 on the pool binding
a regression test that fails when checkout queues on the pool
wrangler.jsonc configured to deploy as checkout-edge

This gives Boris a PR with deployable code. Once merged, running wrangler deploy will replace the degraded worker with the fixed version.

The root cause report has been updated with the occurrence #2 evidence: Root Cause: checkout-edge Latency Degradation (Recurring).

Wall Time

checkout-edge worker · last hour

Export chart

Wall Time P99

28,381ms

Wall Time P95

2,696ms

Wall Time P50

118ms

010k20k30k

18:0018:2519:00

Worked for 4m 12s

AI can make mistakes. Please double check cited sources.

Dig deeper...

Remediation. Agents end the incident. The permanent fix follows.

Autofixes Restore Hyperdrive pool size in checkout-edge Overview

Restore Hyperdrive pool size in checkout-edge

PR open ·

coreplane/checkout-edge · Incident · Cursor ·Started 12 min ago

OverviewTimelineProperties

View pull request View in Cursor

Repository: coreplane/checkout-edge
Executor: Cursor
Triggered by: Incident View incident
Pull request: #142
Branch: cursor/polylane-autofix-restore-hyperdrive-pool-size-on-che…

Prompt Copy prompt

Goal

Stop the P99 latency regression on Cloudflare Worker checkout-edge by restoring the Hyperdrive pool max_connections to 50 and adding a regression test for pool saturation.

Root cause (confirmed)

Deploy 9f3c2a1 reduced max_connections on hd-prod from 50 to 5 (line 24 of wrangler.jsonc). Under checkout load, requests queue on the pool: Wall Time P99 reached 28,381 ms (~28s) against a baseline of ~1.6s. Rolling the pool size back resolves the regression; the deploy's other changes are unaffected.

Production context in your terminal. Your coding agent stops guessing what's in production.

One endpoint.: Browser sign-in, OAuth handled for you.
Everything Polylane's own agents use.: The context graph, telemetry queries, deploys, code search.
Reads by default.: Writes sit behind a default-deny policy; merging stays human.

Claude Code

Cursor

Codex

OpenCode

VS Code

claude — ~/checkout-edge

> make region a required field on the checkout request schema

●polylane · searchcallers of POST /checkout

●polylane · runToolqueryLogs · request shapes

⏺ Hold on: cart-svc and edge-gateway still send region-less requests, 41,200 in the last 24h. Requiring it now would 400 them both. Safer: default it, migrate the two callers, then require. Are you okay with this plan?

Waiting for your reply…

No migration. No new stack. Polylane plugs into what you already run.

Doesn't repeat the same mistakes. Every incident it sees makes it sharper.

The fastest debugger on any team is the one who's seen the incident before. Polylane remembers what broke, what fixed it, and what normal looks like. The knowledge that usually leaves with your best engineer stays in the workspace.

Built by engineers who carried the pager. From Cloudflare, Webflow, Groq, and Twilio.

Cloudflare Webflow

Webflow

Groq

Twilio

We're making software operate itself. Join us.

Questions.

Polylane makes your software self-operating. AI agents watch your production systems, detect issues, investigate them with your real tools, and fix them.

What is Polylane?

Polylane makes your software self-operating. AI agents watch your production systems, detect issues, investigate them with your real tools, and fix them.

How does Polylane detect issues?

Agents read the actual metric, log, and trace series and decide the way an engineer would. Anything your team already charts becomes a check; thresholds exist where they're the right tool.

Does Polylane change production without review?

No, unless you've explicitly allowed it. Rollbacks are off by default and scoped to the services you choose. Code changes never skip review: fixes arrive as pull requests, and your review and CI gate every merge.

What does Polylane work with?

AWS, Cloudflare, Vercel, Fly.io, Render, Kubernetes, and PlanetScale, plus GitHub, Slack, and your observability tools: Datadog, Honeycomb, Axiom, and Sentry.

When can I use Polylane?

Polylane is pre-launch. Early access is rolling out now, through the waitlist on this page.

Can AI agents use Polylane?

Yes. The platform ships a REST API at api.polylane.com (OpenAPI spec at api.polylane.com/v1/doc) and an MCP server at mcp.polylane.com/mcp with OAuth 2.0 dynamic client registration; see polylane.com/auth.md. Site content is machine-readable at polylane.com/llms.txt.