Dashboard

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
or

Early access currently rolling out.

Polylane finds issues in your app and fixes them for you, automatically.

It learns everything you run. Every cloud, every repo, every dependency: one live graph.

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

It never stops looking for problems. Issues surface on their own, including the ones nobody thought to alert on.

Issues Critical latency degradation in checkout-edge worker Overview

Critical latency degradation in checkout-edge worker

Incident critical Polylane ·Detected 3 hours ago ·Last seen 4 minutes ago ·2 occurrences
OverviewInvestigationMetricsTimelineProperties
checkout-edge › Cloudflare Worker

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

Causal metrics All metrics
Request Duration
414 ms ▲ 43.1σ
Wall Time
416 ms ▲ 43.0σ
CPU Time
14 ms ▲ 2.6σ
Blast radius
Search your cloud resources...
Graph Table
edge-gateway Cloudflare Worker ··· checkout-edge Cloudflare Worker ··· hd-prod Hyperdrive ··· payments-db PlanetScale ··· cart-svc Cloudflare Worker ···
Analysis Copy

Deploy 9f3c2a1 shrank the Hyperdrive pool hd-prod from 50 connections to 5. Under checkout load, requests queue on connection checkout and P99 rises 18× against the 30-minute baseline. Restoring the pool size restores latency.

Tags
service · checkout-edgeprovider · cloudflaredeploy · 9f3c2a1signal · wall_time_p99

It listens to every alert you already have. Every alert triaged, the real ones investigated and fixed.

Issues

Issues

Problems detected by Polylane and alerts from your monitoring tools, triaged automatically.

IncidentsNo incidentAll Search issues... Filter
Title Detected by Status
Critical latency degradation in checkout-edge worker Polylane Incident
checkout-edge P99 latency above 2s for 5m Datadog Incident
TypeError: cannot read 'region' of undefined in checkout handler Sentry Triaging
edge-gateway 5xx ratio above 1% for 5m Grafana Cloud No incident
orders-db CPUUtilization above 80% CloudWatch No incident
payments-api webhook retry queue depth above 5,000 Datadog Resolved

It fixes problems, not symptoms. It finds the root cause of every issue it detects and submits PRs to fix.

github.com/coreplane/payments-api/pull/491

Cap retries on the checkout webhook worker #491

polylane
Open polylane wants to merge 1 commit into main from polylane/autofix/chat/k3x9f2-4e7d21a
Conversation 1 Commits 1 Checks 1 Files changed 2
polylane bot commented 6 minutes ago ···

Retries on the checkout webhook worker were unbounded: a failing delivery re-queued itself forever and amplified load on payments-api. This caps delivery at 5 attempts with exponential backoff and dead-letters the payload after the last one.

What changed

worker/deliver.ts gains MAX_DELIVERY_ATTEMPTS = 5 and backoff between attempts; exhausted payloads land in checkout-webhooks-dlq instead of re-queueing.

Validation

npm test — 214 passed. A forced failing delivery stopped after 5 attempts and appeared in the dead-letter queue.

Root cause · Why it's safe · Out of scope
polylane added commit 4e7d21a Verified
Review required At least 1 approving review is required
ci / test Successful in 3m 12s Details
Review required Waiting on your review: Polylane never merges on its own
Merging is blocked

It answers the questions on-call gets. Who owns this, what changed, is it us: replied in the thread, with receipts.

# incidents
Messages Add canvas Files & links
Polylane Agent 2:14 AM

Critical latency regression on checkout-edge: Wall Time P99 is 18× baseline, sustained since 2:02 AM, and checkout requests are queuing. I'm investigating.

boris 2:15 AM

probably the Hyperdrive change in tonight's deploy?

👀 1
Polylane Agent 2:16 AM

Working on it

  • ✓ Pulled the last 30 minutes of checkout-edge metrics
  • ✓ Correlated with the change records
  • ◐ Testing the Hyperdrive pool hypothesis
  • ○ Draft the fix

status as of 2:17 AM UTC

Polylane Agent 2:19 AM

You're right. Deploy 9f3c2a1 shrank the hd-prod connection pool from 50 to 5, and checkout requests queue behind connections. Confirmed against the pool metrics and the change record. Fix is drafted, coreplane/checkout-edge#142 restores the pool. CI is running; I'll report back here.

Open in Polylane Configure

It brings production into your terminal. Your coding agent sees what's running before it changes anything.

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…

It remembers every incident. The next one never starts from zero.

Settings Memories

Memories

Institutional knowledge from investigations and observations.

All Mine Search memories... Filter 7 memories
Name Source Created
hd-prod must keep 50 connections: at 5, checkout-edge requests queue and P99 rises 18x Investigation 3 hours ago
Deploys that touch checkout-edge's Hyperdrive binding need the pool size checked in review Change analysis 3 hours ago
cart-svc and edge-gateway still send region-less checkout requests; region stays optional until they migrate Investigation yesterday
payments-api webhook retries are capped at 5 with backoff since #491; dead-letters land in checkout-webhooks-dlq Automation 2 days ago
payments-db connection spikes follow cart-svc retries, not checkout traffic Observation 6 days ago
checkout-edge P99 sits at 1.4-1.8s on weekday evenings; the Sunday 02:00 UTC bump is the analytics backfill Observation 2 weeks ago
edge-gateway returns 502 for 40s after every deploy while its Fly machines drain; not an incident Change analysis 3 weeks ago

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

AWS Cloudflare Vercel Fly.io Render Kubernetes PlanetScale Supabase Modal Railway Convex Datadog Sentry Honeycomb Axiom Grafana Cloud GitHub Slack Cursor Devin Factory MCP And more →

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

Cloudflare Cloudflare Webflow Webflow Groq Groq Twilio Twilio Uber Uber Robinhood Robinhood
“I spent years building observability platforms, at Baselime and then at Cloudflare. Our tooling is still terrible at finding what's broken, and it can't fix anything on its own. On-call is still broken. I'm fixing it.”
Boris Tane
Boris Tane
Founder

We're making software operate itself. Join us.

Trust is non-negotiable.

AICPA SOC 2

SOC 2 Type II

Independently audited security controls.

ISO 27001

ISO 27001:2022

The international standard for information security management.

End-to-end encryption

AES-256 at rest, TLS 1.2+ in transit.

Data isolation

Fully isolated per organization.

View trust center

Questions.

What is Polylane?

Polylane makes your software self-operating. AI agents learn everything you run, watch production for issues, triage every alert you already have, fix what they can, answer the questions on-call gets, give your coding agent the same production context, and remember every incident.

How does Polylane detect issues?

Agents read the actual metric, log, and trace series and judge them against how each resource normally behaves. 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, PlanetScale, Supabase, and Modal, plus GitHub, Slack, and your observability tools: Datadog, Honeycomb, Axiom, Grafana Cloud, 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.