仪表盘

2026年，不该再有人需要on-call。

阅读你的代码、观察你的基础设施，并在你醒来之前修好生产环境的智能体。

加入候补名单
或

早期访问正在逐步开放。

Polylane找出你应用中的问题，并自动为你修复。

它学习你运行的一切。 每一个云、每一个仓库、每一条依赖：一张实时的图。

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

它从不停止寻找问题。 问题自己浮现出来，包括那些没人想到要设告警的。

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

它倾听你已有的每一条告警。 每一条告警都经过分诊，真正的故障被调查并修复。

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

它修复的是问题，而不是症状。 它找出每一个检测到的问题的根因，并提交修复它的PR。

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

它回答on-call时会被问到的问题。 这归谁管、改了什么、是不是我们的问题：直接在线程里回复，有据可查。

# 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

它把生产环境带进你的终端。 你的编程智能体在改动任何东西之前，先看清正在运行的是什么。

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…

它记住每一次故障。 下一次永远不会从零开始。

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

不用迁移，不用新SDK。 Polylane接入你已经在运行的一切。

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

由扛过on-call的工程师打造。 来自Cloudflare、Webflow、Groq、Twilio、Uber和Robinhood。

Cloudflare Cloudflare Webflow Webflow Groq Groq Twilio Twilio Uber Uber Robinhood Robinhood
“我花了很多年构建可观测性平台，先是在Baselime，然后在Cloudflare。我们的工具在找出什么坏了这件事上依然很糟糕，而且它自己什么也修不了。on-call依然是坏的。我正在修它。”
Boris Tane
Boris Tane
创始人

我们正在让软件自己运维自己。加入我们。

信任没有商量余地。

AICPA SOC 2

SOC 2 Type II

经独立审计的安全控制。

ISO 27001

ISO 27001:2022

信息安全管理的国际标准。

端到端加密

静态数据AES-256加密，传输中TLS 1.2+。

数据隔离

按组织完全隔离。

查看信任中心

常见问题。

Polylane是什么？

Polylane让你的软件实现自我运维。AI智能体学习你运行的一切，监视生产环境中的问题，分诊你已有的每一条告警，修复力所能及的部分，回答on-call时会被问到的问题，把同样的生产上下文提供给你的编程智能体，并记住每一次故障。

Polylane如何检测问题？

智能体读取真实的指标、日志和追踪序列，并对照每个资源的正常行为做出判断。你团队已经在绘制的任何图表都会成为一项检查；阈值只在它是合适工具的地方存在。

Polylane会未经审查就改动生产环境吗？

不会，除非你明确允许。回滚默认关闭，且只限于你选择的服务。代码变更永远不会跳过审查：修复以拉取请求的形式到达，每一次合并都由你的审查和CI把关。

Polylane支持哪些平台？

AWS、Cloudflare、Vercel、Fly.io、Render、Kubernetes、PlanetScale、Supabase和Modal，再加上GitHub、Slack以及你的可观测性工具：Datadog、Honeycomb、Axiom、Grafana Cloud和Sentry。

我什么时候可以使用Polylane？

Polylane尚未正式发布。早期访问正在通过本页的候补名单逐步开放。

AI智能体可以使用Polylane吗？

可以。平台提供位于api.polylane.com的REST API（OpenAPI规范见api.polylane.com/v1/doc），以及位于mcp.polylane.com/mcp、支持OAuth 2.0动态客户端注册的MCP服务器；详见polylane.com/auth.md。站点内容可通过polylane.com/llms.txt以机器可读形式获取。