Nobody should be on-call
Polylane finds issues in your app and fixes them for you, automatically.
Polylane finds issues in your app and fixes them for you, automatically.
Issue hotspot: 4 issues in the last 7 days
Change hotspot: 12 changes in the last 7 days
Change hotspot: 7 changes in the last 7 days
Issue hotspot: 2 issues in the last 7 days
Issue hotspot: 1 issue in the last 7 days
Change hotspot: 3 changes in the last 7 days
main from order-search-trgmMerging 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.
Polylane analysed de91b47 for production impact.
checkout feels slow. is that us or payments-api?
Us. checkout-edge Wall Time P99 is 18× its own baseline and the requests are queuing for a Hyperdrive connection, not on a downstream call.payments-api is answering in 180ms, flat for a week. Deploy 9f3c2a1 at 2:02 AM shrank the hd-prod pool from 50 connections to 5.
how long has it been queueing like that?
Nine minutes, since the deploy landed. It never went above 2 before that. I submitted a PR fix and tagged@justin to deploy 2 minutes ago.
Open in PolylaneConfigure
> 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?
❯ 1. Yes, default it and migrate both callers
❯ 2. Yes, but require it now and let them 400
❯ 3. No, tell Claude what to do differently (esc)
“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.”

We're making software operate itself. Join us.
Independently audited security controls.
The international standard for information security management.
AES-256 at rest, TLS 1.2+ in transit.
Fully isolated per organization.
Polylane makes your software self-operating. AI agents learn everything you run, fix what they can, review every code change against the production it deploys to, answer the questions on-call gets, and give your coding agent the same production context.
Agents read your metrics, logs and traces on a cadence and judge them against how each resource normally behaves. Anything your team already charts becomes a check.
No. Every write pauses for your approval with the exact request on screen, and code changes arrive as pull requests that your review and your CI gate.
AWS, Cloudflare, Vercel, Fly.io, Render, Kubernetes, PlanetScale, Railway, Supabase, Modal, Convex, ClickHouse, and Turso, plus GitHub, Slack, and your observability tools: Datadog, Honeycomb, Axiom, Grafana Cloud, Sentry, Better Stack, OpenStatus, and Logfire.
Now. One command installs the CLI, connects your coding agents, and creates your account: run curl -fsSL https://polylane.com/setup | bash on macOS or Linux.
Yes. There is a REST API at api.polylane.com and an MCP server at mcp.polylane.com/mcp, and this site is machine-readable at polylane.com/llms.txt.