Your Worker breaks at 2am. It's fixed before you're awake.
Polylane puts every Worker, Durable Object and D1 database in one graph, and reads their metrics, logs and traces so it knows the moment one misbehaves.
Get started for freeEverything Polylane picks up.
Every Cloudflare product Polylane reads.
Cloudflare Worker 
AI Gateway 
Cloudflare Container 
Durable Object 
D1 Database 
Hyperdrive 
Cloudflare KV 
Cloudflare Pipeline Pipeline Stream Pipeline Sink 
R2 Bucket 
R2 Domain 
Cloudflare Queue 
Secret Store Cloudflare Secret 
Cloudflare Pages Domain 
AI 
Analytics Engine 
Browser Rendering 
Vectorize 
Cloudflare Workflow Cloudflare Zone Worker Route Worker Domain 
Dispatch Namespace Tenant Worker Snippet 
mTLS Certificate 
Cloudflare Tunnel 
Access Application 
Spectrum App 
Turnstile Widget 
Waiting Room 
Health Check 
Load Balancer Load Balancer Pool Load Balancer Monitor 
Logpush Job SSL Certificate 
Email Address 
Stream Live Input 
Cloudflare Images 
Calls App 
AutoRAG 
R2 Data Catalog 
Artifacts Namespace Self-operating, down to the Worker.
Workers, zones and DNS, connected
Workers, Pages, Durable Objects, D1, R2, KV, Queues, Workflows, Hyperdrive, Vectorize, AI Gateway, zones, DNS, tunnels and Access all sit in one graph with their bindings, config and history. It crosses clouds too: a DNS record pointing at a Vercel project is traced to that project.
Nobody has to watch the dashboards
Polylane reads Workers metrics, logs and traces around the clock: requests, errors, CPU time, Durable Object compute. It judges what it sees against how each resource normally behaves, so there are no thresholds to tune and no alert rules to maintain.
A record of every change
Polylane notes what appeared, changed or disappeared in the account. When a Worker misbehaves twelve minutes after a deploy, the investigation starts from that deploy.
Advisories on every resource
Polylane flags Workers without observability enabled, D1 databases without backups and queues stuck retrying. Each advisory says whether Polylane can fix it in place, or what to do about it.
Read-only by default
A guided flow pre-fills the exact token permissions Polylane needs. With a read-only token, Polylane investigates and explains. With full access, a write waits for your approval, with the request and the reason on screen, unless you've allowed it ahead of time.
The bad deploy gets caught
After every Worker deploy or config change, Polylane watches the signals most likely to break against how they looked before. When the cause is a line of code, the permanent fix follows on the repo behind the Worker.
These prompts already work. Copy one, swap your own service name in, and run it.
Give it to your coding agent and let it cook.
“Review PR #241 against production: what does it deploy to, and what breaks if it merges?” 
“If checkout-api goes down, what goes down with it? Walk the graph and rank by traffic.” 
“List every deploy since Friday and flag the ones whose metrics moved afterwards.” 
“Triage everything that fired overnight: what was real, what was noise, and what's still open?” Use Cloudflare with any coding agent. Polylane connects them.
Connect your agent to Polylane once and it can query Cloudflare alongside the rest of your stack.
Guides and fixes for Cloudflare
- Error fix Fix “Durable Object reset because its code was updated” Why a deploy makes Cloudflare Durable Objects throw “reset because its code was updated”, and how to retry safely, keep clients connected and lose no state.
- Error fix Fix Cloudflare “Error 1102: Worker exceeded resource limits” Why a Cloudflare Worker returns Error 1102, how to tell a CPU time overrun from a 128 MB memory overrun, and the code and Wrangler changes that fix each.
- Blog Turn your app into a context graph Agents that run software need a context graph of the app: every resource, what it connects to, the repository that deploys it and the team that owns it. How we built one on Durable Objects, keep it fresh across every provider without polling AWS, decide what counts as a change, and delete from it safely.
- Guide Cloudflare Containers agent sandboxes: startup and setup Cloudflare Containers now start agent sandboxes in a median 648 ms. Set up the durable_object policy, runtime images and snapshots, and know the limits.
- Guide Workers Issues: route Cloudflare errors to coding agents Cloudflare's new Workers Issues groups exceptions and 5xx errors and sends them to Claude Code, Cursor, Devin or a webhook. Setup, automations and limits.
- Guide Cloudflare Basin: a guide to the serverless data platform Cloudflare Basin went GA on 1 October 2026. What its pipelines, Iceberg catalogue and SQL engine do, how to set it up, and the limits to plan for.
- Guide Cloudflare Durable Objects pending I/O keep-alive guide From 2026-10-01, pending I/O keeps Cloudflare Durable Objects in memory after the client leaves. What counts, the 15-minute limit, flags and billing.
- Guide Cloudflare K2: how to adopt serverless event streams Cloudflare K2, announced 1 October 2026, is a serverless event stream on R2. What it is, how it differs from Queues, setup steps and beta limits.
- Guide Cloudflare Hyperdrive connection errors: causes and fixes Fix Cloudflare Hyperdrive connection errors: config codes 2008 to 2016, pool exhaustion, connection_refused and stale clients reused across Worker requests.
- Guide Cloudflare Workers error 1101: causes and how to fix it Error 1101 means your Cloudflare Worker threw an uncaught JavaScript exception. Find the exception in logs, match it to its cause, fix it and roll back fast.
- Guide How to Debug Cloudflare Workers Errors: Logs, Traces and Error Codes Debug Cloudflare Workers errors step by step: read 1101 and 1102 codes, enable Workers Logs and source maps, use wrangler tail, DevTools and local traces.
- Blog How We Fixed Our Cloudflare Durable Objects Memory Exceeded Errors Cloudflare Durable Objects run in V8 isolates with a hard 128 MB limit. Ours idled at ~140 MB and was reset ~300 times a day. 130 MB of zod schemas were built at module load, most of them by code that was never called. How we profiled the production bundle, the two fixes, and the numbers, 218 MB to 82 MB and resets to zero.
Common questions.
Is Polylane an AI SRE for Cloudflare?
It does that work, though we call it self-operating software. Polylane keeps your Workers, Durable Objects and D1 in one graph, investigates what breaks and fixes it with your approval, so the account looks after itself.
How does Polylane connect to my Cloudflare account?
With a Cloudflare API token. The console pre-fills every permission and opens Cloudflare with the token configured, so there's no permission-picking. You choose read-only or full access.
What Cloudflare resources does Polylane sync?
Workers, Pages, Durable Objects, D1, R2, KV, Queues, Workflows, Hyperdrive, Vectorize, AI Gateway, zones, DNS, load balancers, WAF, Tunnels, Access, and more. The full list is on this page.
Can Polylane change my Cloudflare account?
Only if you let it. On a read-only token, Polylane investigates and explains, and code fixes go to your repo for review. With full access, a write pauses for your approval with the request on screen, unless you've allowed it ahead of time.
How does detection work without alert rules?
Polylane reads your metrics, logs and traces around the clock and judges them against how each resource normally behaves. An 18x P99 regression is caught with no threshold set.
Does it work with my observability provider?
Yes: Datadog, Sentry, Honeycomb, Axiom, Grafana Cloud, Logfire, Better Stack and OpenStatus. Forward their alerts and Polylane triages each one.
What does it cost?
There's a free plan, and paid plans start at $80 a month. On Scale and above you can switch on pay-as-you-go beyond the included credits. Every limit is published at polylane.com/pricing.