Dashboard

Ingen bør være on-call i 2026.

Agenter, der læser din kode, holder øje med din infrastruktur og retter produktion, før du vågner.

Skriv dig på ventelisten
eller

Early access rulles ud lige nu.

Polylane finder issues i din app og retter dem for dig, automatisk.

Den lærer alt, du kører. Hver cloud, hvert repository, hver afhængighed: én levende graf.

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

Den holder aldrig op med at lede efter problemer. Issues dukker op af sig selv, også dem ingen tænkte på at sætte alarmer på.

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

Den lytter til hver alarm, du allerede har. Hver alarm triageret, de rigtige undersøgt og rettet.

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

Den retter problemer, ikke symptomer. Den finder rodårsagen til hvert issue, den opdager, og indsender PR'er, der retter det.

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

Den svarer på de spørgsmål, on-call får. Hvem ejer det her, hvad blev ændret, er det os: besvaret i tråden, med beviser.

# 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

Den bringer produktion ind i din terminal. Din kodeagent ser, hvad der kører, før den ændrer noget.

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…

Den husker hver hændelse. Den næste starter aldrig fra nul.

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 Change analysis 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

Ingen migrering. Ingen nye SDK'er. Polylane kobler sig på det, du allerede kører.

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

Bygget af engineers, der har haft pageren. Fra Cloudflare, Webflow, Groq, Twilio, Uber og Robinhood.

Cloudflare Cloudflare Webflow Webflow Groq Groq Twilio Twilio Uber Uber Robinhood Robinhood
"Jeg brugte år på at bygge observability-platforme, hos Baselime og derefter hos Cloudflare. Vores værktøjer er stadig elendige til at finde det, der er i stykker, og de kan ikke rette noget på egen hånd. On-call er stadig i stykker. Det er jeg ved at rette."
Boris Tane
Boris Tane
Stifter

Vi får software til at køre sig selv. Vær med.

Tillid er ikke til forhandling.

AICPA SOC 2

SOC 2 Type II

Uafhængigt reviderede sikkerhedskontroller.

ISO 27001

ISO 27001:2022

Den internationale standard for informationssikkerhedsledelse.

End-to-end-kryptering

AES-256 i hvile, TLS 1.2+ under overførsel.

Dataisolation

Fuldt isoleret pr. organisation.

Se trust center

Spørgsmål.

Hvad er Polylane?

Polylane gør din software selvkørende. AI-agenter lærer alt, du kører, holder øje med produktion for issues, triagerer hver alarm du allerede har, retter det de kan, svarer på de spørgsmål on-call får, giver din kodeagent den samme produktionskontekst og husker hver hændelse.

Hvordan opdager Polylane issues?

Agenter læser de faktiske metrik-, log- og trace-serier og vurderer dem mod, hvordan hver ressource normalt opfører sig. Alt, dit team allerede har grafer over, bliver en kontrol; tærskler findes dér, hvor de er det rigtige værktøj.

Ændrer Polylane produktion uden gennemgang?

Nej, medmindre du udtrykkeligt har tilladt det. Rollbacks er slået fra som standard og begrænset til de services, du vælger. Kodeændringer springer aldrig gennemgangen over: rettelser kommer som pull requests, og din gennemgang og din CI afgør hver merge.

Hvad virker Polylane med?

AWS, Cloudflare, Vercel, Fly.io, Render, Kubernetes, PlanetScale, Supabase og Modal samt GitHub, Slack og dine observability-værktøjer: Datadog, Honeycomb, Axiom, Grafana Cloud og Sentry.

Hvornår kan jeg bruge Polylane?

Polylane er ikke lanceret endnu. Early access rulles ud nu via ventelisten på denne side.

Kan AI-agenter bruge Polylane?

Ja. Platformen har et REST API på api.polylane.com (OpenAPI-spec på api.polylane.com/v1/doc) og en MCP-server på mcp.polylane.com/mcp med dynamisk klientregistrering via OAuth 2.0; se polylane.com/auth.md. Sitets indhold er maskinlæsbart på polylane.com/llms.txt.