Cloudflare. Workers, Pages, R2, D1, and edge network.
Connect your Cloudflare account to let agents monitor your Workers, Pages, and edge infrastructure. Agents can analyze request patterns, check worker performance, and help troubleshoot issues at the edge.
Join the waitlistWhat Polylane does with Cloudflare.
The whole account in one graph
Workers, Durable Objects, D1, R2, KV, Queues, Workflows, zones, and DNS land in one graph with their bindings, config, and history.
Analytics read on a cadence
Requests, errors, CPU time, and Durable Object compute, judged against how each resource normally behaves. No thresholds to tune.
Rollbacks where you allow them
Off by default. Enabled, agents restore the last known-good Worker version on their own, rate-limited and on the record, and the permanent fix follows.
Advisories on every resource
Workers without observability, D1 databases without backups, queues stuck retrying: each one marked fixable in place or with guidance.
How it works.
Connect
A guided flow pre-fills the exact API token permissions Polylane needs. You choose read-only or full access when you create it.
Sync
The account lands in the graph with its bindings and history, and every sync after records what changed.
Agents take the watch
Analytics are read on a cadence, issues get investigated as they surface, and any write waits for your approval.
In the graph.
The Cloudflare resource types Polylane syncs, with their edges, config, and history.
The tools agents get.
What an agent can do with Cloudflare mid-investigation. Every call lands in the thread transcript, cited.
cloudflareListTelemetryKeys List available Cloudflare telemetry data keys
cloudflareListTelemetryValues List values for a Cloudflare telemetry key
cloudflareRunTelemetryQuery Query Cloudflare Workers / container logs, traces, and AI Gateway request logs
cloudflareTraces Read Cloudflare traces (list summaries, get full span tree)
cloudflareRunGraphqlQuery Execute a GraphQL query against the Cloudflare Analytics API
cloudflareGraphqlSchemaSearch Search the Cloudflare GraphQL schema for matching types, fields, args, and enum values
cloudflareGraphqlSchemaOverview Fetch a paginated overview of all Cloudflare GraphQL types
cloudflareGraphqlTypeDetails Fetch fields, args, and enum values for one Cloudflare GraphQL type
cloudflareGraphqlCompleteSchema Fetch the Cloudflare GraphQL schema with optional root-type details
cloudflareAiGatewayLogs List Cloudflare AI Gateway logs, or fetch one log's full detail
cloudflareAccessApplicationLogs List Cloudflare Access authentication events for an Access application
cloudflareWorkflowInstances List or get Cloudflare Workflows instances
cloudflareApi Call any Cloudflare REST API endpoint that lacks a dedicated tool
cloudflareDeployments List Cloudflare Worker/Pages deployments or Worker versions
Questions.
Is Polylane an AI SRE for Cloudflare?
It's what most people mean by the term: agents that keep your Cloudflare resources in one context graph, watch them, investigate issues and fix what they can, with a human approving anything that changes production. We call it self-operating software rather than an AI SRE: the point is that your software looks after itself, not that a bot joins the on-call rotation.
Can Polylane change anything in Cloudflare?
Only if you let it. Connected read-only, agents investigate and explain, and changes only ever land as pull requests for you to review. With write access, every write pauses for your approval first, with the method, path and reason on screen. Rollbacks are off by default: you enable them per automation and can turn them off at any time.